- Home
- Skills
- Frontend & Web Apps
- Create Mockup — UI From Scratch, Matched to Your Stack
More screenshots
Works with the AI tools you already use
Create Mockup — UI From Scratch, Matched to Your Stack
Interviews you on site type, look and pages, then builds accessible Astro, React or plain-HTML mockups with Tailwind CSS v4 that follow your CLAUDE.md, DESIGN.md and BRIEF.md. No Figma file needed.
$19
Create Mockup — UI From Scratch, Matched to Your Stack
Example session with this skill installed
Create a landing page for a small specialty coffee roaster.
- Read your context and instructions
- Compiled the create mockup
- Generated the app files
The skill first reported the stack it found: "Astro v7, Tailwind CSS v4 (@tailwindcss/vite), icons: @lucide/astro, linter: Biome, CSS: src/styles/global.css, images: src/assets/images/", no DESIGN.md, no BRIEF.md, and all six companion skills detected. Then it asked:
| Step | Question | Answer |
|---|---|---|
| Setup | New project or add to existing? | Start fresh |
| Setup | How much creative direction? | Avoid generic AI look |
| Setup | Japanese-language site? | No |
| Setup | How far to break from default layouts? | Balanced |
| Setup | Run a requirements interview first (brief-me)? | Yes, which wrote BRIEF.md: B2C, 20s to 30s and price-sensitive, freshness and value, goal = purchase or subscribe, avoid flashy effects |
| Setup | How busy should decoration be? (this question is now asked only for Japanese sites) | Restrained |
| Design | Colors, mood, images | White base with one bold accent, modern and minimal, free stock photos from Unsplash |
| Sections | Core and optional sections | Hero with CTA, featured beans and prices, how it works, subscription plans, roastery story, visit the roastery |
| Finish | What next? | Finish here |
What it decided from those answers
| Decision | Result |
|---|---|
| Layout | A zigzag carried by typography and numbers instead of alternating image rows. The hero is an asymmetric split, not 50/50, with a framed photo offset lower. |
| Conversion | The header button is not the only CTA: an inline link sits at the last "how it works" step. In the plans, one button is filled and the other two are outlined, so the anomaly is deliberate. |
| Color | Achromatic base plus one accent (cherry red), defined as @theme tokens (--color-surface, --color-surface-alt, --color-ink, --color-muted, --color-border, --color-accent). White background, because the brief gave no reason to tint it. |
| Restrained | Extra whitespace between sections, the accent used only for buttons, one eyebrow label and link hovers, and no motion beyond a color change on buttons. |
What it built: Layout.astro (lang set to en), Header.astro, Footer.astro, index.astro with six sections, the @theme block, and four optimized photos.
Checks it ran: duplicate classes, default-palette classes, space-* / divide-*, typed uppercase and aria-labelledby references all returned 0 hits. Biome, astro check and the build passed, and the dev server was left running.
Three problems found while checking the page in the browser, and fixed:
- The hero photo dropped below the text: grid auto-placement pushes an overlapping item to the next row. Fixed by placing both items on the same row explicitly.
- The heading ended with one word alone on the last line, and the first attempt at an overlap covered its final period. Headings now use
text-wrap: balanceand paragraphstext-wrap: pretty, and the overlap was removed. - After that, a scan for one-word last lines found none at 390px or 1440px, with no horizontal overflow.
Not covered: the navigation list is hidden below the md breakpoint (no mobile menu yet), the copy, prices and address are placeholders, and the photos are Unsplash stock images.
create-mockup-ui-from-scratch-matched-to-app.zip
ZIP · project files
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
What you get
About this skill
A skill that builds UI mockups from scratch — no Figma file needed — after a short interview, in the style your project already uses. Ask an agent for "a landing page" and you tend to get the same centered hero, the same purple gradient, and code that ignores how your project is set up. This skill puts a few batched questions in front of the build (site type, look, pages, sections, images), detects your stack first, follows your project files, and finishes by checking the result and starting the dev server.
What it does
- Detects the framework, router, icon library, style utilities and linter from
package.json(Astro, React, or plain HTML with Vite), then reads only the reference for that mode - Asks about site type, design style, page type and sections in one or two batched questions, not a long form
- Defines your colors as Tailwind CSS v4
@themetokens, and avoids token names that collide with built-in utilities - Treats
DESIGN.mdas the source of truth when you have one, and usesBRIEF.mdas requirements context when it exists - Builds accessible markup: nav lists, labelled inputs, uppercase applied as a style instead of typed in the HTML, no dangling aria references
- Checks for duplicate and conflicting classes, runs your linter and build, and starts the dev server
How it works
- Reads your project:
package.json,CLAUDE.md, andDESIGN.md/BRIEF.mdif present, then reports the stack it found. - Asks the setup questions: new project or an addition to an existing one, and how much creative direction you want.
- Asks about the design: site type, colors and mood, images, pages and sections.
- Builds: cleans up starter demo content, then implements the pages.
- Checks and runs: class checks, lint and build, then starts the dev server and gives you the URL.
Works with (all optional)
If one of these is installed, the skill offers the matching question. If it is not, the question is skipped.
- Brief Me (brief-me): a requirements interview that writes BRIEF.md first
- Escape AI Slop (cognitive-ui-design): layouts that break the centered-hero default
- Japanese Web Guideline and Japanese LP Seasoning: typography, carousels, scroll reveals and vertical text for Japanese sites
- Code to Figma: export the finished page to Figma
- Anthropic's
frontend-designplugin: a bolder design direction
Requirements
Tailwind CSS v4 is required. The skill stops and points you to the install guide if the project uses Tailwind v3 or no Tailwind at all. You also need a project with a package.json and a CLAUDE.md in the project root (run /init first if it is missing), and Node.js. Stock photos are downloaded from Unsplash to your image folder, which needs internet access; you can choose solid-color placeholders instead. It does not set up a new project for you.
Live demo
A page built with this skill from one short request, a landing page for a fictional coffee roaster: https://create-mockup-demo.gaspanik.workers.dev/
The questions it asked and the decisions it made are in the example session above.
More from KMRVID
The full Claude Code skill bundle for Figma, Tailwind and Astro workflows is available on Gumroad: https://gaspanik.gumroad.com/l/kmrvid-claudeskills
How to install
Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.
- 1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
- 2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
- 3
Ask your agent to use it
Restart the agent if it was already running. It picks the skill up automatically - no config needed.
Skills folder by agent
Click the path to copy it. Create the folder if it does not exist yet.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
30-day refund
Not a fit? Get your money back
Trust & safety
Security scanned
Verified clean 3 days ago
- Passed all security checks, Safe to install