hyperflow-design

Hyperflow design phase. Use when designing a UI / visual system or making a screen look good — verbs like "design the UI", "make it look good", "design the screen", "visual design", "design system". Establishes or extends a domain-grounded design system, researches real-world prior art, and renders it slop-free. Thinking and taste, not building.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

82%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.

A tight, directive instruction skill with excellent token efficiency and a clear four-step sequence. Its weaknesses are dangling references to external materials without locations and absent validation checkpoints to confirm the system file and spec were actually updated.

Suggestions

Give locations for the referenced materials: a path for 'the spec', where the Motion-language standards and mobile matrix documents live, or how to discover the 'matching local taste skill(s)'.

Add a closing validation step (e.g., 'Confirm .hyperflow/design/system.md exists and the spec records the tokens and signature move before finishing') to make the workflow feedback-complete.

Clarify step 2's output requirement — what 'combine them' and 'one deliberate signature move' should be recorded as — so the research step has a verifiable deliverable.

Dimension	Reasoning	Score
Conciseness	The 18-line body is lean and assumes Claude's competence: rules like 'no default AI gradient, one accent, locked corner-radius scale, eyebrow restraint' are stated as directives with no padding or explanation of concepts Claude already knows, matching the 'every token earns its place' anchor.	5 / 5
Actionability	Mostly executable guidance with concrete specifics ('.hyperflow/design/system.md', '≥2 real-world references', enumerated token categories), but key details are missing: where 'the spec' lives, how to 'Discover and apply the matching local taste skill(s)', and where the 'Motion-language standards' or 'mobile platform/device/accessibility matrix' are found — fitting the 'concrete guidance with minor gaps' anchor.	4 / 5
Workflow Clarity	Four numbered steps in a clear sequence with conditional branches ('when a motion surface is in scope…') and a create-vs-extend decision point, but there are no validation checkpoints (e.g., verifying the spec was updated or the system file is complete). This is design/spec work, not destructive or batch operations, so the workflow cap does not apply; it sits at 'clear sequence with most checkpoints' rather than anchor 5's explicit validation steps.	4 / 5
Progressive Disclosure	A short, well-sectioned body (Steps, Rules) that needs no bundle files, but it references external materials — 'the hyperflow doctrine', 'local taste skill(s)', 'Motion-language standards', the 'mobile platform/device/accessibility matrix' — without signaling where they live (no paths or links), a minor organization gap that keeps it below the top anchor.	4 / 5
	Total	17 / 20 Passed

Description

91%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.

A strong description: it answers what and when explicitly, leads with natural trigger phrasing, and defines a clear niche within a pipeline. Its only weaknesses are the slightly vague 'renders it slop-free' phrasing and mild overlap risk with other design-related skills.

Suggestions

Replace or expand the vague phrase 'renders it slop-free' with a concrete action (e.g., 'applies an anti-slop checklist to the rendered output').

Sharpen distinctiveness by naming the sibling phases it must not trigger for (e.g., 'use the build-phase skill for implementation'), reducing overlap with other design skills.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'Establishes or extends a domain-grounded design system, researches real-world prior art' — but 'renders it slop-free' is jargon-adjacent and coverage of outputs is slightly thin, matching the 'several specific actions; minor gaps' anchor rather than the comprehensive anchor 5.	4 / 5
Completeness	Clearly answers both 'what' (establish/extend a design system, research prior art, render slop-free, 'Thinking and taste, not building') and 'when' ('Use when designing a UI / visual system or making a screen look good' with concrete trigger verbs), matching the top anchor exactly.	5 / 5
Trigger Term Quality	Explicitly enumerates natural user phrases — 'design the UI', 'make it look good', 'design the screen', 'visual design', 'design system' — giving comprehensive coverage of the ways a user would naturally ask for this skill.	5 / 5
Distinctiveness Conflict Risk	'Hyperflow design phase' and 'Thinking and taste, not building' carve a clear niche, but generic phrases like 'visual design' and 'design system' create minor overlap risk with other design- or UI-related skills, fitting the 'mostly distinct; minor overlap risk' anchor.	4 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: jeremylongshore/tons-of-skills-marketplace
Path: plugins/ai-agency/hyperflow/templates/antigravity/skills/hyperflow-design/SKILL.md
Commit: 88dcf65

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.