Share design and contribute through PRs

Prepare the handoffCopy Anchor Link

1. Summarize the need, audience and proposed decision.
2. Link research, the UX record, prototype, test results and relevant stories.
3. Describe the states, responsive behavior, copy, accessibility and motion that form the expected experience.
4. Declare what is simulated, untested or still open. Separate the design choice from its possible technical implementation.
5. Discuss feasibility and tradeoffs with development. Record agreed changes in the design source.

When to propose a PRCopy Anchor Link

Agree on a precise contribution: token, component, story, copy or UI interaction. Follow repository rules for files, branches and checks relevant to the contribution. Present before/after behavior, the reason and evidence useful to reviewers.

The PR may propose reusable code or a prototype for evaluation. The team decides integration, any rewrite, technical tests and release according to its process.

Close the design cycleCopy Anchor Link

Gather review feedback and available observations about the implemented experience. Update decisions, flows and the design system when a change emerges. Agree with product and development on how to receive subsequent feedback, without introducing a delivery process imposed by the playbook.

Completion criterionCopy Anchor Link

The recipient can try the proposal, understand the evidence, distinguish established parts from experimental ones and identify open questions.

References: version design work, roles and Storybook.