Content
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable orchestration skill: concrete API patterns, a rigorous phased workflow with validation checkpoints, and excellent progressive disclosure via a reference table pointing to real bundle files. The main weakness is conciseness — substantial rule overlap between the Critical Rules and Anti-Patterns sections inflates the body without adding new guidance.
Suggestions
Deduplicate the rules shared between Section 3 (Critical Rules) and Section 9 (Per-Phase Anti-Patterns) — parallelizing use_figma calls, hallucinating node IDs, building on unvalidated work, and variant-per-icon all appear in both — by stating each rule once and cross-referencing it from the anti-patterns list.
Compress the Section 1 communication contract from prose bullets into a compact format template (checklist header, 'Working on Phase N.X' line, summary fields) to cut tokens while preserving the contract.
Trim the inline Section 7 naming examples and Section 8 token-architecture table to one-line pointers to naming-conventions.md and token-creation.md, since those references already hold the full detail.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is detailed and assumes Claude's competence (it never explains what Figma or design systems are), but it carries real redundancy — parallelizing use_figma calls, hallucinating node IDs, building on unvalidated work, and variant-per-icon each appear in both Section 3 (Critical Rules) and Section 9 (Anti-Patterns) — so it is mostly efficient but could be tightened, matching the score-2 anchor rather than the lean score-3 anchor. | 2 / 3 |
Actionability | Concrete and executable throughout: exact scope values ('FRAME_FILL, SHAPE_FILL'), the var() code-syntax rule ('var(--color-bg-primary)'), alias objects ('{ type: "VARIABLE_ALIAS", id: primitiveVar.id }'), a state-ledger JSON schema, a disk path ('/tmp/dsb-state-{RUN_ID}.json'), and pointers to 9 real helper scripts — matching the score-3 anchor for fully executable, copy-paste-ready guidance. | 3 / 3 |
Workflow Clarity | Phases 0–4 are ordered with per-phase exit criteria, mandatory checklists ('Phase N Checklist'), explicit validation checkpoints ('get_metadata after every create, get_screenshot after each component'), and an error-recovery reference — matching the score-3 anchor for a clear sequence with explicit validation and feedback loops. | 3 / 3 |
Progressive Disclosure | The body is an overview that signals one-level-deep references via the Section 10 table (Doc | Phase | Required/Optional | Load when) and Section 11 script table; all 7 referenced docs and 9 scripts are real files, content is appropriately split, and navigation is easy — matching the score-3 anchor judged against the actual bundle structure. | 3 / 3 |
Total | 11 / 12 Passed |