Toolkits, Cookbooks & Widgets
Toolkits, cookbooks, and widgets help teams standardise how apps are built.
Toolkits provide reusable UI layouts and structural patterns that Builder MCP and screen-generation workflows can apply to screens, sections, containers, lists, forms, dashboards, headers, footers, navigation, and other interface structures.
Cookbooks provide reusable product, domain, workflow, integration, and governance guidance. They help the brief and downstream artifacts follow approved patterns instead of inventing app-specific conventions every time.
Widgets provide reusable interactive capabilities that can be embedded into screens. Standard/native widgets cover common richer app interactions, while code widgets support custom HTML, React, and Async API behavior when standard Buzzy components are not enough.
Toolkits
Use toolkits when you want app screens to follow a shared design and layout language. Toolkit layouts can shape:
screen shells
overlays
headers, footers, and navigation
list, detail, form, dashboard, and section structures
responsive behavior
component-level patterns
Builder workflows should treat toolkit structure as a contract: adapt content and bindings, but preserve the selected layout's important nesting, classes, slots, and responsive behavior.
Cookbooks
Use cookbooks when you want AI-assisted app creation to reuse proven knowledge. Cookbooks can describe:
app archetypes and domain patterns
workflow and lifecycle guidance
data-model conventions
security and privacy expectations
integration and function patterns
screen and UX guidance
Cookbook guidance is especially important during brief construction. Once accepted, the brief can preserve cookbook-derived assumptions so flows, data, blueprint, theme, and screens stay aligned.
Widgets
Use widgets when a screen needs a richer interaction pattern than standard fields, forms, views, and filters.
Widgets can support:
maps, calendars, galleries, and file managers
charts, dashboards, and visual summaries
booking, availability, and scheduling panels
custom search or filter controls
reusable interaction patterns shared across apps
code widgets that call the Async API, Buzzy Functions, or other approved app services
The widget editor is available at app.buzzy.buzz/editor/widgets. In an AI-assisted build, widgets should still respect the accepted data model, theme, screen context, and security model.
Use Code widget when the widget needs custom HTML/React behavior. Use Buzzy Functions & Constants when the widget needs server-side logic, secrets, provider calls, or privileged processing.
Enterprise Governance
For enterprise teams, toolkits, cookbooks, and widgets are governance assets. They help central teams package approved patterns for brands, departments, regulated workflows, reusable app types, interaction patterns, and delivery standards.
On supported enterprise deployments, administrators can manage toolkit, cookbook, and widget sources so teams can refine, disable, extend, or publish approved patterns without waiting for every app to be handled as a one-off project.
Related Pages
Last updated