Basinfy/Basinfy-SaaS-Studio / .agents/skills/saas-prototype
saas-prototype
UnverifiedConcept prototype before PRDs — throwaway HTML, Engine or Paper build, PROCEED/PIVOT/KILL/NOT ASSESSED. After /saas-brainstorm and /saas-setup-stack.
Running this workflow on this client
Run shell commands from the project root. On Windows, use Git Bash for the bash commands if bash resolves to an unavailable WSL distribution. Shared studio files are under .claude/; run the local Studio installer for this project if those files are missing. Read .claude/docs/config-resolution.md and apply its defaults when configuration cannot be resolved. Use this client's tools for reads, edits, and structured questions. If structured questions are unavailable, ask in chat and wait when a decision requires approval. Use the client's delegation feature with the role brief in .claude/agents/ when available. Otherwise perform the specialist checks in sequence and disclose that they were done in one session. If a workflow requires independent sign-off, report it as pending until an independent reviewer can provide it. Treat Task* steps as local workflow tracking using the client's equivalent when available. Report missing tools and unexecuted checks explicitly.
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
Interaction Localization Rule: When
locale: pt-BR(or user speaks Portuguese), ALL questions (AskUserQuestion/ask_question), confirmation prompts, and selectable options MUST be translated and presented in Brazilian Portuguese (PT-BR). Any English question text or options in this skill are illustrative examples — NEVER display English questions or options to a Portuguese developer. Internal reasoning, code synthesis, tests, and documentation files MUST remain 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 |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 114k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 114k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 114k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 114k | Updated | Claude CodeCodex | Verified | Install |