1. Writing a Prompt

Start by describing what you want to build in plain language. Prompts can range from a short description to a detailed breakdown of features, roles, data, flows, or screens.

Prompt-first creation is best for quick starts and focused edits. For larger apps, use the same planning discipline you would use with Builder MCP: define the brief, flows, data model, screen intent, and review checkpoints before asking Buzzy to build too much at once.

Example prompts:

• "A to-do list app with projects and due dates."

• "A mobile-first CRM dashboard for tracking customer interactions and sales pipelines."

Prompts can be entered:

• From the Workspace home screen (to start a new app)

• From the Design > AI section (to update an existing screen or app)

What to Include

• what the app is for

• who uses it

• the core data objects and relationships

• the main user journeys

• permissions or private data rules

• the most important screens

• integrations, functions, or external APIs

• what should be left out of the first version

For complex apps, avoid one giant prompt that tries to finish everything. Start with the app shape, review what Buzzy creates, then iterate through data, screens, debugging, testing, and deployment.