Audience translation

Skill Dragoon0x/taste-skills/skills/articulation/audience-translation

Explain the same design observation to a designer, a developer, and a non-technical stakeholder. Same insight, three languages. Use when working cross-functionally or presenting design decisions to mixed audiences.From its SKILL.md

Install

npx -y skills add Dragoon0x/taste-skills --skill audience-translation

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.2 KB, 194 tokens by cl100k_base, as published. Nobody here has run it

Audience Translation

Same observation. Three languages. All accurate.

How to use

/audience-translation Translate 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...")

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.