CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

recipe-front-design

Execute from repository evidence through applicable UI Spec and optional ADR decisions to complete frontend Design Doc approval

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./dev-workflows-frontend/skills/recipe-front-design/SKILL.md

The canonical home for this skill is recipe-front-design in shinpr/claude-code-workflows

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a tightly written orchestration recipe: every step names its executor, exact inputs, verdict handling, and stop conditions, with feedback loops and a completion checklist throughout. Its main weaknesses are extreme sentence-level compression that occasionally buries sub-sequences (Step 8) and dependence on external skills for several decision rules, which is well signaled but unverifiable within this bundle.

DimensionReasoningScore

Conciseness

The body is densely procedural with no padding and no explanation of concepts Claude already knows — nearly every sentence carries a rule, an input contract, or a routing decision. It falls short of anchor 5 only because of rationale asides ("This independent discovery keeps scope and option convergence grounded in repository evidence rather than the orchestrator's unverified implementation hypothesis") and over-compressed run-ons (the single-paragraph Step 8) that could be tightened without losing content.

4 / 5

Actionability

Guidance is highly concrete for an instruction-only skill: exact agent names ("dev-workflows-frontend:codebase-analyzer"), exact input fields with serialization ("copy the named source values into the exact fields"), and explicit verdict branches (pass / needs_revision / rejected). It is not anchor 5 because several decision procedures — the documentation-criteria UI Spec condition, convergence field rules, Review Resolution, and Structural Scale values — are delegated to external skills whose definitions are not visible in this bundle, leaving minor execution gaps if those are unavailable.

4 / 5

Workflow Clarity

The multi-step process is clearly sequenced (numbered Steps 1-8 plus a flow diagram) with explicit validation checkpoints ("[Stop]" points requiring user confirmation), feedback loops (needs_revision → Review Resolution → correction → re-review; verification rerun after applied corrections), and a Completion Criteria checklist — matching most of anchor 5. It drops to 4 because the packing of multiple operations into single dense paragraphs, especially Step 8, obscures the internal sub-sequence a reader must follow.

4 / 5

Progressive Disclosure

The skill is a self-contained orchestration recipe with no bundle files (references/, scripts/, assets/ are absent), and its sections (Flow, Steps 1-8, Completion Criteria) are well organized with all orchestration content appropriately inline. Cross-skill file references ("references/review-resolution.md" of subagents-orchestration-guide, "references/criteria.md" of requirement-convergence) are clearly attributed to their owning skills, satisfying anchor 4's 'references mostly clear'; it is not 5 because navigation to those dependent definitions is one hop into other skills rather than a clean one-level-deep reference set within this bundle.

4 / 5

Total

16

/

20

Passed

Description

53%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description communicates a specific multi-artifact frontend design workflow, but it is written as an outcome summary rather than a capability-plus-trigger statement. It lacks any 'Use when...' guidance and relies on one generic verb ("Execute"), leaving a model to infer when the skill applies and what concrete actions it performs.

Suggestions

Add an explicit trigger clause, e.g. 'Use when coordinating or completing a frontend design effort that needs a UI Spec, ADR decisions, or an approved frontend Design Doc.'

Replace the single generic verb 'Execute' with concrete actions: 'Creates and reviews the applicable UI Spec, routes qualifying decisions into an ADR batch, and produces an approved frontend Design Doc grounded in repository evidence.'

Include natural user phrasings and synonyms such as 'design document', 'UI specification', 'frontend feature design', and 'architecture decision records' so the description matches how users actually ask.

DimensionReasoningScore

Specificity

The description names the domain ("frontend Design Doc") and concrete pipeline artifacts ("applicable UI Spec and optional ADR decisions"), but the only action verb is the generic "Execute". It sits between anchor 2 ("names the domain but actions are minimal") and anchor 3 ("domain plus 1-2 concrete actions") — the enumerated artifacts lift it above a bare domain label, but coverage of actual actions (create, review, approve) is not comprehensive, matching anchor 3.

3 / 5

Completeness

The 'what' is reasonably clear (run a frontend design workflow from repository evidence through UI Spec and ADR decisions to an approved Design Doc), but there is no 'Use when...' clause or equivalent trigger guidance — the 'when' is entirely absent, capping this dimension at 3 per the judging guidelines. It is above anchor 2 because the 'what' is concrete, not vague.

3 / 5

Trigger Term Quality

Relevant domain keywords are present ("frontend", "Design Doc", "UI Spec", "ADR", "approval"), but natural user phrasings and synonyms are missing — no "design document", "UI specification", "frontend feature design", or "when designing...". This matches anchor 3 ("some relevant keywords but missing common variations or synonyms") rather than 4, where good natural-term coverage would be present.

3 / 5

Distinctiveness Conflict Risk

The description carves a fairly distinct niche (frontend design-doc pipeline with UI Spec and ADR stages), and terms like "UI Spec" signal the frontend domain, giving minor overlap risk with closely related skills (e.g., a backend design-doc variant). It falls just short of anchor 5's "clear niche with distinct triggers" because, without any trigger guidance, distinguishing it from sibling design/backend workflow skills relies on artifact names alone.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

shinpr/claude-code-workflows

Path

dev-workflows-frontend/skills/recipe-front-design/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.