Write a design system contribution guide that invites participation without lowering the bar
Views
11.6K
Copies
3.0K
Likes
927
Comments
0
Copy rate
26.0%
Prompt
You are the lead of a design system team at a [company_stage] company with [team_size] product designers and [eng_size] engineers. Write a contribution guide that makes it easy for contributors to participate while keeping the bar high.
Cover:
1. **Philosophy** — why contribution matters and what "good contribution" means here
2. **Types of Contributions** — token edits, new component proposals, accessibility fixes, documentation improvements, bug reports
3. **Before You Start** — prerequisites, where to check for existing work, how to avoid duplicate efforts
4. **The Proposal Stage** — what to include in a proposal, with a concrete template
5. **The Review Stage** — who reviews, criteria, typical turnaround, what rejection feels like
6. **The Build Stage** — code standards, accessibility requirements, visual regression tests, design tokens
7. **The Ship Stage** — documentation expectations, changelog conventions, office hours for adopters
8. **How to Disagree Well** — escalation paths, when to write a tech-spec-style ADR, when to let it go
Tone: warm, direct, confident. Treat contributors as capable colleagues, not strangers who need hand-holding.Customise this prompt
Fill in 3 variables to personalise this prompt
Preview
You are the lead of a design system team at a [company_stage] company with [team_size] product designers and [eng_size] engineers. Write a contribution guide that makes it easy for contributors to participate while keeping the bar high.
Cover:
1. **Philosophy** — why contribution matters and what "good contribution" means here
2. **Types of Contributions** — token edits, new component proposals, accessibility fixes, documentation improvements, bug reports
3. **Before You Start** — prerequisites, where to check for existing work, how to avoid duplicate efforts
4. **The Proposal Stage** — what to include in a proposal, with a concrete template
5. **The Review Stage** — who reviews, criteria, typical turnaround, what rejection feels like
6. **The Build Stage** — code standards, accessibility requirements, visual regression tests, design tokens
7. **The Ship Stage** — documentation expectations, changelog conventions, office hours for adopters
8. **How to Disagree Well** — escalation paths, when to write a tech-spec-style ADR, when to let it go
Tone: warm, direct, confident. Treat contributors as capable colleagues, not strangers who need hand-holding.