Skip to main content
skill CX Codex

oma-design · first-fluke, oma — Claude Code skill for design systems and setup

The oma-design skill shapes and audits a project’s design system, from DESIGN.md to accessibility and responsive guidance. Use it before frontend work or to review an interface.

MIT ★ 1,472 updated 2026-10-29

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add first-fluke/oh-my-agent
/plugin install oma@oh-my-agent
Open on GitHub

What oma-design does

The skill checks .design-context.md first, then gathers the project’s audience, platform, and design constraints. It proposes several design directions and waits for confirmation before generating or revising DESIGN.md. It can also advise on typography, color, layout, and component choices.

Next, it reviews responsive behavior, WCAG accessibility, and visual anti-patterns. Its baseline uses system fonts, mobile-first layouts, and WCAG AA; motion guidance takes prefers-reduced-motion into account. Stitch MCP is optional. The skill does not implement frontend code.

Create .design-context.md before design work if the project does not already have one. The skill can read and modify DESIGN.md and context files, so review the proposed direction before approving generation.

What it helps with

  • draft a project design system in DESIGN.md
  • choose typography, colors, and interface layout
  • audit a UI for responsive behavior and accessibility
  • spot visual anti-patterns and suggest alternatives

Example prompts for the agent

  • Use oma-design to propose design directions for this project before creating DESIGN.md.
  • Audit DESIGN.md and the interface for accessibility and responsive behavior.
  • Recommend typography and a color system for the project constraints.

How to install oma-design

1Plugin marketplace

/plugin marketplace add first-fluke/oh-my-agent
/plugin install oma@oh-my-agent

This installs the whole oma plugin with all its skills

2Skills CLI (Vercel)

npx skills add first-fluke/oh-my-agent --skill oma-design -a claude-code

3Manually: put the files in place

~/.claude/skills/oma-design/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/oma-design/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about oma-design

How do I install oma-design in Claude Code?

Run /plugin marketplace add first-fluke/oh-my-agent in Claude Code, then run /plugin install oma@oh-my-agent.

What does oma-design do?

It helps set a project’s visual direction, create or revise DESIGN.md, and check interface guidance for responsiveness, accessibility, and visual anti-patterns. It does not build frontend components.

Does oma-design require Stitch MCP?

No. Stitch MCP is optional; the skill can continue using project context and local design materials without it.

Source text

SKILL.md · MIT
---
name: oma-design
description: >
  AI design specialist skill with DESIGN.md management, anti-pattern enforcement,
  optional Stitch MCP integration, and component library guidance.
  Covers typography, color systems, motion design (motion/react, GSAP, Three.js),
  responsive-first layouts, and accessibility (WCAG 2.2).
---

# oma-design

## Scheduling

### Goal
Design specialist that defines, creates, and validates project design systems.
DESIGN.md is the central artifact — all design work revolves around it.

### Intent signature
- User asks for design system, `DESIGN.md`, visual direction, typography, color, motion, accessibility, anti-pattern review, or component guidance.
- User needs design decisions before frontend implementation or wants UI quality audited from a design perspective.

### When to use
- Defining or revising a project design system
- Creating or auditing `DESIGN.md`
- Selecting typography, color, layout, motion, or component direction
- Reviewing UI work for responsive behavior, accessibility, and visual quality
- Using optional vendor inspiration from Stitch MCP or getdesign

### When NOT to use
- Implementing frontend components or application UI -> use `oma-frontend`
- Planning product scope or task breakdown -> use `oma-pm`
- Backend, database, infrastructure, or mobile implementation -> use the relevant specialist skill
- General quality/security review outside visual, interaction, and accessibility concerns -> use `oma-qa`

### Expected inputs
- Product, brand, audience, platform, and UI/design problem
- Existing `.design-context.md`, `DESIGN.md`, screenshots, references, or component constraints
- Accessibility, responsive, language, and implementation constraints

### Expected outputs
- Design direction, revised `DESIGN.md`, audit findings, component guidance, or handoff notes
- Responsive-first, WCAG-aware design recommendations
- Optional vendor seed attribution when getdesign is used

### Dependencies
- `.design-context.md` and `DESIGN.md`
- Design resources, references, anti-pattern catalog, and optional Stitch/getdesign integrations
- shadcn/component library context when recommending components

