v0.6.0

Guidelines for agents move where the people who run the site can edit them.

Highlights

Guidelines live in a global set. php please mcp:guidelines creates a guidelines global set once. Its Site field holds voice and tone, which statamic_overview returns to every agent. Its rows pick collections and taxonomies and say how their entries are put together, and blueprints_get returns the rows naming the requested resource with its blueprints. Admins edit the set in the Control Panel under Globals, with no deploy, and an agent whose user may edit the set can change it through globals_update.

Tab and section instructions reach agents. blueprints_get returns tabs: every tab whose own or whose sections' instructions exist, with the handles of the fields under them. A note about one blueprint, such as which existing entry to follow, goes in its first section, where editors see it too.

A readable block report. mcp:guidelines lists the blocks without instructions grouped under the blueprints that share them, one wrapped line per field, instead of a table wider than any terminal.

The Boost skill maps each kind of guidance to its one place and says never to restate a field in the global set.

Breaking changes

• The markdown files under resources/mcp/guidelines are no longer read, and the guidelines_path config key is gone. The new guidelines key names the set and defaults to guidelines.
• Guidelines for one blueprint or for a global set have no file any more. Put them in a section's instructions.

Migrating from 0.5.0

1. Update the package: composer update danielgnh/statamic-mcp
2. Create the set: php please mcp:guidelines
3. Paste site.md into the set's Site field.
4. Paste each collections/{handle}.md into a row that names its collection. Move anything that describes one field into that field's instructions instead.
5. Delete resources/mcp/guidelines.

Full changelog: v0.5.0...v0.6.0