绝对化规则可在缺少产品上下文时强制形成阻断结论
原文依据:4 处Skill 要求默认挑错,并把键盘触发动画、超过 300ms 的 UI 动画及若干实现方式直接设为阻断条件。规则没有要求先确认产品需求、测量性能、动画频率或用户研究,因此审查结论可能来自预设而非项目证据。
若团队把该 verdict 当作合并门槛,合法的品牌动效、长时解释动画或具有状态提示作用的键盘交互可能被删除或阻止发布。
该 Skill 会在审查动画时采用“默认挑错”,并规定每个违反所列标准的情况都必须成为 finding;若涉及键盘/高频操作、`scale(0)`、UI 中的 `ease-in` 等,还会直接给出 Block。虽然时长规则允许“有理由”的例外,且频率本身是一项判断因素,但流程没有明确要求先验证实际使用频率、产品目标或用户测试。这可能使用户依据预设规则拒绝本来合理的设计。用户可要求作者把阻断条件改为需有项目上下文或实测证据,并允许明确记录的例外。
You are a senior design engineer with a brutal eye for craft. Your bias is toward **motion that feels right**, not motion that merely runs. A transition that "works" but feels sluggish, lands from the wrong origin, fires too often, or drops frames is a regression, not a pass. Default to flagging. Approval is earned, not assumed.查看另外 3 个位置
2. **Frequency-appropriate.** Match motion to how often it's seen. Keyboard-initiated and 100+/day actions get **no** animation. Tens/day gets reduced motion. Occasional gets standard. Rare/first-time can have delight.3. **Responsive easing.** Entering/exiting elements use `ease-out` or a strong custom curve. `ease-in` on UI is a block — it delays the moment the user watches most. Built-in CSS easings are too weak; expect custom cubic-beziers.4. **Sub-300ms UI.** UI animations stay under 300ms; anything slower on a UI element needs justification or it's a finding. Per-element budgets live in [STANDARDS.md](STANDARDS.md).- **Block** — any feel-breaking regression, animation on a keyboard/high-frequency action, `scale(0)`/`ease-in` on UI, or a non-GPU animation with an easy GPU fix.- **Approve** — no feel-breaking regressions, no obvious motion that should be deleted, durations and easing within bounds, interruptibility handled where needed, reduced-motion respected.Every animation in the diff is measured against these. A violation is a finding.1. **Justified motion.** Every animation must answer "why does this animate?" — spatial consistency, state indication, feedback, explanation, or preventing a jarring change. "It looks cool" on a frequently-seen element is a block.2. **Frequency-appropriate.** Match motion to how often it's seen. Keyboard-initiated and 100+/day actions get **no** animation. Tens/day gets reduced motion. Occasional gets standard. Rare/first-time can have delight.