Prototype
Builds throwaway prototypes to answer one design question — a logic demo or radically different UI variations
- What
- Builds throwaway prototypes to answer one design question — a logic demo or radically different UI variations
- Cost
- Free
- Needs
- a Muse account with skill installation enabled
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a prototyping skill built on one rule: a prototype is throwaway code that answers a question, and the question decides the shape. Two branches: "does this logic feel right?" becomes a single shareable HTML file (free-play buttons plus guided walkthroughs) that pushes a state machine through hard-to-reason-about cases, drivable by a non-developer; "what should this look like?" becomes several radically different UI variations on one route, switchable via URL param and a floating bar. Both obey the same discipline: throwaway from day one and clearly marked, trivial to run (one command or a double-click), no persistence by default, no polish, state surfaced after every action — and when done, the validated decision is folded into the real code while the prototype itself is captured on a throwaway branch as a primary source. By @mattpocock, listed here with credit to its creator. Honest caveats: picking the wrong branch wastes the whole prototype, so the skill asks (or states its assumption) when the question is ambiguous; prototypes live next to the real code by design, so a casual reader must see the "prototype" naming or they'll mistake it for production. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: a Muse account with skill installation enabled Install "Prototype" for me. Builds throwaway prototypes to answer one design question — a logic demo or radically different UI variations Repository: https://github.com/mattpocock/skills/blob/main/skills/engineering/prototype/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "mattpocock-prototype". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. save my API key in the vault). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.