odui-check

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Check Open Design UI compliance

检查 Open Design UI 合规性

This Skill is read-only unless a failing check is being fixed. Read AGENTS.md, the component guide,
registry.json
and the affected source files.
  1. Run
    npm run design:check
    . It checks token freshness, theme parity, contrast, import boundaries, native-control baselines and registry adoption.
  2. For component changes also run
    npm run components:build
    ,
    npm run typecheck:studio
    and the focused tests. Use
    npm run check
    for the repository gate when the change touches shared rules or configuration.
  3. Inspect the real catalogue route in both themes. Check focus, disabled/loading, keyboard behavior, accessible names, narrow widths and console errors. A green static check does not replace browser inspection.
  4. Confirm every registry item has a source, alias, example, API notes, real Studio consumer and an adoption decision. An opt-in item needs a review condition. An enforced item needs a matching native rule.
  5. Report each finding with the file, the violated rule, the smallest repair and the exact check that remains.
Do not lower a baseline to hide an un-migrated control. Do not mark a component enforced before a real consumer has been verified.
此 Skill 为只读,除非正在修复失败的检查项。阅读 AGENTS.md、组件指南、
registry.json
以及受影响的源文件。
  1. 运行
    npm run design:check
    。它会检查令牌是否最新、主题一致性、对比度、导入边界、原生控件基线和注册表采用情况。
  2. 对于组件变更,还要运行
    npm run components:build
    、
    npm run typecheck:studio
    和针对性测试。如果变更涉及共享规则或配置,使用
    npm run check
    作为仓库门禁。
  3. 在两种主题中检查真实的目录路由。检查焦点、禁用/加载状态、键盘行为、可访问名称、窄宽度和控制台错误。静态检查通过并不能替代浏览器检查。
  4. 确认每个注册表项都有源文件、别名、示例、API 说明、真实的 Studio 使用方和采用决策。opt-in 项需要审查条件。enforced 项需要匹配的原生规则。
  5. 报告每个发现项,包括文件、被违反的规则、最小修复方案以及仍需进行的确切检查。
不要降低基线来掩盖未迁移的控件。在真实使用方得到验证之前,不要将组件标记为 enforced。