design-direction-lock
防止实现过程中的隐式重设计，保持产品视觉与交互一致性。
固化规则可能阻碍必要的小范围调整，需设定变更流程。
将收敛的设计方向固化成规范文档并在相关 issue 中标注锁定版本。
把已收敛的设计方向固化成一份简短规范（docs/design-direction.md），并在相关 issue 上标注锁定的版本号与适用规则。适合在设计评审达成一致、准备交付给实现团队或代理执行时使用。好处是防止后续实现时的“悄悄重设计”，通过锁定修订号让后续工作按既定视觉语言和运动规则执行。
▸ 展开 SKILL.md 英文原文
After a design direction has converged through mockup iteration, freeze it into a short normative artifact (docs/design-direction.md) carrying the references, visual language, motion rules, and product truths — then stamp every design-facing issue with the lock revision and only the rules that apply to that issue's surface, so implementing agents (especially cheaper ones) implement the approved direction instead of re-designing it. Use at the moment design review rounds converge on an approved direction, and again whenever the direction deliberately changes (a new lock revision, never silent drift). Pairs with agent-tiered-planning (the stamp is what makes design-facing work safe for standard-tier agents).
帮我安装这个 skill：https://raw.githubusercontent.com/boshuthebuilder/ai-tradecraft-skills/main/plugins/coding/skills/design-direction-lock/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/boshuthebuilder/ai-tradecraft-skills/main/plugins/coding/skills/design-direction-lock/SKILL.md"# design-direction-lock Design converges in one place — a mockup review thread, a pair of eyes, a run of iterations — and then dozens of issues implement it in many places, often executed by agents that never saw the iteration. Without a lock, every one of those agents quietly re-designs: each PR drifts a little toward what its model *would have* designed, review rounds burn on re-litigating settled choices, and the product's visual identity dissolves into plausible-but-wrong. The lock converts taste into a **normative artifact**: decided once, referenced everywhere, versioned when it changes. This is the same principle as agent-tiered-planning — **move judgment upstream into artifacts** —