Define or review a visual system, DESIGN.md, or redesign direction. Use for typography, layout, color, motion, and interaction design decisions.
83%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
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.
DESIGN.md, visual direction, redesign, or UI design review.oma-frontend or oma-mobile.oma-pm; generate an image -> oma-image.oma-qa or oma-security.DESIGN.md, .design-context.md, UI, screenshots, and references.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: falseresources/external-design-skills.md.design-review through resources/product-interface-review.md. The frontend recommendation is advisory unless the task explicitly requires design approval.resources/data-grid.md to the selected supplier with the brief.| 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. |
The requested decision or artifact is ready for the next action, with the selected route, project constraints, observed checks, and unresolved limits recorded.
resources/external-design-skills.md to select and load the supplier for
this operation. Follow its relevant instructions and support files.DESIGN.md
only when the visual system changes; use its local specification and semantic
token contract. Optional Stitch/getdesign inputs remain project references.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.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.
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/oh-my-agent
8a03eb1
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.