
design
Canonical repo-local DESIGN.md workflow for product, UI/UX, and frontend decision source of truth
- Installs
- 57
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/yeachan-heo/oh-my-codex --skill design- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads design automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Design Skill
Use $design to discover product and UI evidence, close only design-critical context gaps, and create or refresh the repository’s durable DESIGN.md contract. It is a maintained design brief, not a pixel-matching loop or one-off critique.
Shared operating, delegation, state, hook, team, cancellation, and verification invariants live in templates/AGENTS.md. Follow that source instead of duplicating its rules here.
Use when
- Product, UX, frontend, or design-system decisions need a repo-local source of truth.
- A feature needs a design brief before a designer lane or implementation.
- Existing UI, assets, screenshots, or constraints need an actionable design summary.
Do not use it for visual-reference implementation matching (use $visual-ralph), screenshot comparison alone, or backend/infrastructure work without user-facing design impact.
Relationship to $visual-ralph
$design owns product goals, users, information architecture, visual language, components, accessibility, constraints, and open questions in DESIGN.md. $visual-ralph owns implementation against an approved visual reference or live-URL baseline, measured verdicts, and pixel-diff evidence. Run $design first when both are needed; DESIGN.md supports but does not replace the visual verdict target.
Workflow
1. Discover local evidence
Inspect and cite existing DESIGN.md, design/UX/frontend docs, README/specs/issues, routes/pages/layouts/components/stories, theme and token files, assets, screenshots/mockups, Storybook or Playwright baselines, and accessibility/responsive/i18n/platform constraints. Separate observations from inferences; note absent evidence.
2. Interview only missing context
Ask concise questions only for gaps the repository cannot resolve: users/jobs, goals/non-goals, brand personality and forbidden aesthetics, primary flows, accessibility/device/browser targets, or unavailable assets/references. If answers are unavailable, record explicit assumptions and open questions rather than blocking.
3. Create or refresh DESIGN.md
Preserve useful content, remove contradictions, mark unknowns, and keep decisions actionable. The root file must contain these sections:
Design
Source of truth
Status (Draft | Active | Needs refresh), date, product surfaces, evidence reviewed.
Brand
Personality, trust signals, avoid.
Product goals
Goals, non-goals, success signals.
Personas and jobs
Primary personas, user jobs, contexts of use.
Information architecture
Navigation, routes/screens, content hierarchy.
Design principles
Principles and tradeoffs.
Visual language
Color, typography, spacing, shape/elevation, motion, imagery/iconography.
Components
Existing/new components, variants/states, token ownership.
Accessibility
Target standard, keyboard/focus, contrast, semantics, reduced motion/sensory concerns.
Responsive behavior
Breakpoints/devices, layout adaptations, touch/hover differences.
Interaction states
Loading, empty, error, success, disabled, offline/slow network where applicable.
Content voice
Tone, terminology, microcopy rules.
Implementation constraints
Framework/styling, tokens, performance, compatibility, test/screenshot expectations.
Open questions
[ ] question, owner, and impact.
4. Apply the contract
Before UI decisions, cite relevant DESIGN.md sections, reuse documented components/tokens, and update the file or add an open question when implementation exposes a contradiction. Do not invent a parallel design-system layer.
5. Handoff
For normal frontend work, provide the relevant sections, repo evidence, and acceptance criteria. For visual-reference, image, or live-URL matching, hand off to $visual-ralph with the approved baseline and identify DESIGN.md as supporting context only.
Evidence and completion
Complete only when design docs/assets/components/screenshots were inspected or noted absent; missing context is answered, assumed, or listed; root DESIGN.md contains every required section; recommendations cite it; and any Visual Ralph handoff is clearly separated from design governance.
Task: {{ARGUMENTS}}
FAQ
What does the design skill do?
Canonical repo-local DESIGN.md workflow for product, UI/UX, and frontend decision source of truth
How do I install design?
Run npx skills add https://github.com/yeachan-heo/oh-my-codex --skill design in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/design/ (personal) or .claude/skills/design/ (project).
Which AI agents can use design?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is design safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains design?
It is published by yeachan-heo in yeachan-heo/oh-my-codex. It has 57 recorded installs.
More from yeachan-heo/oh-my-codex
deep-interview
yeachan-heo/oh-my-codex
Socratic deep interview with mathematical ambiguity gating before execution
ultraqa
yeachan-heo/oh-my-codex
Adversarial dynamic e2e QA workflow - generate hostile scenarios, test, verify, fix, report, and clean up
ralplan
yeachan-heo/oh-my-codex
Consensus planning stage for Planner - Architect - Critic handoff to $ultragoal
ai-slop-cleaner
yeachan-heo/oh-my-codex
Run an anti-slop cleanup/refactor/deslop workflow
team
yeachan-heo/oh-my-codex
N coordinated agents on shared task list using tmux-based orchestration
Popular frontend & design skills
setup-matt-pocock-skills
mattpocock/skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
frontend-design
anthropics/skills
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
hyperframes-animation
heygen-com/hyperframes
All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.
prototype
mattpocock/skills
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
hyperframes-core
heygen-com/hyperframes
The HyperFrames composition contract — build one renderable project. Use for composition structure, the data- timing attributes, class="clip", tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.
vercel-react-best-practices
vercel-labs/agent-skills
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.