For the complete documentation index, see llms.txt. This page is also available as Markdown.

Buzzy AI

Buzzy AI helps you start from a prompt and get to a working Buzzy app definition quickly. It is best for early product discovery, MVPs, internal tools, workflow apps, and cases where you want Buzzy to infer an initial brief, flows, data model, theme, blueprint, screens, and sample data.

Buzzy AI is not a one-shot substitute for product thinking. Treat the first generated app as a structured starting point that you can inspect, test, refine, and extend.

Start with a Prompt

A good prompt explains:

  • what the app is for

  • who will use it

  • the main records the app needs to store

  • the core workflows users need to complete

  • roles or access boundaries

  • whether the app needs login, approvals, notifications, files, payments, AI, or external integrations

For a full prompt-first workflow, use Buzzy AI Prompt Workflow.

Keep Iterating in Buzzy

After the first version exists, continue from the Workspace:

Workspace area
What to refine

Brief

Product intent, roles, capabilities, and external-function requirements.

Flows

User journeys, approval paths, lifecycle states, and edge cases.

Blueprint

Screen map and navigation.

Design

Screen-level views, forms, fields, actions, widgets, and responsive layout.

Data

Datatables, fields, relationships, permissions, sample data, and Private Data.

Theme

Visual identity, colors, typography, spacing, borders, shadows, and dark/light mode.

Functions and Constants

Server-side logic, secrets, integrations, AI calls, and reusable configuration.

MCP

Builder MCP for app editing, or Custom MCP for exposing app-specific tools.

People and Settings

Users, roles, teams, organizations, app privacy, and authentication posture.

Tests and Security

Repeatable workflow tests and security review before release.

When to Use Another Path

  • Use Buzzy for Figma when visual design fidelity or an existing Figma file is the starting point.

  • Use Buzzy Builder MCP when an AI coding agent should build or change the app in staged, reviewable steps.

  • Use normal no-code Workspace editing when you already know the change and want to edit data, screens, theme, people, settings, functions, tests, or security directly.

Last updated