Skip to content
cccskills
FreePublished on GitHub

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.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (1)

  • SKILL.md1.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Notice what's deliberately missing from a design. Restraint is a taste signal. Use when studying minimalist products, evaluating design maturity, or understanding the power of removal.

The English summary is being prepared. Showing the original description.

Dragoon0x/taste-skills6Updated Feb 27, 2026

Palette roles, restraint, semantic consistency, and when fewer colors means better design. Use when building color palettes, evaluating color usage, or diagnosing color-related design problems.

The English summary is being prepared. Showing the original description.

Dragoon0x/taste-skills6Updated Feb 27, 2026

Understand the constraints a design was built under and evaluate quality within that context. Use when reviewing work that had limited time, budget, or team size, or when assessing whether constraints were handled well.

The English summary is being prepared. Showing the original description.

Dragoon0x/taste-skills6Updated Feb 27, 2026

Structured exposure habits for building taste through relentless, intentional consumption. Not passive scrolling. Active intake across design, architecture, film, music, food, and culture. Use when building a taste practice, advising on professional development, or diagnosing why someone's design range feels narrow.

The English summary is being prepared. Showing the original description.

Dragoon0x/taste-skills6Updated Feb 27, 2026

Consistent radii, pixel-perfect alignment, state coverage, and the details that signal design quality. Use when polishing designs, auditing quality, or evaluating whether a design is ready to ship.

The English summary is being prepared. Showing the original description.

Dragoon0x/taste-skills6Updated Feb 27, 2026

Precise language for design feedback. Ban vague words. Name what you actually see. Use when giving design feedback, running critiques, or training teams to communicate about quality.

The English summary is being prepared. Showing the original description.

Dragoon0x/taste-skills6Updated Feb 27, 2026

See all skills by Dragoon0x

Report a problem with this skill