메뉴
Complete SaaS ideation to implementation workflow - from idea discovery to task breakdown
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Expert guidance for creating, building, and using Claude Code agents and the Task tool. Use when working with agents, setting up agent configurations, understanding how agents work, or using the Task tool to launch specialized agents.
Run structured APEX implementation (Analyze, Plan, Execute, eXamine) with parallel agents, tests, adversarial review, and proof-backed verification. Use for features, bug fixes, or code changes that need disciplined execution and real-flow evidence.
Deep iterative research using progressive flow psychology (diverge-analyze-converge-execute) with parallel agents, skeptical analysis, and multi-perspective synthesis. Use for thorough topic exploration, decision-making research, or when you need battle-tested conclusions.
Automated CI/CD pipeline fixer - watches CI, fixes errors locally, commits, and loops until green. Use when CI is failing and you want to automatically fix and verify changes.
Improve unclear UX copy, error messages, microcopy, labels, and instructions. Makes interfaces easier to understand and use.
Clean Code rules for TypeScript, React, and Next.js. Apply when writing, refactoring, or reviewing code - naming, small functions, no any, early returns, typed errors, plus tech-specific rules for React 19, Next.js 15/16, Zustand v5, TanStack Query v5.
| name | aibuilder-create-saas |
| description | Complete SaaS ideation to implementation workflow - from idea discovery to task breakdown |
| argument-hint | [project-name] |
| disable-model-invocation | true |
| allow_implicit_invocation | false |
This workflow responds in the user's language while prompts are in English. It's designed for solo developers learning Next.js with Prisma and Better-Auth who want to build a monetizable SaaS in less than 2 weeks.
<quick_start> Start a new SaaS project (interactive discovery):
/create-saas
With custom project name:
/create-saas my-awesome-saas
Continue existing project:
/create-saas -c my-awesome-saas
What it does:
Outputs saved to ~/.claude/output/saas/{project-id}/
</quick_start>
Flags:
-a / -A - Auto mode: skip confirmations (default: false)-s / -S - Save mode: save outputs to files (default: true)-c <project-id> - Continue mode: reload existing project and resume where you left off
<state_variables> Core Variables (persist throughout all steps):
| Variable | Type | Description |
|---|---|---|
{project_name} | string | SaaS project name |
{project_id} | string | Kebab-case identifier for folders |
{auto_mode} | boolean | Skip confirmations |
{save_mode} | boolean | Save outputs to files |
{output_dir} | string | Path to output folder |
{user_language} | string | User's preferred language |
Accumulated State (grows across steps):
| Variable | Set In | Description |
|---|---|---|
{discovery_answers} | Step 1 | User's answers to discovery questions |
{has_previous_project} | Step 1 | Whether user built a project before |
{ideas} | Step 2 | List of 3-6 brainstormed ideas |
{selected_idea} | Step 2 | User's chosen idea |
{validated_idea} | Step 3 | Fully developed and validated idea |
{prd_content} | Step 4 | Product Requirements Document |
{architecture} | Step 5 | Technical architecture decisions |
{tasks} | Step 6 | List of implementation tasks |
</state_variables>
<entry_point>
Load steps/step-00-init.md
</entry_point>
<step_files>
| Step | File | Description |
|---|---|---|
| 0 | steps/step-00-init.md | Initialize: parse flags, create output folder |
| 1 | steps/step-01-discovery.md | Discovery: ask questions to find the right idea |
| 2 | steps/step-02-brainstorm.md | Brainstorm: generate 3-6 ideas, user chooses one |
| 3 | steps/step-03-validate.md | Validate: research, challenge, develop the idea |
| 4 | steps/step-04-prd.md | PRD: create Product Requirements Document |
| 5 | steps/step-05-architecture.md | Architecture: design technical stack |
| 6 | steps/step-06-tasks.md | Tasks: split into actionable implementation tasks |
| </step_files> |
<workflow_diagram>
┌──────────────┐ ┌───────────────┐ ┌───────────────┐
│ Step 0 │────►│ Step 1 │────►│ Step 2 │
│ Initialize │ │ Discovery │ │ Brainstorm │
└──────────────┘ └───────────────┘ └───────┬───────┘
│
┌────────────────────────┘
│ ▲
▼ │ (if not validated)
┌───────────────┴─┐
│ Step 3 │
│ Validate │
└────────┬────────┘
│ (if validated)
▼
┌───────────────┐ ┌───────────────┐
│ Step 4 │────►│ Step 5 │
│ PRD │ │ Architecture │
└───────────────┘ └───────┬───────┘
│
▼
┌───────────────┐
│ Step 6 │
│ Tasks │
└───────────────┘
</workflow_diagram>
<output_structure>
When {save_mode} = true, creates:
~/.claude/output/saas/{project_id}/
├── discovery.md # Discovery answers and insights
├── idea.md # Validated idea with all details
├── prd.md # Product Requirements Document
├── archi.md # Technical Architecture
├── marketing.md # Marketing strategy notes
└── tasks/ # Implementation tasks
├── 01-setup.md
├── 02-auth.md
├── ...
</output_structure>
<success_criteria>
~/.claude/output/saas/{project-id}/Scripts:
scripts/setup.sh <project_id> - Creates output folder structurescripts/rename-project.sh <old> <new> - Renames project and updates all project_id referencesBase Project: