agentleFS
Data-WiseData-Wise/craft/skills/design/backend-designer/SKILL.md

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.

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
  1. Distinctive:

    Start with monolith, extract services only when needed

    line 48
  2. Distinctive:

    Use proven patterns, avoid trendy frameworks

    line 49
  3. Distinctive:

    Prefer boring technology that works

    line 50
  4. Distinctive:

    Document trade-offs, not just decisions

    line 51
  5. Distinctive:

    When analysis is needed, I will:

    line 62
  6. Distinctive:

    Delegate to agents: when feasible:

    line 65
  7. Very specific:

    Run in background: - Use Task tool with run_in_background: true

    line 69
  8. Distinctive:

    When activated, I provide:

    line 88

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

  1. Analyze current state - Review existing code/architecture
  2. Delegate to agents when feasible:
    • backend-architect agent for deep architectural analysis
    • database-architect agent for schema optimization
    • security-specialist agent for auth review
  3. Run in background - Use Task tool with run_in_background: true
  4. 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 plan

Output 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 /brainstorm command (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).

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.