### Control-flow features
- Branches by missing context, CJK language support, vendor seed availability, and anti-pattern audit results
- May read/write design docs and call optional design/vendor tooling
- Requires user confirmation before generation when multiple directions exist

## Structural Flow

### Entry
1. Check `.design-context.md`; if missing, run setup before design work.
2. Identify target audience, platform, content language, and design artifact.
3. Decide whether vendor inspiration or Stitch integration is relevant.

### Scenes
1. **PREPARE**: Load design context and constraints.
2. **ACQUIRE**: Extract existing design signals, references, and anti-pattern risks.
3. **REASON**: Propose directions, typography, color, layout, motion, and accessibility choices.
4. **ACT**: Generate or revise `DESIGN.md` and related guidance.
5. **VERIFY**: Audit responsive behavior, WCAG, Nielsen heuristics, and AI-slop patterns.
6. **FINALIZE**: Handoff design decisions and attribution where required.

### Transitions
- If `.design-context.md` is missing, create it before continuing.
- If CJK support is needed, prioritize CJK-ready fonts.
- If vendor seed fetch fails, choose retry, continue without seed, or abort.
- If anti-patterns appear, surface alternatives before finalizing.

### Failure and recovery
- If design context is insufficient, ask for one focused clarification or propose assumptions.
- If vendor inspiration is unavailable, continue with local design synthesis.
- If accessibility checks fail, revise before handoff.

### Exit
- Success: design artifact is project-specific, responsive-first, accessible, and audit-ready.
- Partial success: missing context, vendor failure, or open design decision is explicit.

## Logical Operations

### Actions
| Action | SSL primitive | Evidence |
|--------|---------------|----------|
| Read design context | `READ` | `.design-context.md`, `DESIGN.md`, references |
| Select design direction | `SELECT` | 2-3 directions and recommended option |
| Infer visual system | `INFER` | Typography, color, layout, motion |
| Call optional tooling | `CALL_TOOL` | Stitch/getdesign/shadcn when relevant |
| Write design artifact | `WRITE` | `DESIGN.md` or audit output |
| Validate design quality | `VALIDATE` | Checklist, WCAG, anti-patterns |
| Report handoff | `NOTIFY` | Final design summary |

### Tools and instruments
- Design references, anti-pattern catalog, checklist, Stitch integration, getdesign fetcher
- shadcn CLI recommendations when component guidance is needed

### Canonical workflow path
```text
1. Check `.design-context.md`; create it if missing.
2. Produce 2-3 design directions and get confirmation.
3. Generate or revise `DESIGN.md`, then run the design checklist.
```

Optional vendor seed discovery:
```bash
bunx getdesign@latest list
```

### Resource scope
| Scope | Resource target |
|-------|-----------------|
| `LOCAL_FS` | `.design-context.md`, `DESIGN.md`, design resources |
| `CODEBASE` | Existing UI and component patterns |
| `NETWORK` | Optional getdesign/vendor references |
| `PROCESS` | Optional CLI/tool invocations |

### Preconditions
- Target design problem and artifact are identifiable.
- Design context exists or setup can create it.

### Effects and side effects
- May create or modify `DESIGN.md` and design context artifacts.
- May fetch vendor seed material and append MIT attribution.
- Does not implement frontend code directly.

### Guardrails
1. Check `.design-context.md` before any design work. If missing, run Phase 1 (Setup) to create it.
2. System font stack as default (`system-ui, -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, sans-serif`). Add custom fonts only with project justification.
3. If the service supports CJK languages (ko/ja/zh): prioritize CJK-ready fonts (Pretendard Variable > Noto Sans CJK > system-ui fallback). If latin-only: choose fonts appropriate for the target audience.
4. Enforce anti-patterns strictly — reject AI slop. See `resources/anti-patterns.md`.
5. Name colors semantically with hex values: "Deep Ocean Navy (#1a2332)" not "dark blue".
6. Recommend components with install commands (shadcn CLI).
7. ALL output must be responsive-first (mobile layout as default, enhance upward).
8. WCAG AA minimum for all designs. Respect `prefers-reduced-motion`.
9. Stitch MCP is optional — all phases work without it.
10. Present 2-3 design directions and get user confirmation before generating.

### Anti-Pattern Quick Reference

