Use these prompts as a staged workflow when updating a component.
component-update-template-prompt.mdUse for the full implementation workflow: Figma analysis, toolkit work, React parity, tests, Storybook, and documentation.component-validation-qa-template-prompt.mdUse once implementation is mostly done and you want an interactive manual QA pass with exact URLs and step-by-step validation.component-pr-readiness-template-prompt.mdUse after QA passes, or when you want the final repo-wide cleanup, release-doc refresh, commit prep, and branch handoff.
The implementation prompt and the two finish-up prompts ask the agent to work in different modes:
- implementation work should stay focused on design analysis and code changes
- interactive QA should pause after each step and wait for pass/fail feedback
- PR-readiness work should keep moving and clean up repo-wide surfaces without stopping after every check
Keeping them separate makes the workflow easier to follow and reduces prompt ambiguity.