From buildable
Generates a local-first prototype from a natural language prompt using Buildable. Copies a runnable starter or writes a plan-only instruction pack. Also supports augmenting existing apps and adding auth.
How this command is triggered — by the user, by Claude, or both
Slash command
/buildable:buildable-generate <app idea prompt> [--out <dir>]This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
Generate a Buildable prototype for: **$ARGUMENTS** 1. Plan first, then generate. If `.buildable/phase-plan.json` exists and the prompt matches, generation reuses that saved audit-first plan. For runnable templates this copies a polished starter; for planned templates add `--plan-pack`: - If the CLI reports the prompt has architecture-changing choices, ask the user those questions, then rerun with `--force` only if the prompt already answers them. - If the CLI reports the template is not runnable yet, rerun with `--plan-pack` to write an instruction pack. - Add `--name "App N...
Generate a Buildable prototype for: $ARGUMENTS
Plan first, then generate. If .buildable/phase-plan.json exists and the prompt matches, generation reuses that saved audit-first plan. For runnable templates this copies a polished starter; for planned templates add --plan-pack:
buildable generate "$ARGUMENTS" 2>/dev/null || node "${CLAUDE_PLUGIN_ROOT:-.}/bin/buildable.mjs" generate "$ARGUMENTS"
--force only if the prompt already answers them.--plan-pack to write an instruction pack.--name "App Name" to brand the generated app, or pass a name in the prompt ("...called FocusList").--with-auth when the user explicitly wants login/accounts but did not include it in the prompt. Use --with-auth-provider <provider> only when the user names a provider.--augment (writes a plan that adapts to the current project without overwriting code).Read buildable-app-spec.json in the output directory and load only appSpec.references. Use .buildable/phase-plan.toon when present as the compact build contract for audit gates, references, screens, entities, features, and guardrails.
Adapt the starter (or implement the plan pack) to the user's specific request. Keep data local/mock by default. Do not add auth, billing, databases, telemetry, or deployment unless explicitly requested.
When code exists, verify it builds, then run /buildable-review on the output directory and fix blocking issues before handoff.
npx claudepluginhub suntay44/buildable-plugin-skills --plugin buildable/prototypeScaffolds minimal viable prototype for an idea: generates project structure, happy-path code, basic UI, single run command, file list, and production notes.
/build-appBuilds a full-stack web app (Spring Boot 3 backend + React frontend + SQLite DB) from a description by orchestrating AI agents in phases: planning, architecture, decomposition, and sprints.
/fire-scaffoldGuided multi-step wizard that scaffolds features and components — React components, API endpoints, database models, pages, hooks, services, and tests — with consistent structure and conventions within an active phase.
/roadmapGenerates ROADMAP.md for app builds from a brief and executes phases autonomously. Supports plan, start, resume, status modes with optional topic.
/brainstormYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores requirements and design before implementation.