The conventions to hand your agent so its edits look like the rest of the library.
Discovery gets the right block into the file. Conventions keep it right after
the agent starts editing. Drop the rules below into your project's instruction
file — CLAUDE.md, AGENTS.md, or whatever your tool reads.
"Chakra v3 APIs only" is the highest-value line. Models have seen far more
v2 code than v3, so without it you get <Modal> and extendTheme in an app
that has neither.
"Never name a palette" is what preserves Theme Config. A single
colorPalette="blue" inside a block silently opts that section out of the
user's accent, and it will not be obvious until someone changes the accent.
"Blocks take no props" stops the agent from helpfully refactoring a block into a configurable component with fourteen optional props.
Ask the agent to change the accent after it finishes:
Change the app accent to purple.
If any section stays the old colour, something in it named a palette or hard-coded a value. That single check catches most convention drift.
These rules are also served by the MCP server's get_convention tool, so an
agent connected to it can look them up mid-task instead of relying on what
was in its context at the start.