# Example contribution checklist

This is an illustrative template. Adapt it to the team and product.

- [ ] Describe the user need and evidence of repeated use.
- [ ] Check existing components and document why they cannot meet the need.
- [ ] Agree the owner, anatomy, label, variants, states and semantic tokens.
- [ ] Review design and code together with a product-team representative.
- [ ] Verify keyboard interaction, focus visibility, contrast and announcements.
- [ ] Check narrow screens, long labels and each supported theme.
- [ ] Publish usage guidance, executable examples and known limitations.
- [ ] Include a changelog, compatibility notes and migration steps.
- [ ] Name a pilot product and collect feedback before broader adoption.