Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From SaaS Factory
Produce the demoable increment for a phase — start the preview, seed data, execute the phase demo click-script end to end, capture screenshots per step, and present a review checklist so the user can approve, request changes, or reject before more tokens are spent.
How this skill is triggered — by the user, by Claude, or both
Slash command
/saas-factory:demo [PHASE-## (default: the building/demo-ready phase)][PHASE-## (default: the building/demo-ready phase)]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Phase: $ARGUMENTS or `.saas-factory/bin/sf active-phase`.
Phase: $ARGUMENTS or .saas-factory/bin/sf active-phase.
Read phases/PHASE-##.md (demo script) and project.json (preview commands).
bin/sf phase-stats PHASE-## — if unverified tasks remain,
list them and stop (offer /saas-factory:build).sf journeys), then saas-factory:design-reviewer
views every capture and grades the craft; — it seeds data, boots
previews in background, walks the demo script, saves screenshots to
.saas-factory/demos/PHASE-##/, hunts dead buttons, records evidence, and
sets the phase demo-ready (or files precise FAILs).demos/PHASE-##/DEMO.md: how to try it live (commands + URL; Expo
QR note for mobile; Tauri/Electron dev command for desktop), the click-path,
and the screenshot gallery inline.bin/sf budget show) + rough next-phase projection, then AskUserQuestion:
Approve → run /saas-factory:phase approve PHASE-##.
Request changes → collect feedback → spawn requirements-analyst to turn
it into REQs scoped to this phase → planner amends → offer /build.
Reject / wrong direction → offer /saas-factory:phase reject PHASE-##
(explains rollback + backup branch) — fail fast beats burning more tokens.npx claudepluginhub usmanali4073/claude-code-saas-factory-plugin --plugin saas-factoryGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.