# 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.

- Skill: `dragoon0x/audience-translation` (Agent Skill)
- Install (CLI): `npx skillmds@latest add dragoon0x/audience-translation`
- Raw SKILL.md: https://api.skillmd.com/api/skills/dragoon0x/audience-translation/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: dragoon0x (https://skillmd.com/u/dragoon0x)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/dragoon0x/audience-translation

---


# 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...")