Skip to main content
skill CX Codex

oma-design · first-fluke, frontend — Claude Code skill: what it does, how to install

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.

MIT ★ 1,472 updated 2026-11-12

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

What oma-design does

The skill sorts out design requests: setting or revising a visual system, reviewing an existing interface, or pulling design decisions out of screenshots and references. It first establishes the scope of change, the platform, the current stack, content languages, and accessibility requirements, then loads a matching supplier through resources/external-design-skills.md — Interface Design for admin consoles and SaaS products, Taste for new web art direction, or an Impeccable operation for auditing and polishing an existing UI.

DESIGN.md only gets updated when the visual system changes in a material way; it holds the token contract and isn't rewritten to match a supplier's house style. The skill doesn't touch application code itself — it hands the decision to the frontend or mobile specialist along with the project's constraints. For Korean, Japanese, and Chinese content it checks glyph coverage and line-breaking separately, and accessibility defaults to WCAG AA or a stricter project target.

Review operations stay read-only; build authorization and any side effects fall under the broader execution policy, not this skill.

What it helps with

  • lock down a project's visual system in DESIGN.md
  • pick an external design skill for a given task — Interface Design, Taste, or Impeccable
  • review an existing interface for hierarchy, density, and consistency
  • pull design decisions out of screenshots and existing UI
  • hand a design decision to the frontend or mobile specialist with project constraints

Example prompts for the agent

  • Define a visual system for a new SaaS dashboard and update DESIGN.md
  • Review the current admin UI for density and component consistency
  • Go through these screenshots and record the colors and typography in DESIGN.md

How to install oma-design

1Plugin marketplace

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

This installs the whole oma-frontend 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, then /plugin install oma-frontend@oh-my-agent.

What does oma-design do?

It sets or revises a project's visual system, maintains DESIGN.md, and routes to a matching external design skill for the task, from new direction work to auditing an existing interface.

How does oma-design pick between Interface Design, Taste, and Impeccable?

Interface Design handles post-build reviews of admin consoles, dashboards, and SaaS products; Taste covers new web art direction; Impeccable operations handle critique, accessibility audits, and polish of an existing UI.

Source text

SKILL.md · MIT
---
name: oma-design
description: Define or review a visual system, DESIGN.md, or redesign direction.
  Use for typography, layout, color, motion, and interaction design decisions.
---

# oma-design

## Scheduling

### Goal
Resolve project design intent, select the applicable external design skill, and
retain the project's visual contract and verification evidence. `DESIGN.md`
records the design system when the task creates or materially changes it.

### Intent signature
- Design system, `DESIGN.md`, visual direction, redesign, or UI design review.
- Typography, color, layout, motion, accessibility, or component decisions before implementation.

### When to use
- Define or revise a visual system or substantial design direction.
- Review an existing UI or refine a chosen visual direction.
- Extract design decisions from existing UI, screenshots, or supplied references.

### When NOT to use
- Implement application UI or export framework-specific tokens -> `oma-frontend` or `oma-mobile`.
- Plan product scope -> `oma-pm`; generate an image -> `oma-image`.
- Review general correctness or security -> `oma-qa` or `oma-security`.

### Expected inputs
- Requested surface and outcome, existing brand and project facts, and change scope.
- Available `DESIGN.md`, `.design-context.md`, UI, screenshots, and references.
- Platform, incumbent stack, content languages, accessibility, and responsive constraints.

### Expected outputs
- Requested design decision, findings, or implementation handoff with observed evidence.
- Selected supplier, operation, resolved source, and capability or verification limits.

```yaml
outputs:
  - name: design-doc
    description: Updated visual contract when the design system materially changes
    artifact: "DESIGN.md"
    required: false
  - name: design-context
    description: Existing context refreshed after substantive discovery
    artifact: ".design-context.md"
    required: false
```

### Dependencies
- Interface Design, Taste, or Impeccable, selected through `resources/external-design-skills.md`.
- Project design artifacts and relevant local resources; Stitch and getdesign are optional inputs.
- The implementation specialist's existing stack and validation tools.

