agentsclimarketplace

Hyperflow design

Skill jeremylongshore/claude-code-plugins-plus-skills/plugins/ai-agency/hyperflow/templates/antigravity/skills/hyperflow-design

425 plugins, 2,810 skills, 200 agents for Claude Code. Open-source marketplace at tonsofskills.com with the ccpi CLI package manager.

Install
npx -y skills add jeremylongshore/claude-code-plugins-plus-skills --skill hyperflow-design

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

1.8 KB, as published. Nobody here has run it

hyperflow-design — design phase (Antigravity single-agent)

Design system and taste, not production code. Follow the hyperflow doctrine.

Steps

  1. Design system first. Ensure .hyperflow/design/system.md exists — create it if missing, extend it (never regenerate) if present: tokens, type scale, motion language, voice, component inventory, references, anti-patterns.
  2. Researched, not invented. Study ≥2 real-world references from the project's own field, combine them, then add one deliberate signature move — never copy a single source.
  3. Taste applied. Discover and apply the matching local taste skill(s); pass the anti-slop floor (no default AI gradient, no serif-by-default, one accent, locked corner-radius scale, eyebrow restraint, no duplicate-intent CTAs, hero fits the viewport, every motion communicates state).
  4. Record the bound design-system tokens and the named signature into the spec. When a motion surface is in scope, apply the Motion-language standards (compositor-only props, spring params, reduced-motion fallback); when a mobile surface is in scope, apply the mobile platform/device/accessibility matrix.

Rules

  • No production code — only the design system and the spec.
  • Defer to accessibility on any a11y conflict (the WCAG floor wins) and to security on any security conflict.
  • Every best-practice claim about a pattern cites a current source.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.