Architecture

Architecture

Config Resolution

Step 1 — Determine mode:

1. Read .lattice/config.yaml in repo root
2. Check architecture_mode key

• If architecture_mode: custom → custom mode
• If absent, or other value → clean architecture mode (default)

Step 2 — Load enforce rule:

• Clean architecture mode → Read ./references/clean-architecture.md for enforce instruction (Self-Validation Checklist, Anti-Pattern Scan, Ambiguity Signals, structural principles)
• Custom mode → Read ./references/custom-architecture.md for enforce instruction

Step 3 — Load architecture content:

• Clean architecture mode:

1. Check paths.architecture in .lattice/config.yaml for custom doc
2. If found, read doc and check YAML frontmatter for mode:

• mode: overlay: Read ./references/clean-architecture-defaults.md first, then apply custom doc section on top. Section match by heading — custom section replace matching default, new section append.
• mode: override: Custom doc take full precedence. Must be comprehensive.

1. If no custom doc → read ./references/clean-architecture-defaults.md

• Custom mode:

1. Check paths.architecture in .lattice/config.yaml for team architecture doc
2. If found → read it. Sole reference — no default.
3. If not found → surface: "No architecture document found. Run /architecture-refiner and select your architecture style to define your team's standards."

Step 4 — Language adaptation:

If paths.language_idioms exist in config, read "Dependency Management" section and adapt dependency direction enforcement to language idioms (e.g., Go interface-at-consumer, Java DI containers, Rust trait bounds). Language idioms take precedence over pseudocode defaults.

Enforcement

STOP after generate each component. Read Self-Validation Checklist and Anti-Pattern Scan from loaded enforce rule (clean-architecture.md or custom-architecture.md) and apply.

Project-specific checks: If architecture content doc (loaded in Step 3) contains a Validation Checklist section (§6), apply those checks as additional project-specific validation after the enforce rule checklist.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: techygarg
• Source: techygarg/lattice
• License: MIT

Install and usage instructions live in the source repository linked above.