From buildable
Classifies app ideas, selects archetypes, decides ask-vs-build, and produces a phase plan plus local-first app spec with mock data and reference inputs.
How this skill is triggered — by the user, by Claude, or both
Slash command
/buildable:plannerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill to classify prompts, choose an archetype, decide whether questions are needed, and produce a top-down phase plan plus app spec.
Use this skill to classify prompts, choose an archetype, decide whether questions are needed, and produce a top-down phase plan plus app spec.
Resolve all referenced paths from the Buildable plugin or repository root.
Use Buildable only for app planning, app generation, UI/UX product guidance, or prototype review. Do not activate globally for unrelated coding tasks.
Mandatory order:
buildable plan "<prompt>" when available. Use --file <path>, --reference <path>, or --screenshot <path> for explicit user-provided files. It saves .buildable/phase-plan.md/json/toon by default; use --no-write only for terminal-only inspection.appSpec.references.appSpec.referenceInputs supplied by the user.knowledge/ or templates/ directories.Use knowledge/INDEX.md and templates/INDEX.md only for discovery when the CLI is unavailable.
buildable plan "<prompt>" when the CLI is available.core/archetype-registry.json tags for lightweight matching before opening archetype docs.core/ask-vs-build-policy.md.core/activation-policy.md.knowledge/archetypes/<archetype>.md.knowledge/data-models/ and knowledge/screen-graphs/ when they exist.templates/<target>/<archetype>/template-spec.json.core/design-system-registry.json and include it as appSpec.designSystem.blocks/registry.json and include them as appSpec.blocks; append only selected block references to appSpec.references.appSpec.mockData with realistic local seed-data guidance and state coverage.appSpec.referenceInputs when users attach screenshots/files; preserve paths and inspection instructions without pasting file contents into the prompt.appSpec.promptRefinement with assumptions, optional sharpening questions, and default answers.appSpec.planAudit with audit-first gates for scope, template status, references, mock data, UI/UX, local-first rules, auth/persistence, and review.core/app-spec-schema.md.appSpec.questions first when questionsNeeded is true.promptRefinement.optionalQuestions only if they would materially improve the result.promptRefinement defaults instead of continuing to interrogate..buildable/phase-plan.json or .buildable/phase-plan.toon compact contract, then load only appSpec.references and the selected starter source.appSpec.auth and the auth references. Default to local/mock auth behind an auth seam; do not choose a hosted provider unless the user names one.Load only what the selected app needs. Do not browse all archetype files. For a todo prompt, prefer:
knowledge/archetypes/task-manager.mdknowledge/data-models/task-manager.mdknowledge/screen-graphs/task-manager.mdtemplates/web/task-manager/template-spec.jsontemplates/web/task-manager/TEMPLATE_PLAN.mdReturn:
appSpec.designSystemappSpec.blocks reusable guidanceappSpec.mockDataappSpec.planAudit audit gatesappSpec.promptRefinement assumptions and optional questions with defaultsappSpec.referenceInputs the builder should inspectnpx claudepluginhub suntay44/buildable-plugin-skills --plugin buildableGenerates or adapts local-first web app prototypes from Buildable app specs, archetypes, UI patterns, and design playbooks. Activates when building or adapting a web app/prototype with Buildable guidance.
Creates structured product plans and build plans with acceptance criteria, architecture, and verification using the planr CLI.
Generates phased roadmaps for full application builds and executes autonomously—committing, deploying, testing phase-by-phase. Modes: plan, start, resume, status.