Concrete Language Rewriter

When to Use

You have a draft — a pitch, value prop, mission statement, explainer, internal memo, training doc, or product page — containing passages that sound abstract, theoretical, or jargon-heavy. The user wants those passages rewritten into sensory, schema-based language the audience can already picture. Before starting, confirm: (1) which passages are to be rewritten (user-flagged or agent-flagged), (2) who the audience is and what reference points they already share, (3) whether the user wants a one-shot pitch (high-concept), an idea that keeps producing behavior (generative analogy), or fast comprehension (schema tap).

The core mechanic: abstract ideas only stick when they hook onto concrete things already in the reader's memory (the "Velcro theory of memory" from Chapter 3). The more sensory hooks, the better the retention. "White things" is vague; "white things in your refrigerator" is concrete. This skill turns the first into the second.

Context & Input Gathering

Required Context (must have — ask if missing)

• The draft: The actual passage(s) to rewrite, verbatim. -> Check prompt for: pasted text, a file path, or attached document -> If missing, ask: "Paste the passage you want rewritten, or give me the file path."
• The audience: Who will read this and what schemas they already have. -> Check prompt for: role names, job titles, prior experience mentions -> Check environment for: audience-profile.md, brief.md, persona.md -> If still missing, ask: "Who is the audience? What do they already know and see every day that I can anchor this to?"