## Structural Flow

### Transitions
- A scoped correction reuses the affected UI and tokens; a discovery document is unnecessary.
- For existing products, establish Preserve or Overhaul from the brief and current system.
- For a post-implementation hierarchy, density, consistency, or craft review of an admin console, dashboard, SaaS product UI, or internal tool, select Interface Design `design-review` through `resources/product-interface-review.md`. The frontend recommendation is advisory unless the task explicitly requires design approval.
- For other existing-UI critique, accessibility or technical audit, polish, or system extraction, select the matching Impeccable operation.
- For dashboards, admin panels, SaaS product UI, or internal tools needing visual direction, select Interface Design.
- When the surface is built around a data table or grid, pass `resources/data-grid.md` to the selected supplier with the brief.
- For other new web art direction or an authorized visual overhaul, select Taste.
- A documentation-only or token-contract task can remain local when no new visual judgment is needed.
- Load one supplier for the current operation. A later operation may select another using the same project context.
- A chosen GPU effect, cinematic video-scroll scene, or GSAP behavior adds the matching frontend implementation extension; it does not select another visual-direction supplier.

### Failure and recovery
| Failure | Recovery |
|---|---|
| Missing or incomplete external bundle | Resolve the catalog entry or use the bounded upstream loading path; retain its complete support directory. |
| Supplier changes the stack, brand, or task scope | Restore the project constraints and choose the applicable operation; implementation remains with the owning specialist. |
| A supplier gate needs an unavailable runtime or unauthorized build | Report the gate as unrun; do not replace it with a claimed pass. |
| Explicitly requested supplier is unavailable | Report the failed route and missing capability; do not silently substitute a different supplier. |
| Missing context changes the design decision | Reuse existing artifacts and the brief; ask only about the material unresolved choice. |

### Exit
The requested decision or artifact is ready for the next action, with the selected
route, project constraints, observed checks, and unresolved limits recorded.

## Logical Operations

### Canonical workflow path
1. Inspect the relevant UI, design artifacts, and brief. Establish scope, platform,
   incumbent stack, languages, brand preservation, and applicable verification.
2. Use `resources/external-design-skills.md` to select and load the supplier for
   this operation. Follow its relevant instructions and support files.
3. Apply the result to the requested decision or artifact. Update `DESIGN.md`
   only when the visual system changes; use its local specification and semantic
   token contract. Optional Stitch/getdesign inputs remain project references.
4. Check the affected result using `resources/checklist.md`. Hand implementation
   to the owning frontend/mobile specialist with the route and project constraints.
   Include a specialized frontend route when the brief calls for that capability.

### Resource scope and effects
Reads project UI and design references; may write requested design artifacts and
load external skill bundles. Supplier installers, hooks, engine downloads,
background processes, and paid services are separate effects, not skill loading.

### Guardrails
1. Keep existing brand, content, URLs, navigation, form contracts, analytics, and
   legal text within the authorized scope; use the redesign preservation contract.
2. Keep incumbent fonts when suitable. For ko/ja/zh, verify glyph coverage,
   fallback, line breaking, and readable metrics; Latin-only references do not establish CJK support.
3. Carry accessibility, responsive, reduced-motion, and platform requirements into
   the selected supplier. Keep WCAG AA as the default accessibility target, or
   the project's stricter target. Its house style does not override that contract.
4. Use actual project assets and claims. Preserve attribution and label concepts
   and placeholders through the asset strategy.
5. Keep the existing implementation stack. The implementation specialist owns
   CSS/Tailwind/component-library syntax and dependencies.
6. Keep review-only operations read-only. Existing task authorization and the
   shared execution policy govern builds, clarification, scope, and side effects.
7. Keep supplier visual cookbooks upstream. OMA's shared interaction-quality
   guidance owns its adopted motion and interaction acceptance rules; do not
   copy an entire external method catalog into these definitions.

