Skills

Design

Use when the user wants the visual/experiential design of a product done systematically...

Install

npx skills add jeremylongshore/tons-of-skills-marketplace --skill design -g -a claude-code -y
Category
Design
Updated
3d ago
License
MIT
Context cost
Mediumabout 1,735 tokens
Runs scripts
No, instructions only

What it does

Use when the user wants the visual/experiential design of a product done systematically, a design system, a screen, a landing page, or a visual identity, grounded in researched real-world prior art and free of AI slop. Establishes/extends the design system, invokes the matching local taste skill, dispatches the designer specialist, and reviews for taste + accessibility. Standalone, ends with a handoff gate into the chain. Trigger with /hyperflow:design, "design the UI", "make a design system", "design this screen", "give this a visual identity", "redesign this".

Design

Systematic, anti-slop product design. All agents inherit the session model. Reviewers bold-labeled; Workers plain.

This skill exercises Layer 4 (Brainstorming/Spec) and the design layer of Layer 0 (Project Analysis). It is thinking, not building, no source code is written here. The only writes are to .hyperflow/design/system.md and .hyperflow/specs/. It ends with a handoff gate into /hyperflow:plan → /hyperflow:dispatch for the build.

Iron Rules

  • Design system first. Every run establishes or extends .hyperflow/design/system.md before designing a screen, per ../hyperflow/design-system.md. The system is created once and extended, never regenerated.
  • Researched, not invented. Ground every direction in ≥2 real products from the project's field, combine them, then diverge with one deliberate signature (the method in design-system.md).
  • Local taste skills are invoked live. The main session calls Skill to invoke the matching taste skill; the dispatched designer agent Reads the SKILL.md and applies it (it has no Skill tool).
  • Per-step agents (DOCTRINE rule 12). No inline design, the designer specialist does the work; an accessibility-reviewer pass gates the result.
  • No code in the design phase. Design produces a system file and a design spec; dispatch executes them.
  • Failure recovery (DOCTRINE rule 14) per ../hyperflow/failure-recovery.md.
  • No AI attribution in any file written.

Per-Step Agent Map (DOCTRINE rule 12)

Read the whole SKILL.md on GitHub

More in Design