backend-patterns
Skill153 starsChanged 8 months agoMITView on GitHub
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
88 other projects use a version of this.
Adopted by
Most recently taken up by
- Rojios/everything-claude-codetheir own version, first seen Nov 8, 2026
- lhbsaa/apex-unifiedtheir own version, first seen Nov 8, 2026
- ahmadvahidi/skill-atlastheir own version, first seen Nov 8, 2026
- Ashfaqbs/ai-coding-agent-toolkittheir own version, first seen Nov 8, 2026
- Lukk17/agent-standardstheir own version, first seen Nov 7, 2026
- XD3an/cc-plustheir own version, first seen Nov 7, 2026
Used with
Projects with it also use everything-claude-code, investor-materials and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
InfopibeSkilleverything-claude-code
Also in 10 projects that use this
InfopibeSkillinvestor-materials
Create and update pitch decks, one-pagers, investor memos, accelerator applications, financial models, and fundraising materials. Use when the user needs investor-facing documents, projections, use-of-funds tables, milestone plans, or materials that must stay internally consistent across multiple fundraising assets.
Also in 29 projects that use this
niloykumarbarmanSkillagent-sort
Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.
Also in 10 projects that use this
tpavanipradeepSkillbun-runtime
Bun as runtime, package manager, bundler, and test runner. When to choose Bun vs Node, migration notes, and Vercel support.
Also in 21 projects that use this
mryeastcodeSkilleverything-claude-code-conventions
Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.
Also in 8 projects that use this
gongyijie85Skillunified-memory
Share durable, inspectable context and handoffs between Claude, Codex, Hermes, Cursor, OpenCode, and other agents through the local ECC Memory Vault. Use when an agent must save work state, transfer context, resume another agent's task, or search shared project knowledge.
Also in 4 projects that use this
- +1 more from Infopibe
Other versions88 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 88
- affaan-m/ECC★ 246ksame name
- YosemiteCrew/Yosemite-Crew★ 2ksame name
- xu-xiang/everything-claude-code-zh★ 1.9ksame name
- loulanyue/awesome-claude-notes★ 272same name
- tpavanipradeep/everything-claude-code★ 104same name
- mturac/everything-openai-codex★ 89same name
- mit-network/everything-claude-code★ 76same name
- tranhieutt/software_development_department★ 71same name
- Fmarzochi/EGC★ 61same name
- ysyecust/everything-claude-code★ 44same name
78 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- rules/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- clickhouse-ioSkill
- cloudnative-writing-baselineSkill
- coding-standardsSkill
- eval-harnessSkill
- frontend-patternsSkill
- project-guidelines-exampleSkill
- prompt-patternsSkill
- security-reviewSkill
- strategic-compactSkill
- tdd-workflowSkill
- verification-loopSkill
- web-content-extractionSkill
The file
Files
Backend Development Patterns
Backend architecture patterns and best practices for scalable server-side applications.
Pattern Categories
API Design
RESTful structure, Repository pattern, Service layer, Middleware pattern. See references/api-patterns.md for implementations.
Database & Caching
Query optimization, N+1 prevention, transactions, Redis cache-aside pattern. See references/database-caching.md for implementations.
Error Handling, Auth & Infrastructure
Centralized error handler, retry with backoff, JWT/RBAC, rate limiting, job queues, structured logging. See references/error-auth-infra.md for implementations.
Quick Decision Guide
| Need | Pattern |
| Data access abstraction | Repository pattern |
| Business logic isolation | Service layer |
| Auth/logging/validation | Middleware pattern |
| Expensive DB queries | Cache-aside (Redis) |
| N+1 query problem | Batch fetch with Map |
| Atomic multi-table writes | Database transactions |
| Unreliable external APIs | Retry with exponential backoff |
| Abuse prevention | Rate limiter (in-memory or Redis) |
| Non-blocking operations | Job queue |
Remember: Choose patterns that fit your complexity level. Not every project needs every pattern.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

