Skip to content

slight76/architecture-standards

v1.0.1MIT

Team architecture standards: solution design, frontend/backend architecture, CQRS, middleware, OpenAPI, HTTP APIs, contracts, messaging, and the ADR process.

architecture-standards

Team architecture standards for developers and AI agents: solution design, frontend and backend architecture, CQRS, middleware, OpenAPI, HTTP APIs, contracts, messaging and resilience, and the architecture decision record (ADR) process.

Part of the Slight76 standards handbooks indexed at standards-marketplace alongside engineering, operations, data, and security. Written for a small team and its agents. Version 1.0.0 is the first release after the repository split; see CHANGELOG.md and MOVED.md.

Documents

DocumentCoversRule prefixes
Architecture principlesThe principles every handbook specialises-
Solution architectureMapping one outcome to applications, stores, and boundariesSA
Solution design and production readinessWhat a solution document must decide before productionSA
Frontend architectureIndependent SPA structure, state, routing, API accessFE
Accessible and resilient user interfacesAccessibility, performance budgets, failure statesUX
Backend architectureUse-case oriented services, boundaries, ownershipBE
CQRS and application executionCommand/query separation, handlers, pipelinesCQRS
HTTP middleware and host compositionMiddleware order, lifetimes, errors, security headersMW
OpenAPI generation and Swagger UIFirst-party OpenAPI, transformers, exposureOAS
Integration architectureSynchronous vs asynchronous integration, ownershipINT
HTTP API designResource-oriented APIs, versioning, errors, paginationAPI
Contract ownership, generation, and compatibilityOwned contracts, generated clients, compatibilityCON
Idempotency, messaging, and resilienceReplay, delivery semantics, retries, timeoutsEVT, RES
Architecture decision recordsWhen and how to write an ADR, where it lives, lifecycle-
Architecture views with C4Which diagrams to produce and how-
Architecture styles and trade-offsModular monolith default, when to split, checklist-
Service boundaries referenceFinding, enforcing, and promoting boundaries-
ExamplesWorked solution examples (inventory, stock adjustment)-
ADR indexAll decisions, including historic ADR-0001..0027 and the v1.0.0 split (ADR-0028..0031)-

Read by task

See skills/architecture-standards/SKILL.md. For tasks outside architecture (branching, tests, CI/CD, schemas, auth) start at the marketplace routing table.

Install as an agent skill

AgentCommand
Copilot CLIcopilot plugin marketplace add Slight76/standards-marketplace then copilot plugin install architecture-standards@slight76-standards
GitHub CLI (any agent)gh skill install Slight76/architecture-standards architecture-standards --scope user --pin v1.0.0
Claude Code/plugin marketplace add Slight76/standards-marketplace then /plugin install architecture-standards@slight76-standards

Application repositories pin this handbook in architecture-baseline.json (standards[], schema v2); see the marketplace consumer kit.

Layout

PathPurpose
docs/Standards documents (frontmatter, applies-when, rule table)
catalog/catalog.jsonMachine-readable rules for this handbook; externalDecisions points at marketplace ADR-0001
adr/Architecture decision records (the team's ADR history lives here)
skills/architecture-standards/Agent skill and references
templates/solution-architecture.mdSolution document template (shared templates live in the marketplace)
governance/migration-*.mdHistoric migration notes for 0.2 and 0.3

Validation: py ../standards-marketplace/tooling/validate.py --root . (CI runs the same through the reusable marketplace workflow). License: MIT.