> For the complete documentation index, see [llms.txt](https://docs.buzzy.buzz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buzzy.buzz/getting-started-with-buzzy/new-buzzy-ai-v3/1.-writing-a-prompt.md).

# 1. Writing a Prompt

<figure><img src="https://1771273900-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3HPEoFCyP7Q88dV3CmqD%2Fuploads%2FU61TFJTHAsoqmd4rSQgc%2FScreenshot%202025-09-24%20at%2011.34.23.png?alt=media&amp;token=e6899f72-17b4-4fc6-8000-3c8a486ddc5a" alt=""><figcaption></figcaption></figure>

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](/the-building-blocks/mcp/buzzy-builder-mcp.md): 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

{% hint style="info" %}
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.
{% endhint %}