mock — build and share UI design variations

Turn a rough idea or an existing interface into a single self-contained HTML file holding several design variations behind a top view-switcher, then get it in front of someone. The whole point is speed and low ceremony: don't over-interview, infer sensible defaults and confirm in one pass.

(The example above is what a finished mock looks like — one HTML file, the tabs top-right flip between variations. Everything is inline, so it renders the same opened from disk, as an email attachment, or at a URL with no network.)

Mode: build-only vs. publish

If the user asks for build-only — /mock --local, "just build the file", "build only", "don't publish", "no public link" — do Steps 1–2, skip the publish path (3A), and deliver via download and/or email only (3B/3C). This is the right default when there's no static host wired up or no need for a shareable URL.