prototype-builder
/prototype-builder
Build a disposable prototype in playgrounds/: a landing page mock, concept page, email preview, ad board. Use when someone wants a prototype, not a deck.
- Author
- calven-ai ↗
- Repository
- marketing-as-code ↗
- Licence
- MIT
- Last repository change
- 22.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 22.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Build a disposable prototype in playgrounds/: a landing page mock, concept page, email preview, ad board. Use when someone wants a prototype, not a deck.
Original author description
Build a disposable prototype in playgrounds/: a landing page mock, concept page, email preview, ad board. Use when someone wants a prototype, not a deck.
How it works
- Procedure
- Rules
SKILL.md preview
---
name: prototype-builder
description: Build a disposable prototype in playgrounds/: a landing page mock, concept page, email preview, ad board. Use when someone wants a prototype, not a deck.
license: MIT
metadata:
kind: workflow
area: core
needs: []
writes: repo
runs: person
---
# Prototype builder
Come to meetings with the thing itself, not a deck about it. Build the
smallest artifact that makes the idea judgeable.
## Procedure
1. **Load `brand/`** (voice, visual identity, `tokens.json`) and the
relevant `strategy/` context. On-brand prototypes get judged on the idea;
off-brand ones get judged on the wrong fonts.
2. **Create `playgrounds/YYYY-MM-DD-<slug>/`** containing:
- The prototype itself. Default form: **a single self-contained HTML
file** (inline CSS, brand tokens applied, no build step, no CDN) that
opens in any browser. An email sequence is one page showing each email
in sequence; an ad board is one page of variants side by side.
- A `README.md`: the one-sentence idea, what feedback is sought, and
"disposable: decision goes to memory/decision-log.md".
3. **Fake honestly.** Placeholder metrics, imagery, and quotes are fine if
you label them as fake in-context (e.g. "[illustrative]"). Never
fabricate a real customer's endorsement.
4. **After the meeting** (when told the outcome): log the decision via
`log-decision`, then move the prototype folder to
`playgrounds/_archive/`.
## Rules
- Never production: nothing in `playgrounds/` ships, gets published, or gets
linked externally.
- Speed beats polish, brand beats speed: rough is fine, off-voice is not.
Versions
The database has no other skills named prototype-builder.
Database snapshot: 13.11.2026 · package version b7207956baa8 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90prototype
Build a throwaway HTML or in-app prototype that answers one design question. Use when the user wants to try a state model or UI idea before committing, or says "mock it up", "prototype", "what should this look like". - 90landing-page
Write landing page copy for a campaign and mock it as a prototype. Use when "landing page for X", "campaign page copy". - 100prototype
Build a throwaway prototype to answer a design question via UI variations or a state walkthrough. Use for /prototype, the plan-canvas design flow or brainstorm. - 90prototype
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like. - 100mock
Build a throwaway interactive prototype to validate one unresolved interaction or behavior before writing production code. Use when the user explicitly asks to "mock it up first" or "prototype this", or when competing UI behaviors need a disposable hands-on comparison. - 82prototype
Build a throwaway UI prototype for the user to react to before any real code. Read this skill when the user asks for a mockup or a prototype of a UI. Use it when a design decision depends on look, feel, or flow that text cannot settle.