backend-designer
Skill4 starsChanged 13 days agoMITView on GitHub
This skill should be used when the user asks to "design an API", "plan database schema", "set up authentication", "design backend architecture", or discusses backend patterns and infrastructure. Provides pragmatic backend design guidance following "solid indie" principles.
In this repository42 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- system-architectSkill
- project-detectorSkill
- audit-routerSkill
- command-skill-token-efficiencySkill
- plugin-auditSkill
- sync-featuresSkill
- devops-helperSkill
- frontend-designerSkill
- git-workflowSkill
- dist-extrasSkill
- distribution-strategistSkill
- homebrew-formula-expertSkill
- homebrew-multi-formulaSkill
- homebrew-setup-wizardSkill
- homebrew-workflow-expertSkill
- architecture-decision-recordsSkill
- changelog-automationSkill
- claude-md-lifecycleSkill
- guard-auditSkill
- hooksSkill
- insights-applySkill
- mode-controllerSkill
- drive-engineSkill
- plan-orchestratorSkill
- repo-triageSkill
- session-stateSkill
- task-analyzerSkill
- workflow-engineSkill
- orchestrator-resilienceSkill
- project-plannerSkill
- preflight-checkSkill
- releaseSkill
- test-generatorSkill
- test-strategistSkill
- adhd-workflowSkill
- brainstorm-insightsSkill
- brainstormSkill
- grillSkill
- prompt-refinerSkill
- background-task-managerSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 48
Start with monolith, extract services only when needed
- Distinctive: line 49
Use proven patterns, avoid trendy frameworks
- Distinctive: line 50
Prefer boring technology that works
- Distinctive: line 51
Document trade-offs, not just decisions
- Distinctive: line 62
When analysis is needed, I will:
- Distinctive: line 65
Delegate to agents: when feasible:
- Very specific: line 69
Run in background: - Use Task tool with run_in_background: true
- Distinctive: line 88
When activated, I provide:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Backend Designer Skill
Auto-activated when: User discusses backend architecture, API design, database decisions, or authentication patterns.
Core Capabilities
1. API Design Patterns
- RESTful API structure (resources, endpoints, versioning)
- GraphQL schema design
- API authentication (JWT, OAuth, API keys)
- Rate limiting and throttling strategies
- Error handling and status codes
2. Database Design
- Schema design (normalized vs denormalized)
- Index strategies for performance
- Migration planning
- ORM vs raw SQL trade-offs
- Connection pooling
3. Authentication & Authorization
- Session management (JWT vs session cookies)
- OAuth flows (authorization code, client credentials)
- Permission models (RBAC, ABAC)
- Secure token storage
- Password hashing (bcrypt, argon2)
4. Performance Patterns
- Caching strategies (Redis, in-memory, CDN)
- Query optimization
- Background jobs (Celery, Bull, Temporal)
- Horizontal scaling considerations
- Database read replicas
Design Philosophy: Solid Indie
Ship Fast Principles:
- Start with monolith, extract services only when needed
- Use proven patterns, avoid trendy frameworks
- Prefer boring technology that works
- Document trade-offs, not just decisions
Anti-Patterns to Avoid:
- ❌ Microservices for < 5 person teams
- ❌ Over-abstraction (generic repositories, factories)
- ❌ Premature optimization
- ❌ Complex caching before measuring
Delegation Strategy
When analysis is needed, I will:
- Analyze current state - Review existing code/architecture
- Delegate to agents when feasible:
backend-architectagent for deep architectural analysisdatabase-architectagent for schema optimizationsecurity-specialistagent for auth review
- Run in background - Use Task tool with
run_in_background: true - Synthesize results - Combine agent outputs into actionable recommendations
Example Activation
User: "I need to design an API for user authentication with social login"
Skill activates and provides:
1. Quick assessment of requirements
2. Recommends OAuth 2.0 flow (authorization code + PKCE)
3. Suggests passport.js or similar proven library
4. Outlines token storage strategy
5. Delegates security review to security-specialist agent (background)
6. Returns with comprehensive auth implementation planOutput Format
When activated, I provide:
Immediate Response
- Pattern Recognition: Identify the design problem category
- Quick Recommendation: Suggest proven pattern
- Trade-offs: List pros/cons of approach
Delegated Analysis (Background)
- Launch appropriate agent for deep analysis
- Provide progress updates
- Synthesize agent findings into actionable plan
Final Output
- Recommended approach with rationale
- Implementation steps (numbered, concrete)
- Code examples (if requested)
- Next steps (what to build first)
Integration with Existing Workflow
- Complements
/brainstormcommand (auto-activates during brainstorm sessions) - Works with
/next(suggests backend implementation steps) - Integrates with
/done(captures backend design decisions)
Remember: This skill auto-activates based on keywords. No explicit invocation needed. Keep responses focused, actionable, and indie-friendly (no corporate over-engineering).
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.

