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)
- 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 noDESIGN.md, say so and offer thedesign-mdskill. If the user declines, agree a short style brief (primary colour, surface, text colour, font, corner radius) and record it inindex.htmland insitemap.jsonasstyleBrief. - Target.
power-appswhen the mockup is headed forcreate-app(the default when theDESIGN.mdsaysTarget: power-appsor the user mentions Power Apps), otherwiseweb. Forpower-apps, readreferences/shared/powerapps-profile.mdnow; the canvas is 1366 × 768 unless the user says otherwise. - 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, changing ten HTML files is not. - Generate the token block:
python3 ${CLAUDE_SKILL_DIR}/scripts/tokens_to_css.py DESIGN.md --target <target>(scripts/tokens_to_css.py). Paste its:rootblock unchanged as the first thing in every page's<style>. With only a style brief, write the same variable names by hand. - Write the pages from
assets/page.template.html, followingreferences/html-contract.mdand the building blocks inreferences/screen-patterns.md. Write the shared chrome first, then paste it unchanged into every screen. Write every screen in full: every row, field, card and navigation item, never "repeat for the rest".assets/example/is a finished, lint-clean three-screen mockup; read it for the level of detail, never copy its content. - Write
sitemap.json(schema:assets/sitemap.schema.json) andindex.htmlfromassets/index.template.html. - Lint with
python3 ${CLAUDE_SKILL_DIR}/scripts/mock_lint.py supersub/mockup --design DESIGN.md(scripts/mock_lint.py; the target comes fromsitemap.json). Fix every error and lint again until the verdict has no errors. Report every warning with the fix you made or the reason it stands. - Hand over (next section).
Rules
- Self-contained. One inline
<style>, no web font, CDN, remote image or script. Icons are inline SVG; images are placeholder boxes withdata-image="<what it shows>". - No dead controls. Every link and button navigates (
data-navplus a realhrefor formaction, so it works from disk with JavaScript off) or names its action (data-action="submit:Requests",run-flow:NotifyApprover), or both. - Real form controls. A choice is a
<select>with its real options or radios, a date is a date input, every field has a<label for>. Data-backed fields carrydata-field, their formdata-source; repeated data sits indata-repeatwith two or three full sample rows. - Tokens first. Every colour, font, size, radius and spacing value is
var(--…)from the generated block. Geometry is px. - Under
power-apps: explicit px canvas on<body>, px geometry throughout, no effect the profile rules out. When the user still wants one, mark the elementdata-unsupported="<profile id>"and scope the CSS to that mark, so the intended look is visible andcreate-appknows to declare it and apply the substitute. - Original content. Invent names and sample data; never reproduce another product's branding or a real person's details.
- One mockup folder per product. Write it under
supersub/mockup/in the project when one is writable; otherwise create the files and hand them to the user.
Hand-off
references/shared/handoff.md is the contract between
the five skills. Never assume an earlier skill ran. Hand over:
- the files, and how to open the mockup: double-click
index.html, or open it in a browser, then click through; - the lint verdict and every warning;
- the lists the mockup implies: every
data-sourceanddata-repeat, with the columns fromdata-field; - the flows it implies: every
run-flow:action, with the screen and control that triggers it; - the next steps:
create-appconverts each screen into a.pa.yaml;create-listbuilds the lists;create-flowplans the flows.