reference-architecturelisted

Use when designing a new service or judging an existing repo against the estate's architecture. The 15 numbered principles (P1-P15) and the compliance checklist: Aspire AppHost as composition root, shared kernel not shared domain, service and database per bounded context, migrated persistence, environment configuration with platform secrets, one container per service, cost-shaped Fly.io topology, degrading optional dependencies, Program.cs as a manifest, interface-plus-registration extensibility, anti-corruption at the edge, tag-driven CI/CD, testing at the layer that holds the logic, in-repo documentation, and observability as a build-time decision. Read this before re-deriving any architectural rule.
konradcinkusz/architecture-standards · ★ 0 · DevOps & Infrastructure · score 72

Install: claude install-skill konradcinkusz/architecture-standards

# The Reference Architecture **Read [`references/00-REFERENCE-ARCHITECTURE.md`](references/00-REFERENCE-ARCHITECTURE.md) before applying any of this.** That file is the standard; everything below it is a summary to help you decide whether this skill applies and to check your work afterwards. Reference-architecture principles: P1-P15. ## What this standard covers - How worked examples are cited - The shape in one picture - Principles - Where the two repositories disagree, and who wins - Known open deviations - Deliberate non-goals of this blueprint ## Checklist Any service claiming to follow this blueprint answers yes to all of these: - [ ] Declared in the AppHost with `WithReference`, `WaitFor` and `WithHttpHealthCheck` - [ ] Calls `AddServiceDefaults()` and `MapDefaultEndpoints()` - [ ] Exposes `/health` and `/alive`; the platform health check points at `/health` - [ ] Emits OTLP traces, metrics and logs - [ ] Owns its database; no other service connects to it - [ ] Schema applied by `MigrateAsync` from provider-specific migrations, in a hosted service - [ ] All configuration from environment variables; no secret in source, config file, or comment, with a secret scanner in CI - [ ] Exactly one service holds a signing key; all others validate against its JWKS endpoint - [ ] The shared kernel holds no entity, DTO, enum, seed dataset, pricing constant or user-facing string — asserted by an architecture test and a CI size check - [ ] Every optional integration has a worki