036bc6a52e
Group G — markdown tech-debt cleanup (post-audit 2026-05-02).
- 36 SKILL.md files: added "## When to use" section. Was missing across the
catalog; orchestrator routing by keyword could not auto-dispatch.
- 20 code-implementer agent .md files: added Output Footer block prescribing
RULE 0.16 STATUS-TRUTH MARKER schema in agent's final report. Previously only
code-implementer-rust.md had it; other 27 language/role variants were silent
about the marker, breaking RULE 0.16 §3 status-truth aggregation for non-Rust
batches.
- skills/site-create/: added phase-5-preview.md and phase-6-deploy.md skeleton
files. SKILL.md table-of-contents referenced 7 phases; only 5 existed on disk.
- skills/{ai-animation,rag-pipeline}/skill.md: added migration banner comment
noting they should be SKILL.md (canonical filename). Case-rename via git is a
separate orchestrator task (macOS APFS is case-insensitive; Linux deploy needs
explicit rename).
- 3 deprecated skills (site-builder, competitor-analysis, design-inspiration):
added concrete removed-after dates (was vague "before v2").
- docs/CONVERGENCE-PLAN.md:129: TBD on _blocks/evidence-grading.md duplicate
resolved (file exists, not duplicated).
- docs/DNA-INDEX.md: count edits made then overwritten by auto-encyclopedia-refresh
hook during agent run. The .kei-registry-ignore files in test fixtures (Group F)
are the structural fix; kei-registry walker implementation is the follow-up.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
27 lines
1.6 KiB
Markdown
27 lines
1.6 KiB
Markdown
---
|
|
name: architecture-rules
|
|
description: Architectural rules engine — pattern validation, duplication detection, stack compatibility, and design pattern enforcement. Auto-triggers during code review, architecture planning, and when creating new modules. Triggers on "проверь архитектуру", "review architecture", "check patterns", "проверь дублирование", "stack compatibility".
|
|
user-invocable: false
|
|
---
|
|
|
|
# Architecture Rules Engine
|
|
|
|
## When to use
|
|
|
|
- Validating an architectural decision against Constructor Pattern rules, duplication limits, or stack compatibility.
|
|
- Loaded automatically by `architecture`, `debug-deep`, and code-review skills — not normally invoked directly.
|
|
- Running a pre-implementation checklist before writing a new module or dependency.
|
|
|
|
This skill provides the rules database for architectural validation.
|
|
It is loaded by other skills (architecture, debug-deep, code-review) when they need to validate decisions.
|
|
|
|
## How to Use
|
|
|
|
When analyzing code or planning architecture, load and apply rules from:
|
|
- `~/.claude/skills/architecture-rules/references/patterns.md` — design patterns catalog
|
|
- `~/.claude/skills/architecture-rules/references/antipatterns.md` — what to avoid
|
|
- `~/.claude/skills/architecture-rules/references/stack-compat.md` — technology compatibility matrix
|
|
- `~/.claude/skills/architecture-rules/references/duplication.md` — duplication detection rules
|
|
- `~/.claude/skills/architecture-rules/references/checklist.md` — pre-implementation checklist
|
|
|
|
For each architectural decision, validate against these references and report violations.
|