Nodejs Backend Patterns
ever-works/ever-works
Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices.
Comprehensive backend development workflow that orchestrates expert analysis, architecture design, implementation, and deployment using the integrated toolset.
$ npx skills add julianromli/opencode-template --skill backend-dev -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install julianromli/opencode-template backend-dev --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/julianromli/opencode-template.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skill/backend-dev .claude/skills/backend-dev && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "backend-dev" agent skill from https://github.com/julianromli/opencode-template/tree/main/skill/backend-dev into .claude/skills/backend-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backend-dev", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/julianromli/opencode-template/tree/main/skill/backend-devType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add julianromli/opencode-template --skill backend-dev -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install julianromli/opencode-template backend-dev --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/julianromli/opencode-template.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skill/backend-dev .agents/skills/backend-dev && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "backend-dev" agent skill from https://github.com/julianromli/opencode-template/tree/main/skill/backend-dev into .agents/skills/backend-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backend-dev", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add julianromli/opencode-template --skill backend-dev -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install julianromli/opencode-template backend-dev --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/julianromli/opencode-template.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skill/backend-dev .cursor/skills/backend-dev && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "backend-dev" agent skill from https://github.com/julianromli/opencode-template/tree/main/skill/backend-dev into .cursor/skills/backend-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backend-dev", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/julianromli/opencode-template.git --path skill/backend-dev--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add julianromli/opencode-template --skill backend-dev -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install julianromli/opencode-template backend-dev --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/julianromli/opencode-template.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skill/backend-dev .gemini/skills/backend-dev && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "backend-dev" agent skill from https://github.com/julianromli/opencode-template/tree/main/skill/backend-dev into .gemini/skills/backend-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backend-dev", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install julianromli/opencode-template backend-devInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add julianromli/opencode-template --skill backend-dev -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/julianromli/opencode-template.git skills-src && mkdir -p .github/skills && cp -r skills-src/skill/backend-dev .github/skills/backend-dev && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "backend-dev" agent skill from https://github.com/julianromli/opencode-template/tree/main/skill/backend-dev into .github/skills/backend-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backend-dev", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add julianromli/opencode-template --skill backend-dev -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install julianromli/opencode-template backend-dev --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/julianromli/opencode-template.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skill/backend-dev .opencode/skills/backend-dev && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "backend-dev" agent skill from https://github.com/julianromli/opencode-template/tree/main/skill/backend-dev into .opencode/skills/backend-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backend-dev", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
backend-devComprehensive backend development workflow that orchestrates expert analysis, architecture design, implementation, and deployment using the integrated toolset.
Backend Dev is an agent skill from julianromli/opencode-template. Comprehensive backend development workflow that orchestrates expert analysis, architecture design, implementation, and deployment using the integrated toolset. Handles everything from API design and database architecture to security implementation and DevOps automation.
Its SKILL.md is about 4.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files (for example `README.md` and `examples.md`).
It sits in Backend & APIs, covering Backend development, API design and Deployment. The repository describes itself as: OpenCode CLI Template by @faizntfd. The licence is Apache-2.0.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 37ceab2. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
pythonplaywrightFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Backend Dev loads about 4.4k tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 1,243 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from julianromli/opencode-template at commit 37ceab2, republished under its Apache-2.0 licence (© julianromli). 1,243 words, ~4,355 tokens.
.claude/skills/backend-dev/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.This skill provides end-to-end backend development services by orchestrating multiple expert systems, advanced development techniques, and specialized tools. It transforms business requirements into production-ready backend systems with comprehensive architecture, security, scalability, and operational excellence.
Key Capabilities:
Perfect for:
Triggers:
Use when: Starting new backend development or modernizing existing systems
Tools Used:
/sc:analyze backend-requirements
BMAD PM Agent: business requirement analysis
Requirements Analyst: technical specification creation
Deep Research Agent: technology stack researchActivities:
Use when: Designing the technical architecture and system components
Tools Used:
/sc:design --type architecture backend-system
/sc:design --type api restful-apis
/sc:design --type database data-model
Backend Architect: comprehensive system design
Security Engineer: security architecture planningActivities:
Use when: Preparing for actual code implementation
Tools Used:
/sc:design --type component implementation-strategy
Python Expert: technology-specific implementation patterns
DevOps Architect: deployment and infrastructure planning
Performance Engineer: optimization and monitoring setupActivities:
Use when: Writing production-ready backend code
Tools Used:
/sc:implement backend-service
Python Expert: production-quality code implementation
Security Engineer: secure coding practices and vulnerability prevention
Database Specialist: optimized database interactions
Performance Engineer: efficient algorithms and caching strategiesActivities:
Use when: Ensuring system reliability and security
Tools Used:
/sc:test backend-comprehensive
Quality Engineer: testing strategy implementation
Security Engineer: security testing and vulnerability scanning
Performance Engineer: load testing and performance validation
Playwright MCP: end-to-end API testingActivities:
Use when: Preparing for production deployment
Tools Used:
/sc:implement production-deployment
DevOps Architect: CI/CD pipeline and infrastructure setup
Security Engineer: production security hardening
Monitoring Setup: observability and alerting systemsActivities:
| Command | Use Case | Output |
|---|---|---|
/sc:design --type architecture | System architecture | Technical architecture specifications |
/sc:design --type api | API design | RESTful/GraphQL API specifications |
/sc:design --type database | Database design | Optimized schema and data models |
/sc:implement backend | Code implementation | Production-ready backend services |
/sc:test backend | Testing strategy | Comprehensive testing plans |
/sc:build deploy | Deployment setup | CI/CD and infrastructure automation |
| Technique | Role | Capabilities |
|---|---|---|
| Greenfield Service Workflow | New project development | Complete backend service development |
| Brownfield Integration | Legacy modernization | Safe system evolution and integration |
| Security-First Development | Secure implementation | Built-in security practices and validation |
| Performance Optimization | Scalability planning | Bottleneck identification and optimization |
| Server | Expertise | Use Case |
|---|---|---|
| Sequential | Complex reasoning | Architecture analysis and problem-solving |
| Context7 | Technical patterns | Framework best practices and implementation guides |
| Playwright | API testing | End-to-end API validation and testing |
| Serena | Project memory | Large codebase navigation and context management |
User: "Create a backend API for an e-commerce platform with user management, product catalog, and order processing"
Workflow:
1. Phase 1: Analyze e-commerce requirements and technical constraints
2. Phase 2: Design microservices architecture with API contracts
3. Phase 3: Plan implementation with Node.js/Express and PostgreSQL
4. Phase 4: Implement secure APIs with JWT authentication
5. Phase 5: Test with comprehensive test suites and load testing
6. Phase 6: Deploy with Docker, Kubernetes, and CI/CD pipeline
Output: Production-ready e-commerce backend with 99.9% uptime targetUser: "Optimize our database architecture for better performance and scalability"
Workflow:
1. Phase 1: Analyze current database performance and bottlenecks
2. Phase 2: Design optimized schema with proper indexing
3. Phase 3: Plan migration strategy with zero downtime
4. Phase 4: Implement caching layer and query optimization
5. Phase 5: Performance test and validate improvements
6. Phase 6: Deploy with monitoring and alerting
Output: 60% performance improvement with horizontal scaling capabilityUser: "Implement comprehensive security for our financial services backend"
Workflow:
1. Phase 1: Analyze security requirements and compliance needs (SOC2, PCI-DSS)
2. Phase 2: Design zero-trust security architecture
3. Phase 3: Plan secure implementation with encryption and audit logging
4. Phase 4: Implement security controls and monitoring
5. Phase 5: Conduct security testing and vulnerability assessment
6. Phase 6: Deploy with security monitoring and incident response
Output: Fully compliant financial services backend with comprehensive securitybackend-system/
├── api/
│ ├── controllers/ # API endpoint implementations
│ ├── middleware/ # Authentication, validation, error handling
│ ├── routes/ # API routing and endpoint definitions
│ └── documentation/ # API documentation and contracts
├── services/
│ ├── business/ # Business logic and domain services
│ ├── data/ # Data access and database services
│ ├── external/ # Third-party service integrations
│ └── security/ # Security services and utilities
├── database/
│ ├── migrations/ # Database schema migrations
│ ├── seeds/ # Initial data setup
│ ├── models/ # Data models and relationships
│ └── queries/ # Optimized database queries
├── tests/
│ ├── unit/ # Unit tests for individual components
│ ├── integration/ # Integration tests for service interactions
│ ├── e2e/ # End-to-end API tests
│ └── performance/ # Load and stress tests
├── infrastructure/
│ ├── docker/ # Container configurations
│ ├── kubernetes/ # K8s deployment manifests
│ ├── ci-cd/ # CI/CD pipeline configurations
│ └── monitoring/ # Logging, metrics, and alerting
├── documentation/
│ ├── architecture.md # System architecture documentation
│ ├── api-specs.md # API specifications and contracts
│ ├── deployment.md # Deployment procedures and runbooks
│ └── security.md # Security procedures and compliance
└── config/
├── development/ # Development environment configurations
├── staging/ # Staging environment configurations
└── production/ # Production environment configurationsThis backend development skill transforms the complex process of backend system creation into a guided, expert-supported workflow that leverages the full power of your integrated development toolset. It ensures that backend systems are secure, scalable, maintainable, and production-ready from day one.
© julianromli, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 3 other files in skill/backend-dev of julianromli/opencode-template.
Open the folder on GitHubat commit 37ceab2
Backend Dev next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Backend Dev this skilljulianromli/opencode-template | 144 | — | ~4.4k | Automated safety check: Pass | Apache-2.0 | |
| Nodejs Backend Patternsever-works/ever-works | 158 | 18 repos | ~4k | Automated safety check: Pass | AGPL-3.0 | |
| Pangolin CRUD Endpointsfosrl/pangolin | 23k | — | ~461 | Automated safety check: Pass | Custom licence | |
| Backend PatternshellangleZ/burn-in-cceverywhere-ralph | 112 | 17 repos | ~3.3k | Automated safety check: Pass | None | |
| API Surface Reviewpolarsource/polar | 10k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Backend FundamentalsDanielPodolsky/ownyourcode | 290 | 1 repos | ~1.1k | Automated safety check: Pass | MIT |
ever-works/ever-works
Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices.
fosrl/pangolin
Use whenever asked to add, create, or scaffold a CRUD endpoint, router, or entity in this repo's server (create/list/get/update/delete handlers, new…
hellangleZ/burn-in-cceverywhere-ralph
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
polarsource/polar
Review changes to Polar's API contract — Pydantic schemas, FastAPI endpoints, OpenAPI output and the generated SDKs.
DanielPodolsky/ownyourcode
Reviews API design, REST conventions, and backend architecture.
selmakcby/claude-agents-skills
Backend API design specialist. An agent skill from selmakcby/claude-agents-skills.
julianromli/opencode-template
A skill your agent uses when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory…
julianromli/opencode-template
Autonomous agent loop for completing features. An agent skill from julianromli/opencode-template.
julianromli/opencode-template
Optimize Next.js App Router data fetching by converting slow client-side fetching to fast server-side fetching using React Server Components (RSC).
julianromli/opencode-template
Manage shadcn/ui components using MCP tools. An agent skill from julianromli/opencode-template.
julianromli/opencode-template
Analyze and implement purposeful UI animations for Next.js + Tailwind + React projects.
julianromli/opencode-template
Generate hierarchical AGENTS.md structures for codebases. An agent skill from julianromli/opencode-template.
Categories
Comprehensive backend development workflow that orchestrates expert analysis, architecture design, implementation, and deployment using the integrated toolset. Backend Dev is an agent skill from julianromli/opencode-template. Comprehensive backend development workflow that orchestrates expert analysis, architecture design, implementation, and deployment using the integrated toolset.
Backend Dev fits situations like: tasks that involve Backend development; tasks that involve API design; tasks that involve Deployment.
Run `npx skills add julianromli/opencode-template --skill backend-dev -a claude-code`. Or copy the skill folder (skill/backend-dev in julianromli/opencode-template) into .claude/skills/backend-dev in your project. Claude Code loads it when a task matches its description.
Run `npx skills add julianromli/opencode-template --skill backend-dev -a codex`. Or copy the skill folder (skill/backend-dev in julianromli/opencode-template) into .agents/skills/backend-dev in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add julianromli/opencode-template --skill backend-dev -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/backend-dev, .gemini/skills/backend-dev, .github/skills/backend-dev and .opencode/skills/backend-dev in your project.
Going by SKILL.md and its folder, Backend Dev needs the command-line tools its instructions call (python and playwright). Our summary lists: Python 3; Node.js; Docker.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Backend Dev is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.4k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Backend Dev: Nodejs Backend Patterns (ever-works/ever-works, 158 stars), Pangolin CRUD Endpoints (fosrl/pangolin, 23k stars), Backend Patterns (hellangleZ/burn-in-cceverywhere-ralph, 112 stars) and API Surface Review (polarsource/polar, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
julianromli (a GitHub user) maintains it in julianromli/opencode-template, which has 144 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on February 3, 2026.
Source: julianromli/opencode-template on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.