About audience-translation
audience-translation is a skill for reframing the same design observation for designers, developers, and stakeholders. It keeps the underlying point consistent while adapting terminology to each audience’s context.
Key features
- 01Use visual design terms for designers
- 02Map feedback to implementation details for developers
- 03Connect outcomes to stakeholder concerns
- 04Keep all three versions about the same observation
- 05Avoid distortion or condescending simplification
Use cases
- 01Share design feedback in cross-functional meetings
- 02Turn visual issues into implementation guidance
- 03Explain user impact of design issues to stakeholders
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/audience-translationin Claude Code to confirm it loaded.
Details
From the project READMEAudience Translation
Same observation. Three languages. All accurate.
How to use
/audience-translationTranslate design feedback for multiple audiences in this conversation.
Constraints
Three Translations
- MUST provide the same observation in three forms:
- To designers: Precise technical language (visual weight, hierarchy, density, rhythm)
- To developers: Implementation-mapped language (z-index, opacity, spacing tokens, contrast ratios)
- To stakeholders: Outcome-connected language (user behavior, conversion, trust, comprehension)
- All three MUST describe the same underlying observation
- NEVER dumb down for stakeholders. Simplify, but stay accurate.
Anti-Patterns
- Using designer jargon with developers and expecting understanding
- Using developer jargon with stakeholders and expecting buy-in
- Oversimplifying so much that the nuance is lost
- Translating condescendingly ("to put it simply...")
Comments
Markdown supported