### Typography
- DON'T: Default to custom Google Fonts when system fonts suffice
- DON'T: Use Inter/Geist alone without considering project context
- DON'T: Load 3+ font families without justification
- DON'T: Body text below 16px on mobile
- DO: System font stack first, custom fonts for brand identity only
- DO: Test CJK at every size (line-height 1.7-1.8)

### Color & Gradient
- DON'T: Purple-to-blue gradient backgrounds (strongest AI slop signal)
- DON'T: Gradient orbs/blobs as hero decoration ("AI SaaS look")
- DON'T: Gradient + glassmorphism + blur combo (triple slop)
- DON'T: Mesh gradient backgrounds as primary visual
- DON'T: Pure white (#fff) on pure black (#000) — too harsh
- DO: Solid colors or subtle single-hue gradients
- DO: Texture (noise, grain, dither) over plain gradients
- DO: Derive gradients from brand colors with clear purpose

### Layout
- DON'T: Nested cards inside nested cards
- DON'T: Desktop-only fixed-width layouts
- DON'T: Hero with identical 3-metric stats layout (AI pattern)
- DO: 8px grid, consistent section rhythm
- DO: Responsive-first, works at 375px minimum
- DO: Mix layout patterns (chess, grid, bento, full-bleed)

### Motion
- DON'T: Bounce easing on everything
- DON'T: Animation duration > 800ms for UI transitions
- DON'T: Ignore prefers-reduced-motion
- DO: transform + opacity only for 60fps
- DO: 150ms micro-interactions, 200-500ms transitions

### Components
- DON'T: Glassmorphism everywhere — use sparingly
- DON'T: Hover-only interactions without touch/keyboard alternatives
- DO: shadcn/ui for base, Aceternity UI / React Bits for accent effects
- DO: All interactive elements must have visible focus states

### Workflow Summary
7 phases: Setup → Extract → Enhance → Propose → Generate → Audit → Handoff.
See `resources/execution-protocol.md` for full detail.

### Vendor Inspiration (getdesign)

Phase 2 can optionally seed from the community
[getdesign](https://getdesign.md) catalog
([VoltAgent/awesome-design-md](https://github.com/VoltAgent/awesome-design-md),
MIT). Trigger it by listing a supported vendor domain in the
`## Reference Sites` section of your `.design-context.md`:

```markdown
## Reference Sites
- [linear.app](https://linear.app) — clean dark UI, minimal, professional
- [stripe.com](https://stripe.com) — strong hierarchy, purposeful animation
```

Any domain that matches a brand in the getdesign manifest triggers an
automatic fetch + hash-verify + load during Phase 2. No new fields, no
extra config. Full vendor list: see `bunx getdesign@latest list`
(telemetry is always disabled by oma-design).

**Seed, not final.** oma-design treats vendor templates as inspiration
and synthesizes a project-specific DESIGN.md around them. Importantly:
- **Typography is never adopted from the seed.** Rule #2 (system font
  stack default) and Rule #3 (Pretendard Variable / Noto Sans CJK for
  ko/ja/zh) always win over the vendor's latin-only fonts.
- **Anti-patterns are pre-audited** before synthesis. If a vendor uses
  heavy glassmorphism or purple gradients, Phase 4 will surface the
  choice explicitly rather than copy the pattern silently.
- **Offline is fine.** If the fetch fails, you get a 3-option dialog
  (retry / continue without seed / abort). Default: continue.

Attribution is appended to the generated `DESIGN.md` in Phase 7 as a
required MIT compliance footer. Full fetcher rules, matching algorithm,
injection defenses, and multi-vendor merge policy live in
`resources/getdesign-fetcher.md`.

### Resources
- `resources/execution-protocol.md` — 7-phase workflow
- `resources/anti-patterns.md` — Full DO/DON'T catalog
- `resources/checklist.md` — Audit checklist (Responsive + WCAG + Nielsen + Slop)
- `resources/design-md-spec.md` — DESIGN.md generation guide (9 sections)
- `resources/design-tokens.md` — CSS/Tailwind/shadcn export templates
- `resources/prompt-enhancement.md` — Vague request → detailed spec
- `resources/stitch-integration.md` — Stitch MCP tool mapping (optional)
- `resources/getdesign-fetcher.md` — Vendor seed fetch, hash verify, seed rules
- `resources/error-playbook.md` — Design error recovery

