Architecture
Enforce architectural rules when generating or modifying code. Defaults to clean architecture; supports any architecture style via the architecture-refiner. Validates layer responsibilities, dependency direction, and structural constraints using the loaded architecture rules. Use when generating code, reviewing architecture, creating new files, or when the user mentions 'architecture', 'layers', 'structure', 'dependency rules', 'hexagonal architecture', 'ports and adapters', 'modular monolith', or 'onion architecture'. Also use when reviewing generated code for structural compliance.From its SKILL.md
npx -y skills add techygarg/lattice --skill architectureAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
2.8 KB, 506 tokens by cl100k_base, as published. Nobody here has run it
Architecture
Config Resolution
Step 1 — Determine mode:
- Read
.lattice/config.yamlin repo root - Check
architecture_modekey- If
architecture_mode: custom→ custom mode - If absent, or other value → clean architecture mode (default)
- If
Step 2 — Load enforce rule:
- Clean architecture mode → Read
./references/clean-architecture.mdfor enforce instruction (Self-Validation Checklist, Anti-Pattern Scan, Ambiguity Signals, structural principles) - Custom mode → Read
./references/custom-architecture.mdfor enforce instruction
Step 3 — Load architecture content:
-
Clean architecture mode:
- Check
paths.architecturein.lattice/config.yamlfor custom doc - If found, read doc and check YAML frontmatter for
mode:mode: overlay: Read./references/clean-architecture-defaults.mdfirst, 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.
- If no custom doc → read
./references/clean-architecture-defaults.md
- Check
-
Custom mode:
- Check
paths.architecturein.lattice/config.yamlfor team architecture doc - If found → read it. Sole reference — no default.
- If not found → surface: "No architecture document found. Run
/architecture-refinerand select your architecture style to define your team's standards."
- Check
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.
What ships with it: 3 files
24.1 KB alongside SKILL.md
references/
- clean-architecture-defaults.md15.3 KB
- clean-architecture.md4.9 KB
- custom-architecture.md3.9 KB
Gives 0 of the 12 instructions most architecture codebase skills give in 506 tokens
Counted across 858 of the 1,304 authors here whose files we hold, read 2026-09-06
- Apply the deletion test to identify shallow modulesin 32 of 858, across 31 files
- Read domain glossary and ADRs before exploringin 22 of 858, across 19 files
- Use Tailwind and Mermaid via CDN for reportsin 21 of 858, across 18 files
- Document architecture decision recordsin 20 of 858, across 12 files
- Offer to record ADRs for rejected candidatesin 17 of 858, across 14 files
- Limit primary navigation to four to seven itemsin 17 of 858, across 7 files
- Write HTML report to the system temp directoryin 17 of 858, across 14 files
- Read product marketing context before asking questionsin 16 of 858, across 6 files
- Use Mermaid graph TD for visual sitemapsin 15 of 858, across 5 files
- Ensure every page has at least one internal linkin 15 of 858, across 5 files
- Use ASCII tree format for page hierarchy draftsin 15 of 858, across 5 files
- Enforce lowercase URLs with hyphensin 15 of 858, across 5 files
Said here and by no other author read
- Read configuration file for architecture mode
- Load enforcement rules based on mode
- Load architecture content documentation
- Adapt dependency enforcement to language idioms
- Stop after generating each component
- Apply self-validation checklist
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.