agentleFS
Dragoon0xDragoon0x/taste-skills/skills/articulation/audience-translation/SKILL.md

audience-translation

Skill5 starsChanged 8 months agoMITView on GitHub

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.

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    MUST provide the same observation in three forms:

    line 17
  2. Distinctive:

    All three MUST describe the same underlying observation

    line 21
  3. Distinctive:

    NEVER dumb down for stakeholders.

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.