Content
78%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
An exceptionally lean and actionable body: tight rules, concrete commands, a clear branch-selection workflow with defaults, and an explicit capture step. The one significant defect is that both referenced branch files (LOGIC.md, UI.md) are missing from the bundle, leaving the skill's core branch-specific guidance dangling.
Suggestions
Ship LOGIC.md and UI.md in the skill bundle (or inline their essential content) — the body delegates each branch's build detail to files that do not exist, so following either link leads nowhere.
Add an explicit verification checkpoint before the capture step (e.g., how to confirm with the user that the design question is answered before folding the decision into real code).
Include one minimal executable skeleton (e.g., the single-HTML-file scaffold or the route-with-search-param switcher) so the launch story is copy-paste ready rather than descriptive.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | "Prototype 是用来回答一个问题的 throwaway code。问题决定形状。" — the body is dense, directive prose with zero padding; it never explains concepts Claude already knows (routing conventions, task runners are referenced, not taught). Every sentence carries instruction or decision rationale. | 5 / 5 |
Actionability | Concrete commands and mechanics throughout: "`pnpm <name>`、`python <path>`、`bun <path>`", "URL search param 和浮动底栏", "带有清晰 'PROTOTYPE, wipe me' 名称的本地文件", "commit 到 main 之外的 throwaway branch". Not 5: no complete executable example in the body, and the branch-specific build detail is delegated to referenced files. | 4 / 5 |
Workflow Clarity | Clear sequence: identify the question → choose a branch (with an explicit default heuristic and assumption disclosure for ambiguous cases) → apply the six common rules → capture the verdict. Rule 5 ("每次 action 或 variant switch 后，打印或渲染完整相关 state") is an explicit feedback mechanism. Not 5: the verify-before-capture checkpoint is only implied by "验证过的 decision" — how to confirm the question is answered before folding decisions into real code is not spelled out. | 4 / 5 |
Progressive Disclosure | The two references ([LOGIC.md](LOGIC.md), [UI.md](UI.md)) are well-signaled, tied directly to the branch questions, and one level deep — but neither file exists in the bundle (no references/, scripts/, or assets/ directories, and a filesystem search finds no LOGIC.md or UI.md). The delegated branch detail is unreachable, breaking navigation despite good structure. | 3 / 5 |
Total | 16 / 20 Passed |