Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →shinpr/recipe-front-design
Execute from codebase analysis to frontend design document creation
Passed 10 of 16 test cases with the skill, and 6 of 16 without it.
and 6 more in the full report
9 fixed5 passed either way5 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
Before sending the created frontend Design Doc to document-reviewer, what verification check must be run and against what doc_type?
| Checked | Without skill | With skill |
|---|---|---|
| Invokes code-verifier with doc_type set to design-doc and document_path set to the Design Doc path | Missed | Passed |
The instructions your model reads when the skill loads.
Execute Skill: documentation-criteria before document routing or creation.
Execute Skill: llm-friendly-context before writing Agent prompts, handoffs, or generated artifacts.
Execute Skill: subagents-orchestration-guide before invoking agents or resolving findings.
Before the first finding disposition, read references/review-resolution.md from the loaded subagents-orchestration-guide skill.
Coordinate a Medium/Large frontend design from evidence to an applicable UI Spec and approved Design Doc. The orchestrator owns requirement convergence, Structural Scale, document routing, ADR qualification, evidence selection, and Review Resolution. Named specialists own semantic investigation and artifacts.
The frontend Design Doc always carries the complete implementation design. An ADR batch narrows qualifying technical choices; an applicable UI Spec owns UI structure and behavior that remain to be designed.
Requirements: $ARGUMENTS
requirement source -> codebase-analyzer -> scope/document routing confirmation [Stop]
|
conditional UI analysis -> UI Spec review [Stop]
|
optional ADR batch/review [Stop]
|
Design Doc -> code-verifier/Resolution -> document-reviewer
|
design-sync -> approval [Stop]
Use Review Resolution for every actionable finding. Wait at each [Stop] for explicit user confirmation.
At each Agent invocation below, build the prompt as a mechanical extraction: copy the named source values into the exact fields, apply only the declared serialization, then invoke immediately.
Use the approved PRD path when one exists. Otherwise use the confirmed requirements verbatim.
Set confirmed_requirement_context to the approved PRD path exactly. Only when no approved PRD exists, use the orchestrator-confirmed convergence record unchanged.
Invoke dev-workflows-fullstack:codebase-analyzer once for the complete confirmed scope with exactly prd_path: [approved PRD path], or requirements: [confirmed requirements verbatim] when no approved PRD exists.
test cases passed, vs 6 / 16 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.