A UI implementation workflow that rebuilds screens or components from a design link, screenshot, or written description while following the project's existing visual and accessibility rules.

Use it to recreate Figma or MasterGo designs, screenshots, and described interactions as working interface components or views.

It helps prevent a new interface from breaking the site's layout, language support, mobile behavior, accessibility, or component conventions.

How oh-my-engine/oh-my-engine configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to oh-my-engine/oh-my-engine. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/oh-my-engine/oh-my-engine/main/.claude/skills/ome-ui/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/oh-my-engine/oh-my-engine

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/oh-my-engine/oh-my-engine/ome-ui/github.svg)](https://agentmods.dev/skills/oh-my-engine/oh-my-engine/ome-ui)

Your own site

<a href="https://agentmods.dev/skills/oh-my-engine/oh-my-engine/ome-ui"><img src="https://agentmods.dev/badge/skills/oh-my-engine/oh-my-engine/ome-ui/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/oh-my-engine/oh-my-engine/ome-ui"><img src="https://agentmods.dev/badge/skills/oh-my-engine/oh-my-engine/ome-ui.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 857 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00015	$0.00857
Opus 5.5	$0.00006	$0.00343
Sonnet 5.5	$0.00003	$0.00171
Haiku 4.5	$0.00002	$0.00086

Measured 2mo ago against content hash c58a312a57c4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ome-ui scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/ome-ui/SKILL.md · 100 lines

How it starts

The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.

ome-ui

Workflow Session Start (MANDATORY)

Before reading source files, planning, editing, or running verification for this workflow, you MUST start the OME workflow session by running:

ome ui $ARGUMENTS

This creates .ome/.session so the final ome finish command can record the execution into .ome/memory/executions/.

If a Windows PowerShell policy blocks the ome shim, run the same step through the cross-shell fallback: cmd.exe /c ome.cmd ui $ARGUMENTS. Do not hardcode this fallback on non-Windows platforms.

Claude Code fast path (other agents: ignore the leading ! and run the bare command via your shell tool):

!ome ui $ARGUMENTS

Purpose

Restore or implement UI from a design source while preserving project layout, theme, i18n, accessibility, responsiveness, and component conventions.

When to Use

Use for Figma, MasterGo, screenshots, design descriptions, or UI restoration requests.
Use when the output is a concrete UI component, view, or interaction.
Do not use for generic component scaffolding without a design target; use ome-comp.

Inputs

Design URL, screenshot, description, or component target.
Existing UI components, styles, tokens, routes, tests, and screenshots if available.
OME.md, .ome/rules/, and ome guidance ui-restore --input "<design-source>".
References: accessibility.md and testing.md.

Process

Load OME guidance and project rules before changing code.
Identify the design target, required states, responsive behavior, and asset needs.
Inspect existing UI patterns, tokens, typography, spacing, i18n, and test style.
Implement the smallest faithful UI slice using existing project conventions.
Verify responsive behavior, accessibility basics, and relevant tests.
If visual tooling is available, inspect the rendered result before final handoff.
Report changed files, UI behavior, verification, and remaining risks.

Red Flags

The design source is inaccessible or missing critical state details.
The implementation would invent a new theme, token system, or layout framework.
Text overlaps, controls lack accessible names, or keyboard behavior is broken.
The requested UI conflicts with existing project rules.

Read the full file on GitHub · 100 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 100 lines · 15 tokens per session scan A c58a312a57c4

Subscribe to this mod's changes

ome-ui is a skill published in the GitHub repository oh-my-engine/oh-my-engine (5 stars, last pushed 2mo ago), licensed MIT. It adds 15 tokens to every session and 857 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Design and UX Frontend ome ui workflow

ome-ui next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
ome-uioh-my-engine/oh-my-engine	Skill	5	2mo ago	MIT	A	15	Claude Code
absolute-uimaddhruv/absolute	Skill	223	4mo ago	MIT	A	121	Claude Code
ui-designfuturegerald/futuregerald-claude-plugin	Skill	7	2d ago	none	A	105	Claude Code
ve-terminal-mononexu-io/open-design	Skill	106k	yesterday	Apache-2.0	A	45	Claude Code, Codex
html-ppt-hermes-cyber-terminalnexu-io/open-design	Skill	106k	yesterday	Apache-2.0	A	53	Claude Code, Codex
tamagui-v6-configtamagui/tamagui	Skill	14k	today	MIT	A	0	Claude Code, Codex
tamagui-theme-generatortamagui/tamagui	Skill	14k	today	MIT	A	48	Claude Code, Codex

oh-my-engine: Skill for Claude Code