rapid-prototype
/rapid-prototype
Use when building the product under time pressure — walking skeleton, thin vertical slices, mock-then-real, and keeping main demoable.
- Author
- lukashouthoofd ↗
- Repository
- cenekathon ↗
- Licence
- MIT
- Last repository change
- 04.11.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 04.11.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
Use when building the product under time pressure — walking skeleton, thin vertical slices, mock-then-real, and keeping main demoable.
Original author description
Use when building the product under time pressure — walking skeleton, thin vertical slices, mock-then-real, and keeping main demoable.
How it works
SKILL.md has no level-two headings · 15 lines, 209 words
SKILL.md preview
--- name: rapid-prototype description: Use when building the product under time pressure — walking skeleton, thin vertical slices, mock-then-real, and keeping main demoable. --- # Rapid prototype - **Walking skeleton:** one input → one real processing step → one visible output, deployed. Do this before any feature. - **Vertical slice = user-visible.** Each slice ends with something you can click or run in the demo. No "backend done, frontend later". - **Mock → real:** stub external or slow parts with clearly labelled fixtures (`MOCK` in the UI); wire the real thing after the slice works. Never present mocks as real. - **Boring tech.** Use what the team already knows. E.g. Next.js/Vite + a serverless function, or FastAPI + a simple page. SQLite / JSON file / Supabase over self-run Postgres. One repo, one deploy. - **Hardcode first,** generalize only if the demo needs it. No auth unless the brief demands it (use a fake user switch). - **Seed data:** commit a fixture so the demo works offline and after a fresh clone. - **Happy-path polish > edge cases.** The demo path must be flawless; everything else may fail gracefully. - **Timebox:** a slice not working after 45 min → cut scope, don't push on. - Commit + push after every working step. `main` must always run. **Done when:** the slice runs from a clean clone with the documented command and shows its result.
Versions
The database has no other skills named rapid-prototype.
Database snapshot: 13.11.2026 · package version ebd83b39a051 (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
- 82idea-to-mvp
Turns an idea note into a one-page spec and a small working prototype, then tracks it as a project. Use when I say build this idea, make an MVP, prototype something, or use my creative block on an idea from Ideas/. - 10003-story-mapping
Use when arranging an existing backlog into user activities, a walking skeleton, and release slices; use backlog-prioritization for economic ordering after the map exists. - 100write-user-stories
Write user stories with acceptance criteria. Use when the user says "write user stories", "convert this to stories", "create acceptance criteria", "break this into tickets", "story map", "walking skeleton", "story for this feature", or wants to translate a feature idea into… - 100to-issues
Break a wiki user story into vertical-slice tracer-bullet checkboxes (or refine existing slices), and in `github`/`gitlab` mode mirror `ready-for-agent` slices to the remote issue tracker with wikilinks back to the story file. Operates on `kind: story` files in the wiki. Quizzes…