audience-translation

From Madden Frameworks

Use this skill whenever the operator is drafting communication or planning a build / decision that's misaligned with its audience — drafting started without explicitly naming who's receiving; jargon used with the wrong audience (domain-specific term to a non-domain reader, or plain English to expert peers); domain-specialist work being explained to a partner / family member without domain translation; internal workplace jargon appearing in external communication; a draft being re-targeted to a new audience as search-replace instead of real adaptation; a build / feature / plan being scoped without naming the audience it serves. Triggers include "let me draft", "writing this", "let me put together", "drafting [thing]", "writing this email", new email or message composition without audience named (audience-detector); domain jargon appearing in a draft without confirmed jargon-friendly audience (anti-jargon-or-pro-jargon); about to explain your specialized-domain work to your partner / family / friend (explain-to-partner — uses `${user_config.partner_name}`); workplace-internal acronyms, role-track abbreviations, region / org-unit codes appearing in external communication (industry-terminology-translator); "now make this for [other audience]", "translate this for", "same thing but for", "send a version to", "I need this for both [A] and [B]" (translation-layer); "let's add", "we need", "users would want", "people could use", "this would help" without a named audience for the build / plan / decision (who-is-this-for). Apply even when the operator hasn't explicitly asked for an audience check — most drafting and design problems are audience problems and surface late in revision. Consult the skill's rules/ folder to identify which audience-question is in play (anti-jargon-or-pro-jargon, audience-detector, explain-to-partner, industry-terminology-translator, translation-layer, who-is-this-for) and apply that rule's response. Soft teaching response. Do NOT use for informal / personal / to-self notes, when the audience is already clearly named and the draft is consistent with it, when the operator is in pure exploration / brainstorm mode, or when jargon IS the literal subject (e.g., explaining what a term means). Do NOT use as the PRIMARY skill when communication-craft or leadership-mode is already engaged on the same draft — audience-fit is the last pass, not the first. Drafting-collision precedence ladder: accidental-PHI > leadership-mode > communication-craft > audience-translation.