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
- teja1103/Claude-Skillstheir own version, first seen Nov 16, 2026
- AndreasKarz/Vibe-Coding-Dev-Setuptheir own version, first seen Nov 16, 2026
- Vinix24/vnx-orchestrationtheir own version, first seen Nov 12, 2026
- mcabreradev/hermes-sdd-agencytheir own version, first seen Sep 17, 2026
- younss/skillstheir own version, first seen Sep 8, 2026
- jshsakura/awesome-opencode-skillstheir own version, first seen Jul 8, 2026
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- Vinix24/vnx-orchestration★ 63same name
- jshsakura/awesome-opencode-skills★ 31same name
- belokonm/claude-supercode-skills★ 11same name
- boxclawai/skills★ 9same name
- nicolasestrem/antigravity-gemini-skills★ 8same name
- AndreasKarz/Vibe-Coding-Dev-Setup★ 7same name
- BenjaminG/ai-skills★ 4same name
- marttp/my_agent_skills_I_use★ 4same name
- mcabreradev/hermes-sdd-agency★ 1same name
- younss/skills★ 1same name
1 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 repository4 other files it gives its agents.
- devopsSkill
- frontend-developerSkill
- hrSkill
- qa-engineerSkill
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
- Distinctive: line 27
Always add JSDoc / docstrings
- Very specific: line 39
Always version APIs: /api/v1/
- Very specific: line 47
Always include: id (UUID preferred), created_at, updated_at, deleted_at
- Distinctive: line 48
Add indexes on foreign keys and frequently queried columns
- Distinctive: line 49
Use migrations — never alter production schema directly
- Distinctive: line 50
Document relationships with comments
- Distinctive: line 68
Use database connection pooling
- Distinctive: line 71
Use background queues for email, notifications, heavy computation
“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.
Files
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
- File structure (show folder layout)
- Core implementation (the main file/module)
- Example request/response (curl or Postman snippet)
- Environment variables needed (list as
.env.example) - Test case stubs (at least happy path + one error case)
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.

