SKILL

backend-patterns

Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.

Target: Software development & testing. Automatically collected · unverified.

Excerpt from the author’s documentation

Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.

Read the original English text

Topics in the source

  • Backend Development Patterns
  • When to Activate
  • API Design Patterns
  • RESTful API Structure
  • Repository Pattern
  • Service Layer Pattern
  • Middleware Pattern
  • Database Patterns

Backend architecture patterns and best practices for scalable server-side applications. Designing REST or GraphQL API endpoints Implementing repository, service, or controller layers Optimizing database queries (N+1, indexing, connection pooling) Adding caching (Redis, in-memory, HTTP cache headers) Setting up background jobs or async processing Structuring error handling and validation for APIs Building middleware (auth, logging, rate limiting) Remember: Backend patterns enable scalable, maintainable server-side applications. Choose patterns that fit your complexity level.

Source repository
affaan-m/ECC
Source file
.kiro/skills/backend-patterns/SKILL.md
Fixed revision
d2ef2680594f9a17526a6e1a2e18b3d242c5d17b
Read the complete original documentation ↗

Sources and evidence

This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.

Author: affaan-m/ECC · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-09T14:01:48.541Z.

Categories are inferred from names, descriptions and paths. They do not establish compatibility.

License and attribution

MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.

Original license ↗

Synchronization, copying and user-reported success do not mark a resource as runtime-tested.

Limitations and notes

  • Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.