Basinfy/Basinfy-SaaS-Studio / .agents/skills/saas-prototype
saas-prototype
UnverifiedBuild isolated throwaway prototypes or spikes to validate risky UX or technical assumptions.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.9 KB |
| references/1-question.md | markdown | 3.6 KB |
| references/2-load-context.md | markdown | 1.0 KB |
| references/3-choose-path.md | markdown | 1.9 KB |
| references/4-plan.md | markdown | 1.3 KB |
| references/5-implement.md | markdown | 4.5 KB |
| references/6-debrief.md | markdown | 2.6 KB |
| references/7-report.md | markdown | 1.0 KB |
| references/8-cd-review.md | markdown | 815 B |
| references/9-summary.md | markdown | 3.8 KB |
| references/spike-mode.md | markdown | 3.9 KB |
SKILL.md
View on GitHub---
name: saas-prototype
description: "Build isolated throwaway prototypes or spikes to validate risky UX or technical assumptions."
argument-hint: "[concept-description] [--path html|engine|paper] [--review full|lean|solo] [--spike]"
user-invocable: true
---
<!-- Generated from .claude/skills by scripts/sync-agent-skills.py. -->
## Running this workflow on this client
Run commands from the project root (use Git Bash on Windows if `bash` points to an unavailable WSL distro). Shared studio files live in `.claude/`; follow `.agents/PORTABLE-RUNTIME.md` and `.claude/docs/config-resolution.md` for client tools, delegation, and approval rules.
Run `bash .claude/hooks/yaml-helper.sh resolve_config --keys locale,review_mode,automation,workflow` and use its output below.
Resolved above — use as-is; `--review` overrides `review_mode` for this run. No
block → defaults in `.claude/docs/config-resolution.md`.
# Prototype
> **Locale & User Profile**: Match `locale` (`pt-BR` → natural Brazilian Portuguese questions/options, overriding English examples; `en` → English) and `user_profile` (`founder` → plain business language with `(Recomendado)` first, zero tech jargon; `developer` → technical). Keep code/tests in English.
## Purpose
This is the **concept prototype** — a fast, throwaway build that answers one question:
*"Is this core idea actually fun to interact with?"*
**Default use** — run right after `/saas-brainstorm` and `/saas-setup-stack`, before writing
PRDs or architecture docs. Its verdict determines whether the concept is worth the
investment of full design documentation.
**Mid-production?** You can also run this at any stage to test a specific feature or workflow,
design change, or technical question. Pass `--spike` to activate spike mode: a
lightweight ~4-hour build with no PRD prerequisites and no phase gate implications.
**Already have PRDs and architecture complete?** To validate the full application lifecycle
before committing to Production, run `/saas-vertical-slice` instead.
---
## Phase 1: Define the Question
**Read `references/1-question.md` now and follow it** — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
## Phase 2: Load Concept Context
**Read `references/2-load-context.md` now and follow it** — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
## Phase 3: Choose the Prototype Path
**Read `references/3-choose-path.md` now and follow it** — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
## Phase 4: Plan the Prototype
**Read `references/4-plan.md` now and follow it** — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
## Phase 5: Implement
**Read `references/5-implement.md` now and follow it** — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
## Phase 6: Usability test Debrief
**Read `references/6-debrief.md` now and follow it** — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
## Phase 7: Generate Prototype Report
**Read `references/7-report.md` now and follow it** — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
## Phase 8: Creative Director Review
**Read `references/8-cd-review.md` now and follow it** — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
## Phase 9: Summary and Next Steps
**Read `references/9-summary.md` now and follow it** — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
## Spike Mode
**Triggered by:** `--spike` flag OR "Mid-production spike" entry choice in Phase 1.
**Read `references/spike-mode.md` now and follow it** — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
### Important Constraints
- Prototype code must NEVER import from production source files
- Production code must NEVER import from prototype directories
- If the recommendation is PROCEED, production implementation is written from
scratch — prototype code is never refactored into production
- Total effort is hard-capped at 1 day (concept prototypes test one core workflow)
- Test ONE core workflow — if scope grows, stop and simplify the question
- No polish. No extra menus, no unnecessary UI unless it IS the core workflow
- If stuck after 2 hours of engine iteration, reframe the question or switch paths
- **3 PIVOT iterations → force a KILL decision.** If this is the third time the
same concept has produced a PIVOT verdict, the concept likely doesn't work.
Ask: "Is this the right idea, or am I in the sunk cost trap?" A new concept
prototyped fresh will almost always beat a fourth iteration of a struggling one.
- Building 2-3 different concept variants and picking the best one is a healthier
strategy than iterating one concept to death. Natural selection between prototypes
beats willpower.
- **Real-time collaborative / multi-tenant products:** A local prototype cannot validate the latency characteristics of a distributed system. Network delay fundamentally changes how collaborative editing, real-time sync, optimistic UI updates, and conflict resolution perform — a prototype running at 0ms local will behave entirely differently under 100ms WAN latency. Use a local prototype to validate that the workflow is *intuitive and functional*. Do not use it as conclusive evidence of multi-user sync performance without simulated network latency or staging load.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |