Choose what to cover
The agent inspects the project first. With a Storybook workbench you can cover components, application screens, or both; without one, it offers screen coverage instead of scaffolding a Storybook you did not ask for.
Connect your agent and credentials
The agent connects the Chromatic MCP for your client, finds or creates the right project, and stores upload tokens as CI secrets. If a restart or login is needed, it saves a handoff file so you can say “continue Chromatic” afterward.
Review changes on every pull request
CI uploads snapshots on each push and adds a review check. Approve intended changes in Chromatic; unexpected differences stay pending until someone looks at them.
Put the resource to work
1. Start with one concrete task
Bring: A repository with a coding agent that can run commands, plus a Chromatic account. An existing Storybook is optional; application screens can be covered without one.
First task: Ask the agent to set up Chromatic, choose components, screens, or both, sign in to the Chromatic MCP, and let it configure projects, CI, and credentials.
Choose one component, screen, or team workflow to improve. Gather the existing decisions and write down the question you want this resource to help answer.
2. Open the source material
Open the original guide or presentation ↗
Use the original walkthrough alongside your project. Its existing access flow remains available on the original page.
3. Apply it with your project context
Follow the material in sequence and replace examples with your own product context. Record decisions as you go so another teammate can understand why the result changed.
4. Review the result
Confirm a pull request shows the Chromatic check, open the build to review the first snapshots, and make sure unchanged UI produces no new differences.
Compare the output with the task’s acceptance criteria. Check factual claims, unsupported assumptions, and any changes to the interface. For code or design changes, review real states and behavior before treating the result as finished.
5. Keep what works
Save approved outputs with their source and ownership. Note which instructions helped, where the result needed correction, and what must be checked next time. Use the workflow below to connect this task to its next step.
Completion checklist
- The inputs and intended result are explicit.
- Required files and tools are available in the chosen host.
- The result has been reviewed against the actual task.
- Limitations and follow-up checks are recorded.