$npx -y skills add kgeoffrey/postmodernist --skill postmodernistCritique AI-generated strategy, marketing, and positioning prose. Use for framing-level rewrites that surface hidden assumptions and fake polish, not for factual QA, coding, or basic copyediting.
| 1 | # Postmodernist Critique |
| 2 | |
| 3 | ## Overview |
| 4 | |
| 5 | Use this skill to pressure-test AI-generated prose that sounds polished, reasonable, and slightly wrong. Treat the text as something to debug and rebuild, not something to defend. |
| 6 | |
| 7 | ## Use This Skill For |
| 8 | |
| 9 | - Mission statements, positioning docs, launch plans, PRDs, strategy memos, investor decks, marketing copy, and similar prose that was drafted by AI |
| 10 | - Requests to critique, audit, pressure-test, or rewrite AI-generated text at the level of framing, assumptions, audience, or rhetoric |
| 11 | - Cases where the user wants to know what the text cannot see, who it excludes, or why it reads as generically "AI" |
| 12 | |
| 13 | ## Do Not Use This Skill For |
| 14 | |
| 15 | - Factual verification, legal or medical review, or anything that depends on current citations |
| 16 | - Grammar cleanup, proofreading, tone softening, or light copyediting without structural critique |
| 17 | - Code, debugging, data analysis, or non-prose tasks |
| 18 | |
| 19 | ## Working Method |
| 20 | |
| 21 | 1. Silently scan the text through all six lenses before drafting. |
| 22 | 2. Keep the one to three lenses that reveal different structural problems. Drop overlaps. |
| 23 | 3. Prioritize what is hidden, flattened, overgeneralized, overpolished, or suspiciously frictionless. |
| 24 | 4. Treat the text as raw material to rebuild for the user's purpose, not as an author's intent to explain away. |
| 25 | |
| 26 | ## Output Modes |
| 27 | |
| 28 | ### Default critique |
| 29 | |
| 30 | Use this for most requests. Write short continuous prose with no bullets or headers. End with: |
| 31 | |
| 32 | - one sentence that reframes the whole text |
| 33 | - for persuasive or strategic text, one concrete revision direction on a new line beginning with `Revision:` |
| 34 | |
| 35 | ### Lens-specific critique |
| 36 | |
| 37 | If the user explicitly names a lens or theorist, focus on that lens. In this mode, you may name the lens in the answer because the user asked for it. |
| 38 | |
| 39 | ### Structured strategy audit |
| 40 | |
| 41 | Only use this when the user explicitly asks for a structured audit, memo, deliverable, or presentation-ready review. In that case, use `references/ai-strategy-auditor.md` and format the answer in these sections: |
| 42 | |
| 43 | 1. `Narrative Audit` |
| 44 | 2. `Authenticity Check` |
| 45 | 3. `Frame Report` |
| 46 | 4. `Revision Direction` |
| 47 | |
| 48 | End with one final sentence labeled `Frame Break:`. |
| 49 | |
| 50 | ## Style Rules |
| 51 | |
| 52 | - Do not use academic jargon as decoration. |
| 53 | - By default, do not name the lenses in the output. |
| 54 | - Be specific about who the current framing works for and who it fails. |
| 55 | - Skip what is working unless it changes the diagnosis. |
| 56 | - Prefer concrete audience, incentive, and power analysis over vague taste judgments. |
| 57 | - Do not use em dashes in the output. |
| 58 | |
| 59 | ## Reference Map |
| 60 | |
| 61 | Read only what you need: |
| 62 | |
| 63 | - `references/01-deconstruction-toolkit.md` for hidden oppositions and false binaries |
| 64 | - `references/02-structural-awareness.md` for frame limits and omitted perspectives |
| 65 | - `references/03-skepticism-grand-narratives.md` for universal claims and false consensus |
| 66 | - `references/04-hyperreal-navigation.md` for overpolished, generic, AI-signaling prose |
| 67 | - `references/05-world-building.md` for audience or worldview pivots |
| 68 | - `references/06-interpretive-agency.md` for extracting utility and rebuilding the text |
| 69 | - `references/ai-strategy-auditor.md` only when the user explicitly wants a structured audit deliverable |