Stats
Actions
Tags
From web-builder
Build a website end-to-end through guided Q&A — dev mode (asks technical preferences like interactivity level, performance priority, language preference; the plugin still picks the framework, but with your input).
How this command is triggered — by the user, by Claude, or both
Slash command
/web-builder:devThe summary Claude sees in its command listing — used to decide when to auto-load this command
You are entering the web-builder flow in **dev mode** — a slightly more technical Q&A. The user can express preferences (e.g., "I care about fast initial load", "I prefer Python on the backend", "let me write the JavaScript myself") and these inform the agent's framework choice. Plain language is still preferred. Use the `Skill` tool to invoke the `web-builder-orchestrator` skill, passing `mode=dev`. Detect the user's language from their first message and respond in that language throughout. Do not output anything to the user before invoking the skill — the skill itself handles all dialog.
You are entering the web-builder flow in dev mode — a slightly more technical Q&A. The user can express preferences (e.g., "I care about fast initial load", "I prefer Python on the backend", "let me write the JavaScript myself") and these inform the agent's framework choice. Plain language is still preferred.
Use the Skill tool to invoke the web-builder-orchestrator skill, passing mode=dev.
Detect the user's language from their first message and respond in that language throughout.
Do not output anything to the user before invoking the skill — the skill itself handles all dialog.
npx claudepluginhub yavuzozguven/web-builder --plugin web-builder/devClassifies a task description into a development type and executes the matching paradigm workflow, reading phase instructions sequentially and enforcing quality gates at boundaries.