Skip to content
Skills Library
Design & UX · Building & coding

make-a-prototype

/make-a-prototype

Build a scoped interactive prototype to test a specific usability question. Use when static sketches cannot answer a flow or feedback question.

Repository
situate ↗
Licence
MIT
Last repository change
13.11.2026

Assessment and security

86/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content21 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Build a scoped interactive prototype to test a specific usability question. Use when static sketches cannot answer a flow or feedback question.

Original author description

Build a scoped interactive prototype to test a specific usability question. Use when static sketches cannot answer a flow or feedback question.

How it works

SKILL.md has no level-two headings · 23 lines, 331 words

SKILL.md preview
---
name: make-a-prototype
description: Build a scoped interactive prototype to test a specific usability question. Use when static sketches cannot answer a flow or feedback question.
---

# Make a prototype

Agree on the question, scenario, entry state and observable outcome. Choose the lowest fidelity that can answer it. A clickable storyboard is enough for navigation questions; editing, feedback or recovery questions may need working state.

Inspect existing tooling and components before introducing dependencies. Respect approved technology constraints for implementation-like prototypes; explicitly distinguish a disposable sketch from production architecture. Do not turn a prototype request into application implementation.

Use synthetic content and local fixtures. Do not connect real accounts, send messages, charge money or run live AI merely to demonstrate a flow. Identify simulated effects in the surrounding prototype notes; do not present them as implemented capabilities.

Implement the tested path and the relevant alternate or failure path. Keep state and feedback coherent:

- Controls required by the task work and have understandable labels.
- Back, cancel and retry behave consistently within the chosen scope.
- Pending, completed and uncertain outcomes are distinguishable where applicable.
- Keyboard focus and touch behavior suit the intended device.
- Out-of-scope controls do not falsely imply working effects.

Add persistence, animation and simulated latency only if the test needs them. Do not require a design system or high-fidelity visuals for an early flow test.

Run through the scenario in the rendered artifact, including its important interruption. Check console errors and relevant automated tests when available. State exactly what was exercised, what is simulated and what could not be verified. Code inspection alone is not proof of rendered behavior.

Create Situate app prototypes in the independent [Vue design workshop](../../../../docs/development/design-workshop.md) under `client/workshop/`. Use its own Vue components, styles and brand snapshot, without live imports from the product. Share the technology and conventions, not mutable UI source. Keep synthetic fixtures, simulated services and proposal notes separate from production services and the requirements catalog. Copy and integrate selected designs into production only after explicit implementation approval; do not synchronize automatically or create a standalone HTML replica. Report the test question, working scope, limitations and next decision.

Versions

The database has no other skills named make-a-prototype.

Database snapshot: 13.11.2026 · package version 7a2b88e37992 (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

  • 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, then turn the answer into a Spec. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
  • 90prototype
    Build a temporary prototype to answer a design question. Use to judge a state model, business logic or alternative UI designs.
  • 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.
  • 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.
  • 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.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.