From buildable
Generates 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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/buildable:web-builderThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill to generate or adapt local web prototypes.
Use this skill to generate or adapt local web prototypes.
Resolve all referenced paths from the Buildable plugin or repository root.
Use only when the user is building or adapting a web app/prototype. Do not activate for unrelated frontend debugging unless the user asks for Buildable guidance.
Mandatory order:
.buildable/phase-plan.json when present, otherwise buildable-app-spec.json. Use .buildable/phase-plan.toon when present as the compact agent-facing build contract.appSpec.references.appSpec.planAudit.checks before editing; treat blocked/failed checks as gates, not suggestions.questionsNeeded is true, ask the user before generating.buildable generate "<prompt>" when a runnable template exists. Add --out <dir> only when the user requested a specific folder.appSpec.designSystem for visual tone, density, palette intent, layout rules, component rules, accessibility, and anti-patterns.appSpec.blocks as reusable micro-template guidance. Selected block docs are references to adapt to the current entity/design system, not generic code to paste blindly.appSpec.auth.requested is true, implement the local/mock auth shape first and keep any named provider behind the auth seam.generic-app, use the selected archetype reference to shape screens and entities instead of loading unrelated templates.npx claudepluginhub suntay44/buildable-plugin-skills --plugin buildableGenerates or adapts local-first Expo and React Native prototypes from Buildable app specs, archetypes, UI patterns, and design playbooks.
Builds React/Next.js web frontends: components, pages, design systems, state management, typed API clients. Uses structured phases and engagement modes.
Scaffolds full-stack applications from natural language requests. Selects tech stack, coordinates specialized agents, and applies project templates.