t-design-check
Evaluate technical design documents for implementability, completeness, and consistency with a quantitative 100-point score.
Profile →npx skills add timzaak/web-dev-skills --skill t-design-check --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 技术设计质量检查 运行时边界统一参考：`${CLAUDE_PLUGIN_ROOT}/protocols/runtime-boundaries.md` 需求来源边界统一参考：`${CLAUDE_PLUGIN_ROOT}/protocols/requirement-source-contract.md` 决策连续性和用户决策暴露统一参考：`${CLAUDE_PLUGIN_ROOT}/protocols/decision-continuity-contract.md` ## 目标 - 评估技术设计文档的可实施性、完整性与一致性。 - 给出可复查的 100 分量化结果。 - 输出 P0/P1/P2 修复清单。 - 给出明确的设计质量检查结论；本检查为可选，不作为 `/t-task` 的硬性前置。 - 发现必须由用户裁决的设计问题时，使用 `AskUserQuestion` 阻塞式提问，不得只写
What does the t-design-check skill do?
Evaluate technical design documents for implementability, completeness, and consistency with a quantitative 100-point score.
How do I install it?
Run `npx skills add timzaak/web-dev-skills --skill t-design-check --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From timzaak/web-dev-skills, a repository with 55 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.