What problem does it solve? Coding standards often decay into unread documents because nothing enforces them. This Skill writes the project's code-writing rules as a visible file where every rule carries an explicit enforcement channel, so a rule without enforcement is never written. ## Core Features & Use Cases - Enforcement-channel binding: Each rule is classified as mechanical (gate dependency/style lint such as Konsist, ArchUnit, dependency-cruiser, or import-linter), discursive (code-review criterion), or structural (citation of the owning skill or gate). - Project-level output: Produces <output_dir>/code-rules.md next to profile.md and architecture.md, with the profile's code_rules binding updated so workers and code review receive it automatically. - Delta-based updates: On later features it proposes only deltas against the existing file, keeping one source of truth. - Use Case: During the mismAgent model movement, after the user deliberates rules in the ARCH_PROPOSAL checkpoint and the stack ADR is set, the architect invokes this Skill to emit code-rules.md with lint tool and config path pinned per stack. ## Quick Start Ask the mismagent-architect during the model movement to write the project's code-rules.md from the deliberated ARCH_PROPOSAL rules after the stack ADR is decided.
