backend-patterns
/backend-patterns
Implement backend APIs, data access, caches and jobs for Node.js/TypeScript services; use for substantive server-side changes, with patterns adapted to the existing stack.
- Author
- Selenophile2004 ↗
- Repository
- applied-agent-skills ↗
- Licence
- MIT
- Last repository change
- 03.11.2026
Assessment and security
- Files in this package
- 5
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 2
No signals detected. Repository changed on 03.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Implement backend APIs, data access, caches and jobs for Node.js/TypeScript services; use for substantive server-side changes, with patterns adapted to the existing stack.
Original author description
Implement backend APIs, data access, caches and jobs for Node.js/TypeScript services; use for substantive server-side changes, with patterns adapted to the existing stack.
How it works
- Specialized cases and output contract
- Task contract
SKILL.md preview
--- name: backend-patterns description: Implement backend APIs, data access, caches and jobs for Node.js/TypeScript services; use for substantive server-side changes, with patterns adapted to the existing stack. metadata: source: https://github.com/WorldFlowAI/everything-claude-code source-commit: 432485ba6b92c14fb357276a98957f348bcff9ee adaptation: Agent Skills; English; task-scoped; 2026-11-02 --- # Backend implementation patterns Use for implementing or materially changing Node.js/TypeScript services, Express or Next.js API routes, database access, caches and background jobs. Preserve the project's stack and contracts; other stacks can reuse general principles without importing Node-specific APIs. - Inspect the relevant endpoint, data model, authorization boundary and existing implementation. Choose only the layers the task needs; do not introduce repositories, queues or microservices by default. - Keep API contracts explicit: runtime input validation, consistent errors, pagination/filtering, status codes and backwards compatibility. Enforce resource/tenant authorization separately from authentication. - Select needed fields, batch related queries and inspect actual query behavior to avoid N+1 work. Use transactions for genuine atomic invariants, parameterized operations and migrations appropriate to the change. - Design caches with explicit keys, tenant/permission isolation, freshness and invalidation. Choose shared storage when cross-instance consistency matters; process-local caches and limiters are not distributed guarantees. - Retry transient failures with bounds, backoff and cancellation where appropriate. Retry writes only with idempotency or equivalent protection. Preserve meaningful errors, timeouts and partial-failure state. - Use durable queues for jobs that must survive process restarts. Define retries, deduplication, concurrency and failure handling according to requirements; an in-memory example is not a durable job system. - Keep logs useful and redacted; preserve request correlation without exposing credentials or user data. Validate affected contracts, data integrity and failure paths with existing commands, broadening checks when dependencies require it. - Make focused changes and reuse existing libraries/runtime. Do not add infrastructure, dependencies or deployments solely to conform to a pattern. For implementation illustrations, search the relevant API, Database, Caching, Error Handling, Authorization or Background Jobs heading in [upstream reference](https://github.com/WorldFlowAI/everything-claude-code/blob/432485ba6b92c14fb357276a98957f348bcff9ee/skills/backend-patterns/SKILL.md). Read only needed sections. The samples require validation against current library APIs; do not copy them as complete middleware, authorization or durable-queue implementations. ## Specialized cases and output contract For substantive relevant work, read [the applied workflow](references/transactional-api-cases.md). Keep unrelated references unloaded. ## Task contract Inputs: Existing stack/contracts, data invariants, tenancy, durability requirements and tests. Deliver: Focused implementation/design, contract/invariant notes and relevant failure-path verification. Acceptance: No blind write retries; concurrency invariants; tenant-safe cache/invalidation; durable required jobs; justified infrastructure.
Files in this package (5)
- LICENSE 1 KB
- README.md 1 KB
- SKILL.md 3 KB
- agents/openai.yaml 1 KB
- references/transactional-api-cases.md 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · Selenophile2004/applied-agent-skills | 100 | MIT |
| Sanit-mann/The-Insectoids | 100 | MIT |
| tadokoro-ryusuke/cc-plugins | 100 | MIT |
| kensaurus/cursor-kenji | 100 | MIT |
| tranhieutt/software_development_department | 100 | MIT |
| affaan-m/ECC | 95 | MIT |
| affaan-m/ECC | 95 | MIT |
| SHRIJANAGAIN/Nemo-Cli | 95 | Apache-2.0 |
| andersonlimahw/lemon-ai-hub | 95 | MIT |
Database snapshot: 13.11.2026 · package version 79dcce255cbe (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100node-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes. Use when building or reviewing Node.js, Express, or Next.js API routes and their data access. - 100backend-dev-guidelines
Backend development guidelines for Node.js/Express/TypeScript applications. Layered architecture (Routes → Controllers → Services → Repositories), error handling, validation, middleware patterns, database access, and testing. Use when creating routes, endpoints, APIs,… - 100backend-api-builder
Designs and builds backend APIs and services in Python or Node: routes, auth, databases, background jobs, rate limits and deployment. Use when the user asks for an API, server, bot backend, database layer, webhook handler, or help deploying a backend. - 100nodejs-backend
Node.js backend patterns: framework selection, layered architecture, TypeScript, validation, error handling, security, production deployment. Use when building REST APIs, Express/Fastify servers, microservices, or server-side TypeScript. - 90node-typescript-backend
Build production Node.js/TypeScript backends (Fastify, NestJS, Express): structure, validation, async, errors, config, testing, performance. Use when writing or reviewing Node/TS services or APIs. - 100backend
Backend development patterns for services, error handling, logging, caching. Use when building backend services, APIs, or microservices.