BF design-spec-personal
生成并验证 UI 设计交付物:可交互 preview.html、annotated.html、tokens.css、spec.json 与 assumptions.log。支持文字、截图、Sketch、Figma 输入,以及 mobile-h5/web-pc 平台;按需加载 universal、内置或用户导入的 design profile,执行组件路由、场景模板、token 约束、静态 QA 和 真实浏览器验收。支持 W3C/Style Dictionary Token 导入。用户要求设计稿、原型、UI、页面设计、视觉稿、交互稿、design、prototype、 mockup、wireframe、hi-fi、设计还原、design token、annotated spec、d2c、Ant Design、antd、 antd-mobile、Arco Design、Arco、中后台或移动端 H5 时使用。
生成并验证 UI 设计交付物:可交互 preview.html、annotated.html、tokens.css、spec.json 与 assumptions.log。支持文字、截图、Sketch、Figma 输入,以及 mobile-h5/web-pc 平台;按需加载 universal、内置或用户导入的…
As a process F 49/100 · Will not run — References files that are not bundled: design-system/universal/tokens.css, design-system/universal/component-tokens.css, design-system/standards/ant-design
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 23. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: design-system/universal/tokens.css - warning
missing-refreference to a missing file: design-system/universal/component-tokens.css - warning
missing-refreference to a missing file: design-system/standards/ant-design
Process rating: all ten parameters 49/100
- 0Tools and files. 3 referenced file(s) missing: design-system/universal/tokens.css, design-system/universal/component-tokens.css, design-system/standards/ant-design
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 3 mutating operations with no state check
- 40Consistency. Frontmatter name (design-spec-personal) differs from the folder (design-hiker-skill)
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 26 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Execution cost. Instruction body is 1546 tokens
- 100Progress reporting. Reports progress
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 408: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 26 items
- +3Output format is stated explicitly
- +4Has examples (7 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.