What to Use When
Buzzy has multiple creation paths because builders start from different places. Use this guide to pick the right workflow before you spend time prompting, designing, or adapting an app.
Quick Decision Table
Builder MCP from a template
Fastest reliable path for common app patterns
A template is structurally close to your idea
You need a completely novel data model or interaction pattern
Builder MCP from scratch
Serious custom apps
You want staged review of brief, flows, data, screens, and runtime behavior
You only need a quick throwaway prototype
Builder MCP for an existing app
Focused changes and refinements
You already have an app and want an agent to inspect, plan, edit, and verify
You have not identified the target app or change
Builder MCP from an external app/codebase
Migration or rebuild projects
You have a Lovable app, legacy app, screenshots, or codebase to use as reference
You expect source code to be copied directly into Buzzy unchanged
Builder MCP from a Figma file
Agent-assisted builds using a design reference
You want Buzzy structure plus design direction from Figma
You need to keep editing the live app entirely through Figma
Buzzy AI prompt workflow
Quick prompt-first app generation
You want to generate or edit directly in the Buzzy workspace
You need careful staged artifact review or external-agent testing
Buzzy Figma plugin
Figma-native no-code design
You want to design, mark up, and publish from Figma
You are starting from a Buzzy AI app that is not editable in Figma
Recommended Defaults
Use Builder MCP from a template when a template is close enough. It gives you a proven starting structure and lets the agent focus on adapting the app to your domain.
Use Builder MCP from scratch when your app has custom workflows, sensitive data, complex permissions, or a data model that needs careful review.
Use Buzzy AI prompt workflow when speed matters more than staged review. It is a good way to explore an idea quickly inside the Buzzy workspace.
Use Buzzy Figma plugin when your primary workflow is visual design in Figma and you want to keep working there.
Good Builder Habits
Plan first: describe the app, roles, data, and core workflow before asking for screens.
Build in layers: brief, flows, data model, theme, blueprint, screens, sample data, verification.
Keep review gates small enough to inspect.
Use templates and reference apps for proven structure.
Use Playwright, screenshots, or browser inspection for important runtime paths.
Verify permissions and sensitive data with both allowed and denied users where relevant.
Last updated