← ClaudeAtlas

backend-standardslisted

Create a new backend service (NestJS / TypeScript / PostgreSQL / Redis) that follows the team's engineering standards from the first commit, or bring an existing service onto those standards. Use this whenever the user wants to start, scaffold, bootstrap, generate or set up a new backend project or microservice — including phrasings like "create a new service for X", "start a backend project", "scaffold a new API", "set up a new microservice", "build me a backend for X", or "apply our backend standards to this repo". Ships the standards as files plus real source templates (money arithmetic, distributed locks, webhook verification, pagination, sort allowlists, the exception filter) rather than describing them, because a description drifts from the code and a file does not.
YoussefRashad/backend-agent-skills · ★ 0 · API & Backend · score 72
Install: claude install-skill YoussefRashad/backend-agent-skills
# Backend Standards > **When to use:** starting a new NestJS/TypeScript service, or bringing an existing one onto the team standard. Invoke with `/backend-standards`, or a phrase like "create a new backend service for X" / "apply our backend standards to this repo". Scaffold a service that follows the team standard from the first commit, and leave behind a repo that keeps following it without anyone remembering to. The standards live in `references/` next to this skill. The files that get copied into the new project live in `templates/`. **This skill is the source of truth until these are promoted to shared npm packages.** Propagation is **pull-based**: re-run this skill on a project to sync it. Read the canonical version from `templates/version.json` — never hardcode it. --- ## Requirements ### `toolchain-config` — required ESLint, Prettier, tsconfig, Husky and lint-staged are owned by the **`toolchain-config`** skill. This skill deliberately does not ship them: two skills shipping the same eslint config is how they drift apart. It must be installed alongside this one, at `~/.claude/skills/toolchain-config/`. `toolchain-config` is an interactive **diff-and-ask** workflow with per-file approval. On a brand-new project there is nothing project-specific to preserve, so tell the person that and offer to approve the whole set at once — otherwise they answer roughly ten prompts in the middle of a scaffold. **Before step 3, check that it exists.** If it does not: > Stat