agentleFS
mikeparcewskimikeparcewski/wicked-garden/skills/engineering/backend/SKILL.md

wicked-garden-engineering-backend

Skill9 starsChanged 7 months agoMITView on GitHub

Backend engineering specialist for APIs, databases, server-side patterns, data modeling, scalability, and integrations.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use comprehensive checklists for:

    line 79
  2. Distinctive:

    Always hash passwords (never plaintext)

    line 99
  3. Distinctive:

    Use transactions for multi-step operations

    line 101
  4. Distinctive:

    Use background jobs for slow operations

    line 103

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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 Skill

Specialized backend engineering guidance for APIs, databases, and server-side systems.

When to Use

  • Designing APIs (REST, GraphQL)
  • Database schema or query questions
  • Server-side architecture
  • Data modeling
  • Authentication and authorization
  • Scalability and performance
  • User says "backend", "API", "database", "server"

Key Focus Areas

API Design

  • RESTful conventions (resources, methods, status codes)
  • GraphQL schema design
  • API versioning strategies
  • Request/response validation
  • Error handling and messaging
  • Pagination and filtering
  • Rate limiting

Database Patterns

  • Schema design and normalization
  • Indexing strategies
  • Query optimization
  • Transaction management
  • Connection pooling
  • Migration best practices
  • N+1 query prevention

Data Modeling

  • Entity definition
  • Relationship modeling (1:1, 1:N, N:M)
  • Data types and constraints
  • Validation rules
  • Audit trails

Authentication & Authorization

  • Password hashing (bcrypt, argon2)
  • JWT or session management
  • OAuth2 / OIDC patterns
  • RBAC (Role-Based Access Control)
  • API key management

Performance & Scalability

  • Query optimization and EXPLAIN plans
  • Caching strategies (Redis, memcached)
  • Background jobs (Celery, Bull)
  • Database read replicas
  • Horizontal scaling

Integration Patterns

  • External API resilience (retry, timeout, circuit breaker)
  • Webhook handling with retry
  • Message queue patterns
  • Idempotency for critical operations

Review Process

Use comprehensive checklists for:

  • API quality (REST conventions, validation, versioning)
  • Database quality (schema, indexes, transactions)
  • Security (auth, validation, injection prevention)

See refs/checklists.md for detailed checklists, anti-patterns, and output templates.

Code Patterns

Common backend patterns for:

  • API endpoints with auth and validation
  • Query optimization and N+1 prevention
  • Authentication and authorization
  • External API integration with resilience
  • Caching strategies

See refs/patterns.md for code examples and best practices.

Notes

  • Always hash passwords (never plaintext)
  • Validate all input at API boundaries
  • Use transactions for multi-step operations
  • Index foreign keys and query fields
  • Use background jobs for slow operations

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.