Backend Architecture

When to use

Invoke after system-design has produced an approved system design and before implementation-specific skills generate code, schemas, tests, or deployment assets.

Use this skill to turn high-level system architecture into backend implementation direction: service responsibilities, domain boundaries, interface contracts, execution flows, consistency rules, security touchpoints, and operational expectations.

Do not use for framework scaffolding, database-specific schema design, frontend state/rendering architecture, Kubernetes manifests, CI/CD pipelines, or broad system topology decisions that still belong in system-design.

Inputs

Required:

• Approved system-design.md.
• Relevant ADRs from the system design.
• Target backend component, service, bounded context, or module.
• Primary consumers and upstream/downstream dependencies.