What problem does it solve? Teams often capture domain decisions in CONTEXT.md glossaries, ADRs, and grill-with-docs notes, but that knowledge stays in prose instead of being enforced by the type system and module graph. This Skill codifies approved documentation into compiling typed architecture before any business behavior is written. ## Core Features & Use Cases - Fact extraction and ambiguity gating: Builds a fact table from CONTEXT.md, ADRs, and grill notes, then asks one concrete question whenever docs and code conflict on naming or structure. - Typed architecture generation: Produces domain types, discriminated unions, smart constructors, service seams, typed error families, production/test adapter slots, and call stacks following project conventions. - Dependency enforcement: Adds architecture tests, lint rules, or import-boundary checks so module dependency direction is mechanically verified. - Use Case: After a grill-with-docs session clarifies a link catalog domain, use this Skill to generate the LinkCatalog service seam, branded slug types, memory and Durable Object adapters, and import-boundary checks — while explicitly leaving business logic unimplemented. ## Quick Start Ask the assistant to convert the approved CONTEXT.md and ADR decisions for a domain into typed architecture with seams, adapters, and dependency checks, without implementing business behavior.
