t-demo-accept
Validate demo tests cover user stories, compile and pass, and output structured acceptance reports.
Profile →npx skills add timzaak/web-dev-skills --skill t-demo-accept --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.
# Demo 测试验收 运行时边界统一参考：`${CLAUDE_PLUGIN_ROOT}/protocols/runtime-boundaries.md` 需求来源边界统一参考：`${CLAUDE_PLUGIN_ROOT}/protocols/requirement-source-contract.md` ## 目标 - 验证测试是否覆盖用户故事。 - 验证测试是否可编译、可运行且全部通过。 - 输出结构化验收报告到 `.ai/quality/`。 ## 参数 ```bash /t-demo-accept [target] ``` `target` 说明： - 测试文件路径：`demo/e2e/<role>/<scenario>.e2e.ts` - 角色名：按目标项目 `demo/e2e/` 下的实际角色目录匹配 - `all` 或留空：验收全部 Demo 测试 ## 执行流程 - 识别目
What does the t-demo-accept skill do?
Validate demo tests cover user stories, compile and pass, and output structured acceptance reports.
How do I install it?
Run `npx skills add timzaak/web-dev-skills --skill t-demo-accept --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.