Backend Development Planning Assistant

What problem it solves

Backend requirements are rarely just “write an API”: engineers need decisions on stack, API style, auth, rate limiting, schema migration, security review, and deployment risk. This skill helps turn a clearly stated requirement into a workable BackendPlan, covering stack selection, API checklist, database and security checklist, testing strategy, and deployment approach, while reducing common anti-patterns.

How it works

It follows a six-step flow: selection matches Node.js, FastAPI, Go, or Rust stacks to development speed, concurrency, and data model needs, and pairs them with PostgreSQL, MongoDB, Redis, or Kafka; API design covers REST / GraphQL / gRPC, schema, validation, auth, rate limiting, and error codes; database covers schema, indexes, pooling, migrations, backups, and performance tests; security checks OWASP Top 10 items such as parameterized queries, OAuth 2.1 + PKCE, Argon2id, security headers, and rate limits; testing recommends unit, integration, and E2E coverage, plus contract tests for microservices; deployment covers Docker, CI/CD, blue/green or canary, feature flags, monitoring, and logs. The output is structured as {stack, api_checklist, security_checklist, test_strategy, deploy_strategy}, which downstream skills such as better-auth, databases, devops, or code-review can consume.

Boundaries

It targets backend architecture and implementation decisions, not frontend UI details or cloud console operations. It provides a plan and checklists, so concrete implementations still need validation against existing code, team conventions, and production constraints. For real-time, high-concurrency, or compliance-heavy systems, treat the security and performance lists as a baseline, not a substitute for load testing, audits, or release review.