菜单
Use when Phase 4 Review checks architectural integrity, the user asks to "check for violations" or "find circular deps", or before a release. Detects orphans, layer violations, circular dependencies, and hotspots; build-loop's native rules engine from NavGator.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Compose a complete, durable build-loop handoff document from the current run state, and optionally launch a fresh session with it injected. Use when crossing a context boundary (context limit, planned restart, worktree GC). Triggers: 'hand off', 'handoff', 'new session', 'context limit', 'restart', 'fresh session', '/build-loop:compose-handoff'.
Use when build-loop needs UI design direction, visual style selection, UI guidance inventory, a .build-loop/app-contract/ui.md design contract, or non-trivial web/mobile/native UI planning. Build-loop-owned design route for design-contract-specialist; selects from project tokens, recent structures, UI Guidance, IBR artifacts, Mockup Gallery, and research based on product/workflow/data/platform fit.
Generate accessible color systems and solve contrast, instead of guessing hex values. Use when picking or fixing colors for any UI, chart, diagram, doc, or artifact — "what colors should this use", "is this readable", "this text fails contrast", "make a dark theme", "pick an accent". Also use before shipping any palette, to PROVE contrast rather than assert it. NOT for choosing layout, typography, or component structure.
Use when a Build Loop run or Git worktree touches mutable non-Git state: SQLite or file-backed databases, PostgreSQL databases/schemas and migrations, generated search/vector indexes, Docker volumes or service projects, mutable file trees, caches that cannot be rebuilt safely, or external cloud/account namespaces. Inventories each surface, selects per-worktree, shared-readonly, shared-serialized, or external-namespaced isolation, registers it in the run data manifest, validates collisions before writes, and requires a terminal disposition at closeout.
Use when choosing a model tier or segment for a subagent, deciding a role descriptor (segment + tier) in frontmatter, or escalating mid-flow. Covers the two-axis taxonomy (work-role segment × 7-rung capability ladder) — Opus/Sonnet/Haiku are Anthropic-default mappings; selection is provider-portable and data-driven. NOT for benchmarking models head-to-head on a task — use `model-bakeoff`.
Orchestrated build loop for multi-step code work. TRIGGER on verb language ('build', 'implement', 'create', 'add', 'ship', 'wire up', 'integrate', 'refactor', 'migrate', 'rewrite', 'replace') OR symptom language ('fix', 'broken', 'doesn't work', 'isn't loading', 'not displaying', 'missing', 'should show', 'needs to', 'make it', 'show this differently') OR any task touching 2+ files, adding/removing an endpoint, crossing an architectural boundary, or attached screenshots of a bug. SKIP one-line edits, pure Q&A, conversational clarifications, status checks, and trivial typos/renames.
| name | build-loop:architecture-rules |
| description | Use when Phase 4 Review checks architectural integrity, the user asks to "check for violations" or "find circular deps", or before a release. Detects orphans, layer violations, circular dependencies, and hotspots; build-loop's native rules engine from NavGator. |
| version | 0.1.0 |
| user-invocable | false |
| source | NavGator/commands/test.md |
| source_hash | 4a967c08ff3d7cddd408e7caefcd07b09e8931bcaccf9ea70c0f5aa94349e0d1 |
Run NavGator's rules engine to detect architectural violations using the mcp__plugin_navgator__rules MCP tool. Classifies findings as blocking (circular dependency, layer violation, database isolation breach, frontend-direct-DB at error level) vs warning (hotspot, high-fan-out, orphan, shallow-module).
Divergence note: NavGator has no discrete SKILL.md for rules. The canonical wrapper is
commands/test.md, which orchestratesnavgator rules+navgator dead+ pipeline traces. This skill extracts the rules-only workflow.
.navgator/architecture/index.json does not exist → no-op with NavGator: no architecture snapshot found — skipping rules check. Recommend build-loop:architecture-scan.index.json generated_at timestamp. If >24 hours old, warn: "Architecture data is N hours old — consider running build-loop:architecture-scan first for accurate results."mcp__plugin_navgator__rules (or navgator rules --json)| Severity | Categories |
|---|---|
| Blocking | circular-dependency, layer-violation, database-isolation, frontend-direct-db (error level) |
| Warning | hotspot, high-fan-out, orphan, shallow-module (thin pass-through: high fan-out, low fan-in — advisory design guidance, never blocks) |
.build-loop/state.json.architecture.rules.baseline.navgator/lessons/lessons.json (lessons with matching signature).build-loop/state.json.architecture.rules with {blocking_count, warning_count, new_violations[], recurrences[]}.build-loop/issues/ and surface in Review-F ReportARCHITECTURE RULES
==================
Blocking: N (N new this build)
Warnings: N (N new this build)
Recurrences against lessons: N
[BLOCKING] Layer violation: ComponentA (frontend) → ComponentB (database)
File: src/pages/users.tsx:45
Recurrence: matches lesson 'frontend-direct-db' (last seen 2026-03-15)
If no findings: report "No connection-integrity issues found" — do not omit the section.
build-loop:architecture-scan — refresh data firstbuild-loop:architecture-impact — pre-flight blast-radius for any blocking finding's affected componentbuild-loop:architecture-dead — orphan-only scan (warnings flagged here too)build-loop:architecture-review — runs rules as part of a 5-phase integrity reviewSource: NavGator commands/test.md (the orchestrator that calls navgator rules). The canonical rules engine is the MCP tool. Drift-checked by build-loop:sync-skills.