mockup-architectlisted
Install: claude install-skill ralvarez-ai/ralvaskills
# Mockup architect
How to build mockups that can be compared, screenshotted and decided on. Companion to
[landing-page-designer](../landing-page-designer/SKILL.md) (what a landing page must say) and
[ui-ux-architect](../ui-ux-architect/SKILL.md) (what the shipped UI must satisfy).
## 1. Rules
- **Self-contained.** One `.html` opens from `file://`: inline or sibling CSS/JS, no build step, no CDN.
A mockup never imports the app's code.
- **Dated folder** `mockups/<collection>/<YYYY-MM-DD>/`, an `index.html` gallery linking every page, and a row
in the collection README (file, what it decides). Superseded rounds move to `archive/`; do not edit them.
- **Tokens, not literals.** Colours, radii and fonts are CSS variables on `:root`; variants are
`:root[data-<axis>=<value>]` blocks. Same names as the app (`--bg --card --text --muted --line --line-strong
--accent --btn-bg --btn-fg --shadow`) so the bar and the port both work.
- **One question per page.** A page that offers options says what is being decided and recommends one.
- **Honest data.** Numbers are real or marked sample.
- **Draw, do not ship.** Mockups never touch the app's source.
## 2. The preview bar (use it whenever a page offers options)
`assets/pv-bar.css` + `assets/pv-bar.js`; `assets/example.html` is a working page. Copy both files next to the
mockups (or inline them); do not link across repos.
1. Declare axes in `<script type="application/json" id="pv-config">` in `<head>`, before `pv-bar.js`. Each a