feature-mockup

Generates self-contained HTML UI mockups and iterates them with the user into design decisions.

Updated May 26, 2026
One-click install
npx skills add https://github.com/cagriy/dev-skills --skill feature-mockup-cagriy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-mockup
Source: https://github.com/cagriy/dev-skills/tree/main/skills/feature-mockup
Command: npx skills add https://github.com/cagriy/dev-skills --skill feature-mockup-cagriy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a vague UI idea into a concrete, agreed visual direction is slow when it happens only in prose. This Skill renders the user-visible surface of a feature as static HTML mockup pages, publishes them as reviewable Claude Artifacts, and iterates with the user until one direction is accepted, returning the decisions to the calling design skill. ## Core Features & Use Cases - Grounded mockup generation: Reads the host project's existing design language (components, tokens, prior mockups) and produces self-contained, offline HTML pages that look like they belong in the project. - New vs. modify workflows: A brand-new surface gets one overall view; a modification to an existing surface gets 2-4 uniquely named alternatives that differ on a real axis such as placement, density, or typography. - Artifact publishing and iteration: Each page is published as a Claude Artifact with a stable URL, revised in place across feedback rounds, and the accepted result is returned as a parseable decision block to the calling skill. - Use Case: While designing a reminders feature for a todo app, the design skill invokes this Skill to render the reminder list and editor as an HTML mockup, the user picks a right-hand drawer layout, and the concrete UI decisions flow directly into the design document. ## Quick Start This Skill is not user-invocable; it runs automatically when the feature-design skill reaches its mockup step for a feature with a user-visible surface.

Frequently Asked Questions about feature-mockup

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

FAQPage Schema
How do I create a UI mockup during feature design?

Run the feature-design skill; when the feature has a user-visible surface it invokes feature-mockup automatically. The mockup pages are written as self-contained HTML under the feature folder and published as Claude Artifacts for review.

Can I invoke the feature-mockup skill directly?

No, feature-mockup is marked user-invocable: false and runs only as an internal step of other skills, currently feature-design. It receives the feature folder, version, and surface description from its caller.

Does the mockup use my project's existing design system?

Yes. The skill reads the project's UI layer, design tokens, and prior accepted mockups to build a design-language digest, and user-supplied visual references take precedence over project conventions on visual choices.

What happens if Claude Artifacts are unavailable in my session?

The skill falls back to presenting the local HTML file path and continues normally. The file under the feature folder's mockups directory is always the source of record, so publishing is preferred but never required.

When does feature-mockup skip making a mockup?

It returns status not-applicable when the feature has no user-visible surface, such as API-only changes, background jobs, or schema migrations. It also never runs when the user already fully specified the surface with their own reference.

Do mockup files get wired into my application code?

No. Mockups are non-functional, self-contained HTML stored only under the feature folder's mockups directory. The skill never edits application source, templates, styles, or build configuration.