Request changes safely

Agentful is designed so everyday shop changes flow through durable extension points. The rule is simple: if the change should survive an update, do not change core source files in the running shop.

Change Decision Table

Request	Safe surface	Example tool
Update footer link or copy	Storefront settings	settings.update
Change theme or color mode	Theme settings	settings.list_themes, settings.update
Add or edit products	Product catalog	products.create, products.update
Upload product images	S3 upload workflow	products.create_image_upload
Refund an order	Payment tools	orders.refund
Add a new storefront slot	Plugin manifest	plugins.install, plugin slot
Add a new full page	Plugin page namespace	/plugins/:pluginId/...
Restart or restore the app	Operations plugin	Not in default admin MCP

Prompt Pattern

Use prompts that name the allowed surface:

Use Agentful MCP tools only. Make the Premier Studio footer text link to
https://premierstudio.ai by updating persisted storefront settings.
Do not edit source files, Docker files, or deployment files.

For plugin work:

Build this as an Agentful plugin. Declare every storefront slot, page, API
route, MCP tool, event subscription, and database table in shop-plugin.json.
Do not patch core app files.

Open-Closed Principle

Core remains closed because release images replace it. Agentful stays open through:

• Database-backed settings.
• Theme presets and color mode.
• Product, order, payment, user, and event records.
• Manifest-declared plugins.
• Plugin-owned database tables.
• Plugin-owned storefront pages under /plugins/:pluginId.

If the requested change does not fit one of those surfaces, create a core feature request or plugin proposal instead of asking an agent to patch the running app.