backend-api-builder
/backend-api-builder
Designs and builds backend APIs and services in Python or Node: routes, auth, databases, background jobs, rate limits and deployment. Use when the user asks for an API, server, bot backend, database layer, webhook handler, or help deploying a backend.
- Author
- dev-shubh-madara ↗
- Repository
- madara-skillhub ↗
- Licence
- MIT
- Last repository change
- 09.11.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 09.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Designs and builds backend APIs and services in Python or Node: routes, auth, databases, background jobs, rate limits and deployment. Use when the user asks for an API, server, bot backend, database layer, webhook handler, or help deploying a backend.
Original author description
Designs and builds backend APIs and services in Python or Node: routes, auth, databases, background jobs, rate limits and deployment. Use when the user asks for an API, server, bot backend, database layer, webhook handler, or help deploying a backend.
How it works
- Before you start
- Workflow
- Quality bar
- Output
- Avoid
- Reference
- Self-check before replying
SKILL.md preview
--- name: backend-api-builder description: "Designs and builds backend APIs and services in Python or Node: routes, auth, databases, background jobs, rate limits and deployment. Use when the user asks for an API, server, bot backend, database layer, webhook handler, or help deploying a backend." --- # Backend API builder ## Before you start Confirm four things, guessing sensibly if the user is vague: language and framework, database, where it will be deployed, and who will call the API. Default to FastAPI for Python and Express or Fastify for Node. ## Workflow 1. **Write the contract first.** List endpoints with method, path, request body, response body and error cases. Show it before writing code. 2. **Model the data.** Tables or collections, keys, indexes, and what must be unique. 3. **Build in layers.** Routes call services, services call the data layer. Keep business rules out of route handlers. 4. **Secure it.** Validate all input. Hash passwords with a proper algorithm. Keep secrets in environment variables and ship an `.env.example`. Add rate limits on auth and expensive routes. 5. **Handle failure.** Consistent error shape, timeouts on outside calls, retries only where the call is safe to repeat. 6. **Test.** Write tests for the contract: one success and the main failures per endpoint. Run them. When a test fails, fix the code, never loosen the test to make it pass. 7. **Deploy notes.** Start command, required environment variables, health check route, and the logs to watch. ## Quality bar - Every endpoint documented and every error returns a clear message and status code. - No secrets, tokens or keys in code or logs. - Database queries are parameterized. - The app starts from a clean clone with the README steps alone. - A `/health` route exists. ## Output Contract, then folder structure, then code file by file, then run and deploy steps. Keep each file complete so the user can paste it without guessing. ## Avoid - Building auth from scratch when a vetted library fits. - Storing anything sensitive in plain text. - Hidden global state that breaks when the host restarts or scales. - Claiming a deploy works without a way to check it. ## Reference Read `references/api-patterns.md` when writing the contract, choosing status codes, adding auth or rate limits, or deploying. It has the checklists, templates and worked examples for this skill. ## Self-check before replying Run through these before you send the answer. Fix anything that fails. - Does every endpoint in the contract exist in the code, with the same paths and fields? - Is every input validated and every error in the same shape? - Is any secret hard-coded, logged, or missing from `.env.example`? - Does the app bind to `0.0.0.0` and read `PORT` if it will be deployed? - Did the tests run? If a test failed, did I fix the code rather than the test? - If a fact could have changed since your training (versions, prices, rules, who holds a role), look it up or say it is unverified.
Files in this package (2)
- SKILL.md 3 KB
- references/api-patterns.md 4 KB
Versions
The database has no other skills named backend-api-builder.
Database snapshot: 13.11.2026 · package version 289e82e17f36 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes. Use when building or reviewing Node.js, Express, or Next.js API routes and their data access. - 95senior-backend
Comprehensive backend development skill for building scalable backend systems using NodeJS, Express, Go, Python, Postgres, GraphQL, REST APIs. Includes API scaffolding, database optimization, security implementation, and performance tuning. Use when designing APIs, optimizing… - 90backend-engineering
Design, implement, or review backend behavior for an application or service. Use for API routes, domain logic, persistence, authentication, background work, integrations, and reliability. - 95backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes. Use when building or reviewing Node.js, Express, or Next.js API routes and their data access. - 95backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes. Use when building or reviewing Node.js, Express, or Next.js API routes and their data access. - 90backend-craft
Backend engineering standards — API design, layering, database patterns, caching, error handling, auth, background jobs, logging, and the production-readiness checklist. Use when building any server-side code (endpoints, services, models, migrations, jobs).