authoring-hi-fi

Generate high-fidelity UI designs as runnable code from wireframes and design-system tokens.

1|1|Updated May 24, 2026
One-click install
npx skills add https://github.com/bm629/agent-skills --skill authoring-hi-fi-bm629
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: authoring-hi-fi
Source: https://github.com/bm629/agent-skills/tree/main/skills/authoring-hi-fi
Command: npx skills add https://github.com/bm629/agent-skills --skill authoring-hi-fi-bm629

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning wireframes into polished, high-fidelity UI screens by hand is slow and error-prone: tokens drift, states get skipped, accessibility issues surface late, and unrendered code hides visual defects. This Skill produces each wireframe-named screen as runnable code (HTML+Tailwind or React+shadcn), rendered headlessly and vision-reviewed before handoff. ## Core Features & Use Cases - Token-backed code generation: Maps design-system/DTCG tokens into CSS custom properties, Tailwind utilities, and shadcn themes so no raw hex or pixel values bypass the token layer. - Render-vision-review loop: Generates code, renders it headlessly via a browser, screenshots per viewport and state, vision-reviews against the wireframe and design system, then refines within a bounded iteration cap. - Numeric WCAG 2.2 AA checks on the render: Verifies contrast ratios, focus visibility, and target sizes with axe-core on the actual rendered output, never disabling rules. - Scoped amend mode: Applies changes as versioned deltas, rippling token edits through the map once and re-rendering only affected screens. - Use Case: Given wireframes for a Projects list screen with empty, loading, populated, and error states plus a design system, produce four rendered, token-backed, WCAG-passing screens as a build seed for engineers. ## Quick Start Use authoring-hi-fi to realize the screens in my wireframes document as rendered HTML+Tailwind code using the tokens from my design-system doc.

Frequently Asked Questions about authoring-hi-fi

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn wireframes into high-fidelity UI code?

Provide the wireframes and design-system documents, then the Skill derives one rendered screen per wireframe-named screen and state. It maps design tokens into Tailwind or shadcn themes, renders each screen headlessly, and vision-reviews screenshots before handoff.

Should I use HTML+Tailwind or React+shadcn for hi-fi prototypes?

Standalone HTML+Tailwind is the default because it renders headlessly with no toolchain. Switch to React+shadcn when the project's build stack is React, so the seed sits close to the build target and minimizes drift.

Does this work without a vision-capable AI runtime?

A vision-capable runtime is required for the render-review loop. A text-only run produces blind codegen and is treated as degraded; the Skill surfaces this explicitly rather than presenting unverified renders as reviewed.

How are WCAG accessibility checks enforced on generated UI?

Contrast (4.5:1 and 3:1), focus visibility, and 24px target sizes are checked numerically on the rendered output using axe-core plus vision review. Failures are fixed at the token layer, and disabling an axe rule is treated as a finding.

What are the limitations of the generated hi-fi code?

The output is a build seed, not production code: it intentionally omits tests, real backends, and routing. It also never invents tokens or screens; missing design-system elements are surfaced as gaps for the design-system owner.