Content
82%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.
A tight, configuration-dense body that sequences the pipeline clearly and includes an explicit critique feedback loop with a termination condition. Its main weaknesses are prose-described rather than snippet-complete GenUI configs and dangling spec citations with no bundled document behind them.
Suggestions
Ship the spec sections cited ('§10.3.1', '§21.3.1', etc.) as a bundle reference file, or inline the one or two rules actually needed — currently the citations are unresolvable dead ends.
Provide the two GenUI surfaces as complete config snippets (like the pipeline block) instead of field-value prose, so the plugin layer can be implemented copy-paste.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~40-line body is lean and dense: 'the canonical figma-migration flow. The pipeline is sequenced so each stage's output is the next stage's input' plus concrete artifact paths, with zero concept over-explanation or padding. Matches the 'lean and efficient; every token earns its place' anchor, not 4 because there is no over-explanation left to trim. | 5 / 5 |
Actionability | The pipeline JSONC block ('stages', atom lists, repeat/until) is copy-paste ready, and the surfaces section gives concrete field values ('oauth.route=\'connector\'', connectorId=\'figma'', 'kind=\'form\''). Not 5 because the GenUI surface configs are described in prose rather than given as complete snippets, leaving minor gaps. | 4 / 5 |
Workflow Clarity | The stage sequence is explicit with data-flow rationale ('figma-extract writes figma/tree.json ... generate reads both') and an explicit feedback loop ('repeat: true, until: critique.score>=4 || iterations>=3'). Not 5 because per-stage failure handling and validation checkpoints between extract/tokens/generate are not specified. | 4 / 5 |
Progressive Disclosure | Under 50 lines with well-organized sections ('## Default pipeline', '## Required GenUI surfaces') and no external files needed, which would merit 5 — but the 'Spec §1 / §10.1 / §21.3.1 / §23.3.3' citations point to a spec document that is not in the bundle, leaving unresolvable references. | 4 / 5 |
Total | 17 / 20 Passed |