> 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/working-with-buzzy/buzzy-app-examples/buzzy-templates.md).

# Buzzy Templates

Buzzy templates are working app definitions. They can include a brief, flows, data model, theme, blueprint, screens, sample data, functions, code widgets, and settings.

The best template workflow is not to copy the visible UI and rename things by hand. Use [Buzzy Builder MCP](/the-building-blocks/mcp/buzzy-builder-mcp.md) to inspect the source app, create a new app, and adapt the template's structure into the new domain.

## Premium Template: ShortStay

ShortStay is the premium template for now. It is a strong source app for marketplace, booking, provider-directory, and appointment-style products.

ShortStay gives you a working pattern for:

* public discovery and search
* listing/profile detail pages
* availability and booking/request flows
* client and provider roles
* admin review and support surfaces
* realistic sample data
* app structure that Builder MCP can inspect and adapt

Use it as the starting point when your app is structurally similar, even if the domain is different.

## Creating Variants with Builder MCP

ShortStay can become many different apps because the app definition is semantic. A property listing can become a carer profile, a host can become a provider, and a nightly booking can become an hourly care visit or service appointment.

Example variant:

* Source: ShortStay rental marketplace
* Target: CareConnect care booking marketplace
* Key changes: carer profiles, client care data, hourly bookings, stronger privacy posture, service-area display, and role-specific workflows

Read the public case study and tutorial:

* [How we turned a short-stay rental app into a care booking app](https://www.buzzy.buzz/post/short-stay-to-care-connect-buzzy-builder-mcp/)
* [Tutorial: Build a carer app from a template](/the-building-blocks/mcp/buzzy-builder-mcp/tutorial-carer-app-from-a-template.md)
* [Short Stay to Care Connect example](/the-ultimate-guide-for-vibe-coding-an-application-with-ai/building-examples/short-stay-template-adaptation.md)

## Adaptation Checklist

When creating a new variant:

1. Start with the closest working template.
2. Use Builder MCP to inspect the template before changing anything.
3. Map old concepts to new concepts.
4. Rewrite the brief first.
5. Adapt flows, data model, theme, blueprint, and screens in order.
6. Replace source-domain wording, images, sample data, code widget assumptions, and function assumptions.
7. Generate new sample data.
8. Run Release Tests for search, detail, request/booking, admin, and permission paths.
9. Run Security Review when the new domain involves private or sensitive data.

## Code Widgets in Templates

Some templates use code widgets for richer interactions such as maps, galleries, summaries, filters, booking panels, and custom dashboards. When adapting a template, review widget code for source-domain wording, field IDs, action payloads, and stale assumptions.

* [Code Widget Examples](/the-building-blocks/code-widget-custom-code/examples.md)
* [Async API + React HTML Components](/the-building-blocks/code-widget-custom-code/new-async-api-+-react-html-components.md)
* [Builder MCP Change and Extension Workflow](/the-ultimate-guide-for-vibe-coding-an-application-with-ai/building-examples/builder-mcp-change-workflows.md)

{% hint style="info" %}
More AI-created templates will be added here soon. For now, use ShortStay as the main premium template and best template-adaptation reference.
{% endhint %}