architecture-refiner

Defining architecture principles requires a structured interview where you provide project context and a chosen style to produce a formal standards document. The Skill supports clean architecture, hexagonal, modular monolith, or custom styles and outputs the result to .lattice/standards/architecture.md.

Setting up hexagonal architecture involves specifying the ports and adapters style to generate formal documentation with style-specific guidance. You provide YAML frontmatter containing your project name and description to produce a ready-to-use architecture principles document.

Yes, you can define a custom architecture style by specifying it in your input. The Skill generates a formal architecture document with architecture_mode set to custom, providing tailored guidance for your non-default design principles and repository standards.

The input requires a YAML frontmatter containing your project name and description, along with optional resource folders for scripts, references, and assets. This input drives the structured interview to produce your formal architecture document.

You should skip guided architecture refinement if your repository already has a formal architecture document with established design principles. The process is intended for setting up new projects, defining standards, or transitioning to styles like hexagonal or modular monolith.