## References
- `resources/product-interface-review.md`: recommended post-implementation product-interface review and frontend handoff.
- `resources/external-design-skills.md`: supplier selection and complete-bundle loading.
- `../oma-frontend/resources/specialized-visual-implementation.md`: chosen GPU, video-scroll, or GSAP implementation capability.
- `../_shared/ui-interaction-quality.md`: motion intent, feedback, and interaction-quality decisions.
- `resources/execution-protocol.md`: operation scope, artifacts, and handoff.
- `resources/redesign-protocol.md`: preserving an existing product.
- `resources/design-md-spec.md`: creating or materially revising DESIGN.md.
- `resources/design-tokens.md`: semantic token handoff to implementation.
- `resources/checklist.md`: affected-result verification and evidence.
- `resources/data-grid.md`: alignment, filter toolbar, and row rules for data tables and grids.
- `resources/asset-strategy.md`: actual assets, claims, provenance, and placeholders.
- `resources/getdesign-fetcher.md`: explicitly relevant vendor inspiration.
- `resources/stitch-integration.md`: requested Stitch operation.
- `resources/error-playbook.md`: an observed supplier or design-tool failure.
- `../_shared/core/execution-policy.md`: authorization, budgets, builds, and completion.

© 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 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. CX Codex +1 ★ 1,472repo stars dark-mode-design Owl-Listener The dark-mode-design skill turns an existing light palette into a dark theme: surface elevation, contrast, desaturated accents. Use it when the light tokens already exist. CX Codex +1 2,900installs visual-design-foundations Seth Hobson The visual-design-foundations skill helps define typography, color, spacing, and icon rules for a project. Use it when setting up design tokens or bringing an interface into visual consistency. CX Codex +1 13,566installs color-system Owl-Listener The color-system skill walks an agent through building a product palette: tonal scales, semantic roles and WCAG contrast checks. Useful when colours are defined from scratch. CX Codex +1 3,000installs editorial typeui.sh Turns your agent into an editorial design-system author: serif type scale, 8pt grid, color tokens, component states and accessibility checks. CX Codex +1 3,300installs premium typeui.sh premium sets Apple-inspired design-system guidance for tokens, spacing, typography and accessibility. Use it when building or aligning an interface. CX Codex +1 3,200installs vocabulary index-how vocabulary is a Claude Code skill that turns loose UI descriptions into exact terms and distinguishes near-synonyms. It helps refine specs and commit messages. CX Codex +1 1,200installs

From the same set69

The whole set →
oma-search oma-search — a skill for Claude Code and Codex that routes queries across external documentation, web search, and remote code. It picks the matching retrieval channel and returns answers backed by citations. CX Codex +1 ★ 1,472repo stars oma-pm oma-pm is a Claude Code skill that turns product requirements into a prioritized task plan with dependencies and acceptance criteria. It prepares the plan before work is handed to specialist agents. CX Codex +1 ★ 1,472repo stars oma-brainstorm oma-brainstorm — a skill for exploring intent, constraints, and alternative approaches before planning or coding. Use it when you have an idea but the path forward is unclear. CX Codex +1 ★ 1,472repo stars oma-pm oma-pm — a skill for Claude Code and Codex decomposes product requirements into scoped tasks with dependencies and acceptance criteria. Generates plan artifacts for specialist agents and orchestrators. CX Codex +1 ★ 1,472repo stars oma-hwp oma-hwp converts Korean HWP, HWPX, and HWPML documents into Markdown or JSON for LLM prompts and retrieval pipelines. CX Codex +1 ★ 1,472repo stars oma-search The oma-search skill picks a search channel for docs, web research, code, or local project files, then labels external sources by domain trust. Use it when the right place to search is unclear. CX Codex +1 ★ 1,472repo stars oma-image oma-image routes image generation requests across Codex, Pollinations and Gemini, and turns a reference picture into a new variation matching its style or layout. CX Codex +1 ★ 1,472repo stars oma-architecture oma-architecture is a Claude Code skill that helps design module and service boundaries, compare alternatives, and document architecture decisions as ADRs. CX Codex +1 ★ 1,472repo stars

Project sponsors

Companies that keep this analytics open