> 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/advanced-deployment-settings/installation/toolkits-and-cookbooks.md).

# Enterprise Toolkits & Cookbooks

Enterprise teams can use toolkits and cookbooks to govern how AI-assisted Buzzy apps are created and maintained across a deployment.

Toolkits package approved UI layouts and screen structures. Cookbooks package reusable product, workflow, domain, integration, and governance knowledge. Together they help teams move quickly while keeping app output aligned with organisation standards.

## Why Manage Them Centrally

* Keep apps aligned to approved design systems and interaction patterns.
* Reuse validated app patterns across teams and departments.
* Capture domain knowledge once instead of rediscovering it in each prompt.
* Reduce app-by-app drift in security, privacy, workflow, and UX decisions.
* Give Builder MCP and Buzzy AI better source material for brief, blueprint, and screen generation.

## Toolkit Administration

Toolkit administration is used to inspect, preview, extend, disable, export, and sync reusable layout assets.

Supported enterprise workflows can include:

* reviewing source toolkit layouts
* creating database-backed toolkit additions
* editing toolkit layout JSON for approved additions
* copying source layouts into editable additions
* disabling layouts that should not be used by AI or builders
* exporting layouts for review or migration
* regenerating toolkit indexes used by search and allocation

Treat toolkit changes as shared platform changes. Test representative apps after changing layouts that are used broadly.

## Cookbook Administration

Cookbook administration is used to manage reusable app-building guidance.

Supported enterprise workflows can include:

* maintaining app archetypes and domain playbooks
* updating workflow, data, screen, integration, and governance guidance
* enabling or disabling cookbook sources
* syncing cookbook indexes used by Builder MCP and Buzzy AI
* reviewing which cookbooks influenced a generated brief

Cookbooks should be written as reusable guidance, not one-off instructions for a single app. If guidance belongs only to one app, keep it in that app's brief or project notes.

## Release Discipline

Changes to enterprise toolkits and cookbooks can affect future app generation. Use a controlled change process:

1. Draft the change.
2. Review it with the owning product, design, security, or platform team.
3. Test it on representative app builds or screen-generation cases.
4. Sync the relevant indexes.
5. Communicate the change to builder teams.

## Related Pages

* [Toolkits & Cookbooks](/the-building-blocks/toolkits-and-cookbooks.md)
* [Buzzy Builder MCP](/the-building-blocks/mcp/buzzy-builder-mcp.md)
* [Release Management](/advanced-deployment-settings/installation/release-management.md)