## References
- `reference/visual-hierarchy.md` — 7 hierarchy principles (Alignment, Color, Contrast, Proximity, Size, Texture, Time)
- `reference/typography.md` — Font selection, type scale, CJK
- `reference/color-and-contrast.md` — Color psychology, WCAG contrast
- `reference/spatial-design.md` — 8px grid, breakpoints, spacing
- `reference/motion-design.md` — motion/react, GSAP, Three.js, ogl, Temporal UX
- `reference/responsive-design.md` — Mobile-first, theme system
- `reference/component-patterns.md` — shadcn/Aceternity/React Bits catalog
- `reference/accessibility.md` — WCAG 2.2, ARIA, focus, reduced-motion
- `reference/shader-and-3d.md` — WebGL, R3F, ogl, performance

### Examples
- `examples/design-context-example.md` — .design-context.md example
- `examples/landing-page-prompt.md` — Detailed landing page prompt

© First Fluke · MIT · first-fluke/oh-my-agent

Similar skills

All skills for Design →

oma-design by other authors comes first.

oma-design First Fluke oma-design resolves a project's design direction and maintains DESIGN.md as the visual contract. Picks an external design skill — Interface Design, Taste, or Impeccable — for the task at hand. CX Codex +1 ★ 1,472repo stars frontend-design-review microsoft The frontend-design-review skill reviews and creates frontend interfaces with checks for design quality, accessibility, and design-system use. Use it for UI reviews, PRs, and responsive layouts. CX Codex +1 237installs impeccable boraoztunc impeccable helps agents design, review, and refine frontend interfaces. Use it for UX audits, responsive layouts, accessibility, and design-system work. CX Codex +1 260installs tailwind-design-system Seth Hobson tailwind-design-system helps build design systems with Tailwind CSS v4, from theme tokens to component variants. Use it when a project needs shared UI patterns. CX Codex +1 70,180installs web-design-reviewer official github The web-design-reviewer skill inspects a running website, spots layout, responsive, and accessibility issues, and can fix them in the source code. Use it when a UI review should lead to verified code changes. CX Codex +1 13,957installs responsive-design Owl-Listener responsive-design — a skill that steers your coding agent toward layouts and interactions that hold up across screen sizes and input methods. CX Codex +1 2,700installs ui-design Starchild-ai-agent ui-design — a build guide and quality gate for visual interfaces, covering track selection, accessibility, responsive behavior, themes, motion, and preview delivery. CX Codex +1 1,800installs

From the same set69

The whole set →
oma-recap oma-recap pulls conversation histories from AI tools across a chosen timeframe and organizes them into a themed project report. Useful for standups and understanding how work distributed across different AI assistants. CX Codex +1 ★ 1,472repo stars oma-tf-infra The oma-tf-infra skill creates and reviews Terraform code, plans, and cloud infrastructure. It covers IAM, networking, state, cost, and destructive-change risk. CX Codex +1 ★ 1,472repo stars oma-mobile oma-mobile is a skill that builds and edits mobile screens and features in Flutter, React Native, Swift, or Kotlin. It inspects existing widgets, providers, and API clients before code changes. CX Codex +1 ★ 1,472repo stars oma-architecture oma-architecture — a skill for Claude Code and Codex to evaluate system boundaries and architectural tradeoffs. Runs during system design reviews, module boundary audits, and ADR authoring. CX Codex +1 ★ 1,472repo stars oma-brainstorm oma-brainstorm — a skill for Claude Code and Codex designed for early feature exploration before task planning. Clarifies ambiguous requests one question at a time and compares technical options. CX Codex +1 ★ 1,472repo stars oma-orchestrator oma-orchestrator — a skill that automates spawning multiple specialist agents at once, coordinates them via MCP Memory, and tracks progress. CX Codex +1 ★ 1,472repo stars oma-explanation oma-explanation turns a PR, branch or commit range diff into a self-contained HTML walkthrough with background, code narration and a five-question quiz. CX Codex +1 ★ 1,472repo stars oma-translation oma-translation — a skill for Claude Code and Codex translates and reviews UI strings, documentation, and prose while protecting placeholders. Updates target locale files after source edits. CX Codex +1 ★ 1,472repo stars

Project sponsors

Companies that keep this analytics open