architecture

Featured

Enforce architectural rules when generating or modifying code, and validate proposed designs before approval (design mode). 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.

AI & Automation 190 stars 13 forks Updated 4 days ago MIT

Install

View on GitHub

Quality Score: 88/100

Stars 20%
76
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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 a custom document path. 2. If a document exists at that path → read it and check its YAML frontmatter for `mode`: - **`mode: overlay`** (or no mode field): read `./references/clean-architecture-defaults.md` first, then apply the custom document's sections on top. Sections match by exact heading — a custom section replaces the matching default; new sections append after the defaults. - **`mode: override`**: the custom document takes full precedence. It must be comprehensive. 3. If the path is configured but no document exists at it → tell the user which configured path is missing, then read `./references/clean-architecture-defaults.md`. 4. If there is no configured path → read `./references/clean-architecture-defaults.md`. - **Custom mode:** 1. Check `paths.a...

Details

Author
techygarg
Repository
techygarg/lattice
Created
6 months ago
Last Updated
4 days ago
Language
JavaScript
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category