agentsclimarketplace

Cc skill backend patterns

Skill newmindsgroup/ai-agent-skills-library/dist/skills/cc-skill-backend-patterns

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

Install
npx -y skills add newmindsgroup/ai-agent-skills-library --skill cc-skill-backend-patterns

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.3 KB, 371 tokens by cl100k_base, as published. Nobody here has run it

Backend Development Patterns

Backend architecture patterns and best practices for scalable server-side applications.

When to Use

  • This skill is applicable to execute the workflow or actions described in the overview.

Core Workflow

  1. Confirm the request matches this skill's trigger, scope, and risk profile.
  2. Use the topic map to identify the relevant pattern, checklist, or example before writing detailed guidance or code.
  3. Load references/full-guidance.md when implementation details, examples, anti-patterns, validation checks, or edge cases are needed.
  4. Apply only the relevant guidance instead of loading or repeating the entire reference by default.
  5. Verify the result against any validation checks, limitations, security notes, or platform constraints in the reference.

Topic Map

  • API Design Patterns
  • RESTful API Structure
  • Repository Pattern
  • Service Layer Pattern
  • Middleware Pattern
  • Database Patterns
  • Query Optimization
  • N+1 Query Prevention
  • Transaction Pattern
  • Caching Strategies
  • Redis Caching Layer
  • Cache-Aside Pattern
  • Error Handling Patterns
  • Centralized Error Handler
  • Retry with Exponential Backoff
  • Authentication & Authorization
  • JWT Token Validation
  • Role-Based Access Control

Reference Map

  • references/full-guidance.md preserves the complete original guidance, including examples and detailed edge cases.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Progressive Loading

Keep this SKILL.md as the compact routing and workflow entrypoint. Load the reference file only when the user task requires the deeper implementation material.

What ships with it: 1 file

13.4 KB alongside SKILL.md

references/

Gives 0 of the 12 instructions most data backend skills give in 371 tokens

Counted across 229 of the 229 authors here whose files we hold, read 2026-08-07

  • Separate business logic into service layersin 22 of 229, across 15 files
  • Retry failures with exponential backoffin 21 of 229, across 14 files
  • Select only needed database columnsin 20 of 229, across 13 files
  • Abstract data access into repository classesin 19 of 229, across 12 files
  • Use centralized error handlersin 17 of 229, across 10 files
  • Use AsNoTracking for read-only queriesin 16 of 229, across 4 files
  • Use async/await for all I/O operationsin 16 of 229, across 5 files
  • Implement structured loggingin 15 of 229, across 4 files
  • Use dependency injection for all servicesin 14 of 229, across 2 files
  • Use resource-based URLs for REST APIsin 13 of 229, across 7 files
  • Invalidate cache after data changesin 13 of 229, across 9 files
  • Use a dependency injection containerin 12 of 229, across 4 files

Said here and by no other author read

  • Confirm the request matches the skill scope
  • Identify the relevant pattern before writing code
  • Load detailed guidance only when implementation details are needed
  • Apply only the relevant guidance from references
  • Verify results against validation checks and constraints
  • Stop and ask for clarification if inputs are missing

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,782. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.