backend-architecture
Backend Architecture
Use this skill for TypeScript and Node.js backend work. It is framework-neutral: apply it to Fastify, Express, Hono, Workers, queues, CLIs, SDKs, database packages, integration modules, and service packages by mapping the same responsibilities to the local framework.
First Move
Before changing code:
- Read repo guidance first:
AGENTS.md, package READMEs, existing conventions, local test setup, and nearby code. - Inspect the current package layout, imports, naming, server entrypoints, db/repo code, helpers, and tests.
- Prefer existing repo conventions when they are clear. Use this skill as the default for new code, ambiguous code, or code that needs architectural cleanup.
- Search before creating a new helper, service, schema, repository, middleware, or shared type. Consolidate similar code instead of adding another near-duplicate.
- Identify the canonical source of truth for contracts and generated files before editing schemas or DTOs.
Default posture: boundaries early, implementations lean.
Core Principles
More from we-are-singular/skills
frontend-architecture
Use when writing, reviewing, or refactoring TypeScript frontend code, including React components, Astro or Next.js apps, shared UI packages, client state, server-state fetching, forms, styling systems, routing, analytics, frontend tests, and frontend architecture decisions.
3git-commit-pr
Use when preparing local changes for commit, push, and pull request creation, especially in repositories that use conventional commits, package/workspace scopes. This skill optimizes for clean history, package-scoped commits, repository-specific rules, and a PR body that explains intent.
2