← ClaudeAtlas

mock-uilisted

Turns a DESIGN.md plus a description of what the product must do into a clickable HTML mockup: one self-contained .html per screen with every button and link wired, an index.html screen map and a sitemap.json. Use when someone wants a mockup, wireframe or click-through prototype, asks to "prototype the screens" or "make HTML pages from this design", or wants screens planned before building a Power Apps app. Not for writing the design system itself (that is design-md) and not for converting HTML into Power Apps (that is create-app, which reads what this skill writes).
YKUNAKORN/Supuersub · ★ 0 · Web & Frontend · score 62
Install: claude install-skill YKUNAKORN/Supuersub
# Mockup: screen inventory, then linked HTML pages Produce a mockup folder: one `.html` per screen, `index.html`, `sitemap.json`. Reply in the user's language; visible text in the pages follows it, identifiers stay ASCII. Paths are relative to this skill's folder: `${CLAUDE_SKILL_DIR}`, or run from that folder. ## The workflow (in order) 1. **Inputs.** A `DESIGN.md` (a path, an attachment or pasted text) and the requirements: what the product does, for whom, which records it keeps, what happens on submit. With no `DESIGN.md`, say so and offer the `design-md` skill. If the user declines, agree a short style brief (primary colour, surface, text colour, font, corner radius) and record it in `index.html` and in `sitemap.json` as `styleBrief`. 2. **Target.** `power-apps` when the mockup is headed for `create-app` (the default when the `DESIGN.md` says `Target: power-apps` or the user mentions Power Apps), otherwise `web`. For `power-apps`, read [`references/shared/powerapps-profile.md`](references/shared/powerapps-profile.md) now; the canvas is 1366 × 768 unless the user says otherwise. 3. **Screen inventory before any HTML.** Show one table: screen id (`scr` + PascalCase), file name, title, purpose, the data it reads or writes (list and columns), and where each control leads or which action it fires. Mark the start screen. Check that every screen is reachable and has a way back. **Get the user's agreement**; changing a row now is cheap, chan