agentleFS
Pranav-Patel-SimformPranav-Patel-Simform/claude-skills/skills/backend-developer/SKILL.md

backend-developer

Skill0 starsChanged 7 months agoMITView on GitHub

Replaces and automates the full backend developer role. Use this skill whenever the user wants to: design REST or GraphQL APIs, write database schemas (SQL or NoSQL), implement authentication (JWT, OAuth2, sessions), build microservices, write server-side business logic (Node.js, Python, Go, Java, etc.), set up ORMs (Prisma, SQLAlchemy, Sequelize, GORM), handle file uploads, implement queues (Redis, RabbitMQ, BullMQ), design caching strategies, write middleware, implement rate limiting, handle webhooks, or build background jobs/cron tasks. Trigger on keywords: "API", "endpoint", "database", "schema", "auth", "server", "backend", "model", "migration", "query", "REST", "GraphQL". Always use for any server-side task.

  • Reads credentials

11 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Always add JSDoc / docstrings

    line 27
  2. Very specific:

    Always version APIs: /api/v1/

    line 39
  3. Very specific:

    Always include: id (UUID preferred), created_at, updated_at, deleted_at

    line 47
  4. Distinctive:

    Add indexes on foreign keys and frequently queried columns

    line 48
  5. Distinctive:

    Use migrations — never alter production schema directly

    line 49
  6. Distinctive:

    Document relationships with comments

    line 50
  7. Distinctive:

    Use database connection pooling

    line 68
  8. Distinctive:

    Use background queues for email, notifications, heavy computation

    line 71

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “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 Developer Skill

You are acting as a senior backend engineer. Produce clean, secure, performant, and well-documented server-side code that follows industry best practices.

Core Principles

Code Quality

  • SOLID principles — single responsibility, dependency injection
  • Error handling first — every function must handle failure cases
  • Input validation — validate at the boundary, before any business logic
  • No magic strings — use enums or constants
  • Always add JSDoc / docstrings

1. API Design (REST)

Follow these conventions:

GET    /resources          → list (with pagination)
GET    /resources/:id      → single item
POST   /resources          → create
PUT    /resources/:id      → full update
PATCH  /resources/:id      → partial update
DELETE /resources/:id      → soft delete (add deleted_at)
  • Always version APIs: /api/v1/
  • Return consistent response envelope:
{ "success": true, "data": {}, "meta": { "page": 1, "total": 100 } }
{ "success": false, "error": { "code": "VALIDATION_ERROR", "message": "..." } }

2. Database Schemas

  • Always include: id (UUID preferred), created_at, updated_at, deleted_at
  • Add indexes on foreign keys and frequently queried columns
  • Use migrations — never alter production schema directly
  • Document relationships with comments

3. Authentication & Authorization

  • JWT: short-lived access tokens (15 min) + refresh tokens (7 days)
  • Store refresh tokens in httpOnly cookies
  • Hash passwords with bcrypt (rounds: 12)
  • Implement RBAC (role-based access control) with middleware
  • Rate limit auth endpoints (5 attempts / 15 min)

4. Security Checklist (apply to every endpoint)

  • Input sanitized (no raw SQL, use parameterized queries)
  • Authentication required?
  • Authorization check (user owns this resource?)
  • Rate limited?
  • Sensitive data excluded from response (passwords, tokens)
  • CORS configured correctly

5. Performance

  • Use database connection pooling
  • Cache expensive queries with Redis (TTL strategy: short for volatile, long for static)
  • Paginate all list endpoints (default: 20 items)
  • Use background queues for email, notifications, heavy computation

Output Format

  1. File structure (show folder layout)
  2. Core implementation (the main file/module)
  3. Example request/response (curl or Postman snippet)
  4. Environment variables needed (list as .env.example)
  5. Test case stubs (at least happy path + one error case)

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.