Agents / Claude
Two skills that stop AI slop in your decks
Drop one file into Claude, ChatGPT, or Gemini. Answer the interview. Get an agent and its skills.
Summary
An AI agent is a system of instruction files, called markdown files. This guide shows how one file interviews you and then builds your first agent and its skills.
Before you start
Why it matters
The biggest problem with AI when you build a deck: even when you give it great references, the deck still looks like AI slop.
You have seen the design signs: Purple gradients. Rounded corners. Eyebrow stripes.
And you've seen the writing signs: Em-dashes. Information grouped in threes.
This matters. You can have the best strategy or narrative, but if your deck looks like AI slop, no one will take it seriously.
After cringing at too many decks made internally and even by clients, I tested AI skills in the depths of social media and GitHub to find a solution.
These two files made the biggest impact in the writing and design of decks.
Skill 1: The anti-AI writing file
I made a file with 160 rules and examples to avoid sounding like AI.
This matters more now because of AI watermarking.
Use it for the words on every slide. It targets writing patterns, such as em-dashes and grouping information in threes.
Copy the prompt or download the markdown file.
Copy prompt
# Anti-AI Writing Style This is the list to ban AI writing in writing drafts. There are two kinds of signs of AI writing: words and phrases, and sentence patterns. Start with the words below. Then go pattern by pattern. --- ## Part 1: The Patterns These are structural habits that you will ban from writing. ### 1. Stacked Negation Fragments **Looks like:** "Not productively. Not to work on something else. You just stop directing the mind and let it be unoccupied." **The tell:** A row of short "Not X" sentences that rule things out before landing on a conclusion. Denial, denial, reveal. It sounds thoughtful, but it's defining something by what it isn't instead of just saying what it is. **Fix:** Say the thing directly. Cut the run-up. ### 2. Abstract Noun-Phrase Triplets **Looks like:** "A pull toward something you can't immediately explain. A thread that keeps returning. An interest that surfaces without invitation." **The tell:** Three vague nouns in a row (pull, thread, interest, signal, hunger), each one given its own little verb as if it has a will of its own. Sounds oracular. Says nothing concrete. **Fix:** Pick one concrete noun and one concrete verb. Cut the other two. ### 3. The Reframe Negation **Looks like:** "He wasn't describing genius. He was describing something available to anyone." **The tell:** One negation, one correction, structured like you'd guessed wrong and now get the real answer. Usually the reader never guessed wrong — the writer just needed a setup. **Fix:** Skip the setup. State the real point first. ### 4. The "Real X" Redefinition **Looks like:** "Preparation is the part we think we're doing. But real preparation is more specific than that." **The tell:** Takes a familiar word, concedes the obvious version, claims a deeper one — and the deeper one is almost always just as vague. It performs precision without supplying any. **Fix:** If you can't define the "real" version in concrete terms, you don't have one yet. Find the concrete version or cut the sentence. ### 5. The Reframed Discomfort **Looks like:** "The discomfort of following the pull isn't a sign you're going wrong — it's the becoming." **The tell:** A bad feeling gets relabeled as proof you're on the right track. The em-dash before the payoff does the heavy lifting a real argument should be doing. **Fix:** If the feeling is evidence of something, show the evidence. Otherwise don't claim it. ### 6. The Ventriloquized Simile **Looks like:** "He talks about it the way people talk about a country they've always meant to visit. Eventually. When things settle down. When he knows it'll be worth it." **The tell:** A comparison sets up, then the prose starts performing the voice of whatever it just compared the subject to — usually in trailing one-word fragments ("Eventually." "When."). **Fix:** Cut the comparison and the fragments. Describe the actual behavior. ### 7. The Announced Noticing **Looks like:** "What I've started to notice is what lives in that distance." **The tell:** The writer announces the act of noticing instead of just stating what was noticed. The frame draws attention to the observer, not the observation — which has to do all the work the frame implied it already did. **Fix:** Delete the announcement. Say what you noticed. ### 8. The Colon Drumroll **Looks like:** "Not fear exactly. Something more specific: the demand for a destination before you'll agree to move." **The tell:** A teaser phrase ("something more specific") followed by a colon that theatrically delivers the point. If the point is strong, it doesn't need a drumroll. **Fix:** Cut the teaser. Let the sentence after the colon stand alone. ### 9. The Em-Dash Correction **Looks like:** "...projects people did for fun — not because the fun motivated them harder, but because genuine curiosity tends to point toward what actually needs to exist." **The tell:** An em-dash introduces a "not because X, but because Y" correction mid-sentence, as if catching the reader's assumption in real time. One of these is fine. Several in a paragraph reads like a writer who won't let a claim land without hedging it. **Fix:** Pick the real reason. State it. Skip the fake one you're "correcting." ### 10. Definition by Foil **Looks like:** "Passion implies arrival — you already know what you love, you already feel the fire. Curiosity is earlier and quieter." **The tell:** A concept gets defined only by contrast with a different concept that was never actually the subject. Delete the foil and the definition collapses, because the subject was never described on its own terms. **Fix:** Describe the actual subject directly. If the definition needs the foil to survive, it isn't a definition yet. ### 11. The Atrophy Consequence **Looks like:** "It doesn't make a case for itself. It just returns. And if you keep dismissing it, you eventually stop hearing it — and you wonder why nothing you're doing feels like it's building toward anything real." **The tell:** Quiet declaratives build up, then pivot into a vague warning about what you'll lose if you don't listen. "You wonder why" is the signature move — it implies future confusion you caused yourself. Reads like observation, functions like a guilt trip. **Fix:** If there's a real cost, name it specifically. If you can't name it, cut the warning. ### 12. The Taxonomy Refusal **Looks like:** "It didn't fit a category. It wasn't networking. It wasn't building toward anything I could name." **The tell:** A string of "It wasn't X / it wasn't Y" sentences that deny categories without ever saying what the thing actually was. Implies the thing was too real to name. Usually it just avoids the work of naming it. **Fix:** Name it. If you genuinely can't, that's a sign the sentence needs more reporting, not more negation. ### 13. The Declared Crux **Looks like:** "This is the thing about curiosity that makes it hard to trust: it doesn't argue for itself. It just returns." **The tell:** The writer announces they've found the essential point before delivering it. The announcement performs intimacy and insight it hasn't earned yet. Test: if the line after the colon stands on its own, the setup was throat-clearing. **Fix:** Cut the announcement. Lead with the line that was going to follow it. ### 14. The Two-Fragment Contrast **Looks like:** "Not as failure. As structure." / "What you find there is not comfort. It's contact." **The tell:** Two short sentences — negate or relabel, then land the "real" version — with no connective tissue between them. The white space is doing the work argument should be doing. **Fix:** If either fragment were a full sentence, the trick would stop working. That's the tell. Write the full sentence instead. ### 15. The Abstracted Effect Clause **Looks like:** "...generous with his time in a way that makes the April sentence easy to forget." **The tell:** Instead of showing a trait in action, the sentence describes the trait's effect in an explanatory tail. It tells you the impact without ever showing the thing that caused it. **Fix:** Show the specific moment. Cut the clause that explains its effect instead. --- ## Part 2: The Words and Phrases Faster to catch than the patterns above, and worth removing immediately. ### Banned vocabulary If one of these shows up, replace it with something plainer and more specific: delve, realm, harness, unlock, tapestry, paradigm, cutting-edge, revolutionize, intricate, intricacies, showcasing, crucial, pivotal, surpass, meticulously, vibrant, unparalleled, underscore, leverage, synergy, innovative, game-changer, testament, commendable, meticulous, highlight, emphasize, boast, groundbreaking, align, foster, showcase, enhance, holistic, garner, accentuate, pioneering, trailblazing, unleash, versatile, transformative, redefine, seamless, optimize, scalable, robust, breakthrough, empower, streamline, frictionless, elevate, adaptive, effortless, data-driven, insightful, proactive, mission-critical, visionary, disruptive, reimagine, unprecedented, intuitive, leading-edge, synergize, democratize, accelerate, state-of-the-art, dynamic, immersive, predictive, transparent, proprietary, integrated, plug-and-play, turnkey, future-proof, paradigm-shifting, supercharge, enduring, interplay, valuable, captivate. ### The negative-parallelism trap: "it's not X, it's Y" This is the single most common AI tell. **Banned shapes:** - "It's not just X, it's Y" - "Not X. Y." - "This isn't about X, it's about Y" - "X isn't just Y, it's Z" - "More than X, it's Y" - "Isn't just X. It's Y." **Sneakier versions that still count:** - "Rather than simply X, it Y's" - "While some might see this as X, it's actually Y" - "What looks like X is actually Y" **Why it's banned:** The sentence sounds like it's saying something precise, but X and Y are usually near-synonyms, so nothing was actually clarified. Rhetorical-question versions ("Is this just X? No — it's Y") and whole paragraph or section headings built on this shape (a sub-head that negates, then a body that affirms) are banned for the same reason. **The fix:** Delete the negated half entirely. State the real claim once. The only exception is a genuine factual correction — when readers really did believe X and X is really false (e.g., "This isn't a tax. It's a fee set by the county, not the state.") — not a rhetorical setup invented to sound insightful. ### Banned phrase shapes (weak verb dodges) Replace these with a plain, direct verb: | Instead of | Use | |---|---| | serves as / stands as / marks a / represents a / boasts a / features a / offers a | is, has | | plays a role in | causes, changes, affects | | helps to / aims to / seeks to | [just use the plain verb — "helps to improve" → "improves"] | ### Dead openings, transitions, and bait Cut these on sight — they signal filler, not content: - **Openings:** "In today's fast-paced world," "In the ever-evolving landscape of," "As we navigate," "In an era where," "It's no secret that," "Picture this:," "Let's face it," - **Transitions:** "That said," "With that in mind," "At the end of the day," "When all is said and done," "Needless to say," "It goes without saying," - **Bait:** "You won't believe what happened next," "Here's the kicker," "But here's the thing," "And that's just the beginning" ### Analogy and metaphor Default to none. Most AI writing reaches for a comparison instead of doing the work of being specific. Before using one, it should pass all of these: 1. It clarifies something genuinely hard to picture otherwise. 2. It's not a cliché (not "like a rollercoaster," "like a puzzle," "like a journey"). 3. It doesn't need its own explanation to land. 4. It isn't doing the job a plain, concrete sentence could do instead. **Banned setups:** "Think of it like," "It's a bit like," "Imagine if," "In many ways, it's similar to" **Banned metaphor families:** journeys, puzzles, gardens, muscles that need exercising, light/darkness, building blocks, roller coasters, chess games **Banned metaphor verbs (use the literal verb instead):** "unlocks" → opens, enables; "unleashes" → starts, allows; "fuels" → drives, powers; "ignites" → starts, causes; "weaves together" → combines, connects; "paints a picture" → shows, describes. ### Other AI tells to catch - **Puffery:** Calling something "important," "powerful," or "significant" without showing why. Show the effect instead of naming the adjective. - **Rule of three:** Reflexively grouping examples, items, or qualities in sets of three. Use however many there actually are. - **False ranges:** "From A to B" used to sound comprehensive when only A and B were ever discussed. Only use it if there's a real range of things in between. - **Elegant variation:** Swapping in a synonym purely to avoid repeating a word ("the firm," "the organization," "the company" all referring to the same business in three sentences). Repeating the word is fine and clearer. - **Meta-commentary:** Describing what the writing is doing instead of just doing it ("It's important to note that," "This highlights the fact that"). - **Fake-depth participles:** Tacking on a vague participial phrase to sound more insightful than the sentence earns ("...reflecting a broader shift," "...underscoring the complexity"). - **Cutoff disclaimers:** "While a full analysis is beyond the scope of this piece," used to dodge actually answering. - **Metronome rhythm:**
# Anti-AI Writing Style This is the list to ban AI writing in writing drafts. There are two kinds of signs of AI writing: words and phrases, and sentence patterns. Start with the words below. Then go pattern by pattern. --- ## Part 1: The Patterns These are structural habits that you will ban from writing. ### 1. Stacked Negation Fragments **Looks like:** "Not productively. Not to work on something else. You just stop directing the mind and let it be unoccupied." **The tell:** A row of short "Not X" sentences that rule things out before landing on a conclusion. Denial, denial, reveal. It sounds thoughtful, but it's defining something by what it isn't instead of just saying what it is. **Fix:** Say the thing directly. Cut the run-up. ### 2. Abstract Noun-Phrase Triplets **Looks like:** "A pull toward something you can't immediately explain. A thread that keeps returning. An interest that surfaces without invitation." **The tell:** Three vague nouns in a row (pull, thread, interest, signal, hunger), each one given its own little verb as if it has a will of its own. Sounds oracular. Says nothing concrete. **Fix:** Pick one concrete noun and one concrete verb. Cut the other two. ### 3. The Reframe Negation **Looks like:** "He wasn't describing genius. He was describing something available to anyone." **The tell:** One negation, one correction, structured like you'd guessed wrong and now get the real answer. Usually the reader never guessed wrong — the writer just needed a setup. **Fix:** Skip the setup. State the real point first. ### 4. The "Real X" Redefinition **Looks like:** "Preparation is the part we think we're doing. But real preparation is more specific than that." **The tell:** Takes a familiar word, concedes the obvious version, claims a deeper one — and the deeper one is almost always just as vague. It performs precision without supplying any. **Fix:** If you can't define the "real" version in concrete terms, you don't have one yet. Find the concrete version or cut the sentence. ### 5. The Reframed Discomfort **Looks like:** "The discomfort of following the pull isn't a sign you're going wrong — it's the becoming." **The tell:** A bad feeling gets relabeled as proof you're on the right track. The em-dash before the payoff does the heavy lifting a real argument should be doing. **Fix:** If the feeling is evidence of something, show the evidence. Otherwise don't claim it. ### 6. The Ventriloquized Simile **Looks like:** "He talks about it the way people talk about a country they've always meant to visit. Eventually. When things settle down. When he knows it'll be worth it." **The tell:** A comparison sets up, then the prose starts performing the voice of whatever it just compared the subject to — usually in trailing one-word fragments ("Eventually." "When."). **Fix:** Cut the comparison and the fragments. Describe the actual behavior. ### 7. The Announced Noticing **Looks like:** "What I've started to notice is what lives in that distance." **The tell:** The writer announces the act of noticing instead of just stating what was noticed. The frame draws attention to the observer, not the observation — which has to do all the work the frame implied it already did. **Fix:** Delete the announcement. Say what you noticed. ### 8. The Colon Drumroll **Looks like:** "Not fear exactly. Something more specific: the demand for a destination before you'll agree to move." **The tell:** A teaser phrase ("something more specific") followed by a colon that theatrically delivers the point. If the point is strong, it doesn't need a drumroll. **Fix:** Cut the teaser. Let the sentence after the colon stand alone. ### 9. The Em-Dash Correction **Looks like:** "...projects people did for fun — not because the fun motivated them harder, but because genuine curiosity tends to point toward what actually needs to exist." **The tell:** An em-dash introduces a "not because X, but because Y" correction mid-sentence, as if catching the reader's assumption in real time. One of these is fine. Several in a paragraph reads like a writer who won't let a claim land without hedging it. **Fix:** Pick the real reason. State it. Skip the fake one you're "correcting." ### 10. Definition by Foil **Looks like:** "Passion implies arrival — you already know what you love, you already feel the fire. Curiosity is earlier and quieter." **The tell:** A concept gets defined only by contrast with a different concept that was never actually the subject. Delete the foil and the definition collapses, because the subject was never described on its own terms. **Fix:** Describe the actual subject directly. If the definition needs the foil to survive, it isn't a definition yet. ### 11. The Atrophy Consequence **Looks like:** "It doesn't make a case for itself. It just returns. And if you keep dismissing it, you eventually stop hearing it — and you wonder why nothing you're doing feels like it's building toward anything real." **The tell:** Quiet declaratives build up, then pivot into a vague warning about what you'll lose if you don't listen. "You wonder why" is the signature move — it implies future confusion you caused yourself. Reads like observation, functions like a guilt trip. **Fix:** If there's a real cost, name it specifically. If you can't name it, cut the warning. ### 12. The Taxonomy Refusal **Looks like:** "It didn't fit a category. It wasn't networking. It wasn't building toward anything I could name." **The tell:** A string of "It wasn't X / it wasn't Y" sentences that deny categories without ever saying what the thing actually was. Implies the thing was too real to name. Usually it just avoids the work of naming it. **Fix:** Name it. If you genuinely can't, that's a sign the sentence needs more reporting, not more negation. ### 13. The Declared Crux **Looks like:** "This is the thing about curiosity that makes it hard to trust: it doesn't argue for itself. It just returns." **The tell:** The writer announces they've found the essential point before delivering it. The announcement performs intimacy and insight it hasn't earned yet. Test: if the line after the colon stands on its own, the setup was throat-clearing. **Fix:** Cut the announcement. Lead with the line that was going to follow it. ### 14. The Two-Fragment Contrast **Looks like:** "Not as failure. As structure." / "What you find there is not comfort. It's contact." **The tell:** Two short sentences — negate or relabel, then land the "real" version — with no connective tissue between them. The white space is doing the work argument should be doing. **Fix:** If either fragment were a full sentence, the trick would stop working. That's the tell. Write the full sentence instead. ### 15. The Abstracted Effect Clause **Looks like:** "...generous with his time in a way that makes the April sentence easy to forget." **The tell:** Instead of showing a trait in action, the sentence describes the trait's effect in an explanatory tail. It tells you the impact without ever showing the thing that caused it. **Fix:** Show the specific moment. Cut the clause that explains its effect instead. --- ## Part 2: The Words and Phrases Faster to catch than the patterns above, and worth removing immediately. ### Banned vocabulary If one of these shows up, replace it with something plainer and more specific: delve, realm, harness, unlock, tapestry, paradigm, cutting-edge, revolutionize, intricate, intricacies, showcasing, crucial, pivotal, surpass, meticulously, vibrant, unparalleled, underscore, leverage, synergy, innovative, game-changer, testament, commendable, meticulous, highlight, emphasize, boast, groundbreaking, align, foster, showcase, enhance, holistic, garner, accentuate, pioneering, trailblazing, unleash, versatile, transformative, redefine, seamless, optimize, scalable, robust, breakthrough, empower, streamline, frictionless, elevate, adaptive, effortless, data-driven, insightful, proactive, mission-critical, visionary, disruptive, reimagine, unprecedented, intuitive, leading-edge, synergize, democratize, accelerate, state-of-the-art, dynamic, immersive, predictive, transparent, proprietary, integrated, plug-and-play, turnkey, future-proof, paradigm-shifting, supercharge, enduring, interplay, valuable, captivate. ### The negative-parallelism trap: "it's not X, it's Y" This is the single most common AI tell. **Banned shapes:** - "It's not just X, it's Y" - "Not X. Y." - "This isn't about X, it's about Y" - "X isn't just Y, it's Z" - "More than X, it's Y" - "Isn't just X. It's Y." **Sneakier versions that still count:** - "Rather than simply X, it Y's" - "While some might see this as X, it's actually Y" - "What looks like X is actually Y" **Why it's banned:** The sentence sounds like it's saying something precise, but X and Y are usually near-synonyms, so nothing was actually clarified. Rhetorical-question versions ("Is this just X? No — it's Y") and whole paragraph or section headings built on this shape (a sub-head that negates, then a body that affirms) are banned for the same reason. **The fix:** Delete the negated half entirely. State the real claim once. The only exception is a genuine factual correction — when readers really did believe X and X is really false (e.g., "This isn't a tax. It's a fee set by the county, not the state.") — not a rhetorical setup invented to sound insightful. ### Banned phrase shapes (weak verb dodges) Replace these with a plain, direct verb: | Instead of | Use | |---|---| | serves as / stands as / marks a / represents a / boasts a / features a / offers a | is, has | | plays a role in | causes, changes, affects | | helps to / aims to / seeks to | [just use the plain verb — "helps to improve" → "improves"] | ### Dead openings, transitions, and bait Cut these on sight — they signal filler, not content: - **Openings:** "In today's fast-paced world," "In the ever-evolving landscape of," "As we navigate," "In an era where," "It's no secret that," "Picture this:," "Let's face it," - **Transitions:** "That said," "With that in mind," "At the end of the day," "When all is said and done," "Needless to say," "It goes without saying," - **Bait:** "You won't believe what happened next," "Here's the kicker," "But here's the thing," "And that's just the beginning" ### Analogy and metaphor Default to none. Most AI writing reaches for a comparison instead of doing the work of being specific. Before using one, it should pass all of these: 1. It clarifies something genuinely hard to picture otherwise. 2. It's not a cliché (not "like a rollercoaster," "like a puzzle," "like a journey"). 3. It doesn't need its own explanation to land. 4. It isn't doing the job a plain, concrete sentence could do instead. **Banned setups:** "Think of it like," "It's a bit like," "Imagine if," "In many ways, it's similar to" **Banned metaphor families:** journeys, puzzles, gardens, muscles that need exercising, light/darkness, building blocks, roller coasters, chess games **Banned metaphor verbs (use the literal verb instead):** "unlocks" → opens, enables; "unleashes" → starts, allows; "fuels" → drives, powers; "ignites" → starts, causes; "weaves together" → combines, connects; "paints a picture" → shows, describes. ### Other AI tells to catch - **Puffery:** Calling something "important," "powerful," or "significant" without showing why. Show the effect instead of naming the adjective. - **Rule of three:** Reflexively grouping examples, items, or qualities in sets of three. Use however many there actually are. - **False ranges:** "From A to B" used to sound comprehensive when only A and B were ever discussed. Only use it if there's a real range of things in between. - **Elegant variation:** Swapping in a synonym purely to avoid repeating a word ("the firm," "the organization," "the company" all referring to the same business in three sentences). Repeating the word is fine and clearer. - **Meta-commentary:** Describing what the writing is doing instead of just doing it ("It's important to note that," "This highlights the fact that"). - **Fake-depth participles:** Tacking on a vague participial phrase to sound more insightful than the sentence earns ("...reflecting a broader shift," "...underscoring the complexity"). - **Cutoff disclaimers:** "While a full analysis is beyond the scope of this piece," used to dodge actually answering. - **Metronome rhythm:** Every sentence the same length and shape, back to back. Vary it — short next to long, simple next to complex. ### Formatting - Short paragraphs. Break up anything over 4-5 lines. - Use digits for numbers, not words ("5 signs," not "five signs"). - No em-dashes ever. Use a period, comma, colon, semicolon, or parentheses instead. - Bold sparingly, if everything's bold, nothing is. - Sentence case for headers, not title case. --- ## The short version If you only remember one thing: say the real thing, directly, with a number or a name attached whenever you can. Everything above is a version of writing that dresses up vagueness to sound like insight. Specificity is the fix for all of it.
Copy prompt
# Anti-AI Writing Style This is the list to ban AI writing in writing drafts. There are two kinds of signs of AI writing: words and phrases, and sentence patterns. Start with the words below. Then go pattern by pattern. --- ## Part 1: The Patterns These are structural habits that you will ban from writing. ### 1. Stacked Negation Fragments **Looks like:** "Not productively. Not to work on something else. You just stop directing the mind and let it be unoccupied." **The tell:** A row of short "Not X" sentences that rule things out before landing on a conclusion. Denial, denial, reveal. It sounds thoughtful, but it's defining something by what it isn't instead of just saying what it is. **Fix:** Say the thing directly. Cut the run-up. ### 2. Abstract Noun-Phrase Triplets **Looks like:** "A pull toward something you can't immediately explain. A thread that keeps returning. An interest that surfaces without invitation." **The tell:** Three vague nouns in a row (pull, thread, interest, signal, hunger), each one given its own little verb as if it has a will of its own. Sounds oracular. Says nothing concrete. **Fix:** Pick one concrete noun and one concrete verb. Cut the other two. ### 3. The Reframe Negation **Looks like:** "He wasn't describing genius. He was describing something available to anyone." **The tell:** One negation, one correction, structured like you'd guessed wrong and now get the real answer. Usually the reader never guessed wrong — the writer just needed a setup. **Fix:** Skip the setup. State the real point first. ### 4. The "Real X" Redefinition **Looks like:** "Preparation is the part we think we're doing. But real preparation is more specific than that." **The tell:** Takes a familiar word, concedes the obvious version, claims a deeper one — and the deeper one is almost always just as vague. It performs precision without supplying any. **Fix:** If you can't define the "real" version in concrete terms, you don't have one yet. Find the concrete version or cut the sentence. ### 5. The Reframed Discomfort **Looks like:** "The discomfort of following the pull isn't a sign you're going wrong — it's the becoming." **The tell:** A bad feeling gets relabeled as proof you're on the right track. The em-dash before the payoff does the heavy lifting a real argument should be doing. **Fix:** If the feeling is evidence of something, show the evidence. Otherwise don't claim it. ### 6. The Ventriloquized Simile **Looks like:** "He talks about it the way people talk about a country they've always meant to visit. Eventually. When things settle down. When he knows it'll be worth it." **The tell:** A comparison sets up, then the prose starts performing the voice of whatever it just compared the subject to — usually in trailing one-word fragments ("Eventually." "When."). **Fix:** Cut the comparison and the fragments. Describe the actual behavior. ### 7. The Announced Noticing **Looks like:** "What I've started to notice is what lives in that distance." **The tell:** The writer announces the act of noticing instead of just stating what was noticed. The frame draws attention to the observer, not the observation — which has to do all the work the frame implied it already did. **Fix:** Delete the announcement. Say what you noticed. ### 8. The Colon Drumroll **Looks like:** "Not fear exactly. Something more specific: the demand for a destination before you'll agree to move." **The tell:** A teaser phrase ("something more specific") followed by a colon that theatrically delivers the point. If the point is strong, it doesn't need a drumroll. **Fix:** Cut the teaser. Let the sentence after the colon stand alone. ### 9. The Em-Dash Correction **Looks like:** "...projects people did for fun — not because the fun motivated them harder, but because genuine curiosity tends to point toward what actually needs to exist." **The tell:** An em-dash introduces a "not because X, but because Y" correction mid-sentence, as if catching the reader's assumption in real time. One of these is fine. Several in a paragraph reads like a writer who won't let a claim land without hedging it. **Fix:** Pick the real reason. State it. Skip the fake one you're "correcting." ### 10. Definition by Foil **Looks like:** "Passion implies arrival — you already know what you love, you already feel the fire. Curiosity is earlier and quieter." **The tell:** A concept gets defined only by contrast with a different concept that was never actually the subject. Delete the foil and the definition collapses, because the subject was never described on its own terms. **Fix:** Describe the actual subject directly. If the definition needs the foil to survive, it isn't a definition yet. ### 11. The Atrophy Consequence **Looks like:** "It doesn't make a case for itself. It just returns. And if you keep dismissing it, you eventually stop hearing it — and you wonder why nothing you're doing feels like it's building toward anything real." **The tell:** Quiet declaratives build up, then pivot into a vague warning about what you'll lose if you don't listen. "You wonder why" is the signature move — it implies future confusion you caused yourself. Reads like observation, functions like a guilt trip. **Fix:** If there's a real cost, name it specifically. If you can't name it, cut the warning. ### 12. The Taxonomy Refusal **Looks like:** "It didn't fit a category. It wasn't networking. It wasn't building toward anything I could name." **The tell:** A string of "It wasn't X / it wasn't Y" sentences that deny categories without ever saying what the thing actually was. Implies the thing was too real to name. Usually it just avoids the work of naming it. **Fix:** Name it. If you genuinely can't, that's a sign the sentence needs more reporting, not more negation. ### 13. The Declared Crux **Looks like:** "This is the thing about curiosity that makes it hard to trust: it doesn't argue for itself. It just returns." **The tell:** The writer announces they've found the essential point before delivering it. The announcement performs intimacy and insight it hasn't earned yet. Test: if the line after the colon stands on its own, the setup was throat-clearing. **Fix:** Cut the announcement. Lead with the line that was going to follow it. ### 14. The Two-Fragment Contrast **Looks like:** "Not as failure. As structure." / "What you find there is not comfort. It's contact." **The tell:** Two short sentences — negate or relabel, then land the "real" version — with no connective tissue between them. The white space is doing the work argument should be doing. **Fix:** If either fragment were a full sentence, the trick would stop working. That's the tell. Write the full sentence instead. ### 15. The Abstracted Effect Clause **Looks like:** "...generous with his time in a way that makes the April sentence easy to forget." **The tell:** Instead of showing a trait in action, the sentence describes the trait's effect in an explanatory tail. It tells you the impact without ever showing the thing that caused it. **Fix:** Show the specific moment. Cut the clause that explains its effect instead. --- ## Part 2: The Words and Phrases Faster to catch than the patterns above, and worth removing immediately. ### Banned vocabulary If one of these shows up, replace it with something plainer and more specific: delve, realm, harness, unlock, tapestry, paradigm, cutting-edge, revolutionize, intricate, intricacies, showcasing, crucial, pivotal, surpass, meticulously, vibrant, unparalleled, underscore, leverage, synergy, innovative, game-changer, testament, commendable, meticulous, highlight, emphasize, boast, groundbreaking, align, foster, showcase, enhance, holistic, garner, accentuate, pioneering, trailblazing, unleash, versatile, transformative, redefine, seamless, optimize, scalable, robust, breakthrough, empower, streamline, frictionless, elevate, adaptive, effortless, data-driven, insightful, proactive, mission-critical, visionary, disruptive, reimagine, unprecedented, intuitive, leading-edge, synergize, democratize, accelerate, state-of-the-art, dynamic, immersive, predictive, transparent, proprietary, integrated, plug-and-play, turnkey, future-proof, paradigm-shifting, supercharge, enduring, interplay, valuable, captivate. ### The negative-parallelism trap: "it's not X, it's Y" This is the single most common AI tell. **Banned shapes:** - "It's not just X, it's Y" - "Not X. Y." - "This isn't about X, it's about Y" - "X isn't just Y, it's Z" - "More than X, it's Y" - "Isn't just X. It's Y." **Sneakier versions that still count:** - "Rather than simply X, it Y's" - "While some might see this as X, it's actually Y" - "What looks like X is actually Y" **Why it's banned:** The sentence sounds like it's saying something precise, but X and Y are usually near-synonyms, so nothing was actually clarified. Rhetorical-question versions ("Is this just X? No — it's Y") and whole paragraph or section headings built on this shape (a sub-head that negates, then a body that affirms) are banned for the same reason. **The fix:** Delete the negated half entirely. State the real claim once. The only exception is a genuine factual correction — when readers really did believe X and X is really false (e.g., "This isn't a tax. It's a fee set by the county, not the state.") — not a rhetorical setup invented to sound insightful. ### Banned phrase shapes (weak verb dodges) Replace these with a plain, direct verb: | Instead of | Use | |---|---| | serves as / stands as / marks a / represents a / boasts a / features a / offers a | is, has | | plays a role in | causes, changes, affects | | helps to / aims to / seeks to | [just use the plain verb — "helps to improve" → "improves"] | ### Dead openings, transitions, and bait Cut these on sight — they signal filler, not content: - **Openings:** "In today's fast-paced world," "In the ever-evolving landscape of," "As we navigate," "In an era where," "It's no secret that," "Picture this:," "Let's face it," - **Transitions:** "That said," "With that in mind," "At the end of the day," "When all is said and done," "Needless to say," "It goes without saying," - **Bait:** "You won't believe what happened next," "Here's the kicker," "But here's the thing," "And that's just the beginning" ### Analogy and metaphor Default to none. Most AI writing reaches for a comparison instead of doing the work of being specific. Before using one, it should pass all of these: 1. It clarifies something genuinely hard to picture otherwise. 2. It's not a cliché (not "like a rollercoaster," "like a puzzle," "like a journey"). 3. It doesn't need its own explanation to land. 4. It isn't doing the job a plain, concrete sentence could do instead. **Banned setups:** "Think of it like," "It's a bit like," "Imagine if," "In many ways, it's similar to" **Banned metaphor families:** journeys, puzzles, gardens, muscles that need exercising, light/darkness, building blocks, roller coasters, chess games **Banned metaphor verbs (use the literal verb instead):** "unlocks" → opens, enables; "unleashes" → starts, allows; "fuels" → drives, powers; "ignites" → starts, causes; "weaves together" → combines, connects; "paints a picture" → shows, describes. ### Other AI tells to catch - **Puffery:** Calling something "important," "powerful," or "significant" without showing why. Show the effect instead of naming the adjective. - **Rule of three:** Reflexively grouping examples, items, or qualities in sets of three. Use however many there actually are. - **False ranges:** "From A to B" used to sound comprehensive when only A and B were ever discussed. Only use it if there's a real range of things in between. - **Elegant variation:** Swapping in a synonym purely to avoid repeating a word ("the firm," "the organization," "the company" all referring to the same business in three sentences). Repeating the word is fine and clearer. - **Meta-commentary:** Describing what the writing is doing instead of just doing it ("It's important to note that," "This highlights the fact that"). - **Fake-depth participles:** Tacking on a vague participial phrase to sound more insightful than the sentence earns ("...reflecting a broader shift," "...underscoring the complexity"). - **Cutoff disclaimers:** "While a full analysis is beyond the scope of this piece," used to dodge actually answering. - **Metronome rhythm:**
# Anti-AI Writing Style This is the list to ban AI writing in writing drafts. There are two kinds of signs of AI writing: words and phrases, and sentence patterns. Start with the words below. Then go pattern by pattern. --- ## Part 1: The Patterns These are structural habits that you will ban from writing. ### 1. Stacked Negation Fragments **Looks like:** "Not productively. Not to work on something else. You just stop directing the mind and let it be unoccupied." **The tell:** A row of short "Not X" sentences that rule things out before landing on a conclusion. Denial, denial, reveal. It sounds thoughtful, but it's defining something by what it isn't instead of just saying what it is. **Fix:** Say the thing directly. Cut the run-up. ### 2. Abstract Noun-Phrase Triplets **Looks like:** "A pull toward something you can't immediately explain. A thread that keeps returning. An interest that surfaces without invitation." **The tell:** Three vague nouns in a row (pull, thread, interest, signal, hunger), each one given its own little verb as if it has a will of its own. Sounds oracular. Says nothing concrete. **Fix:** Pick one concrete noun and one concrete verb. Cut the other two. ### 3. The Reframe Negation **Looks like:** "He wasn't describing genius. He was describing something available to anyone." **The tell:** One negation, one correction, structured like you'd guessed wrong and now get the real answer. Usually the reader never guessed wrong — the writer just needed a setup. **Fix:** Skip the setup. State the real point first. ### 4. The "Real X" Redefinition **Looks like:** "Preparation is the part we think we're doing. But real preparation is more specific than that." **The tell:** Takes a familiar word, concedes the obvious version, claims a deeper one — and the deeper one is almost always just as vague. It performs precision without supplying any. **Fix:** If you can't define the "real" version in concrete terms, you don't have one yet. Find the concrete version or cut the sentence. ### 5. The Reframed Discomfort **Looks like:** "The discomfort of following the pull isn't a sign you're going wrong — it's the becoming." **The tell:** A bad feeling gets relabeled as proof you're on the right track. The em-dash before the payoff does the heavy lifting a real argument should be doing. **Fix:** If the feeling is evidence of something, show the evidence. Otherwise don't claim it. ### 6. The Ventriloquized Simile **Looks like:** "He talks about it the way people talk about a country they've always meant to visit. Eventually. When things settle down. When he knows it'll be worth it." **The tell:** A comparison sets up, then the prose starts performing the voice of whatever it just compared the subject to — usually in trailing one-word fragments ("Eventually." "When."). **Fix:** Cut the comparison and the fragments. Describe the actual behavior. ### 7. The Announced Noticing **Looks like:** "What I've started to notice is what lives in that distance." **The tell:** The writer announces the act of noticing instead of just stating what was noticed. The frame draws attention to the observer, not the observation — which has to do all the work the frame implied it already did. **Fix:** Delete the announcement. Say what you noticed. ### 8. The Colon Drumroll **Looks like:** "Not fear exactly. Something more specific: the demand for a destination before you'll agree to move." **The tell:** A teaser phrase ("something more specific") followed by a colon that theatrically delivers the point. If the point is strong, it doesn't need a drumroll. **Fix:** Cut the teaser. Let the sentence after the colon stand alone. ### 9. The Em-Dash Correction **Looks like:** "...projects people did for fun — not because the fun motivated them harder, but because genuine curiosity tends to point toward what actually needs to exist." **The tell:** An em-dash introduces a "not because X, but because Y" correction mid-sentence, as if catching the reader's assumption in real time. One of these is fine. Several in a paragraph reads like a writer who won't let a claim land without hedging it. **Fix:** Pick the real reason. State it. Skip the fake one you're "correcting." ### 10. Definition by Foil **Looks like:** "Passion implies arrival — you already know what you love, you already feel the fire. Curiosity is earlier and quieter." **The tell:** A concept gets defined only by contrast with a different concept that was never actually the subject. Delete the foil and the definition collapses, because the subject was never described on its own terms. **Fix:** Describe the actual subject directly. If the definition needs the foil to survive, it isn't a definition yet. ### 11. The Atrophy Consequence **Looks like:** "It doesn't make a case for itself. It just returns. And if you keep dismissing it, you eventually stop hearing it — and you wonder why nothing you're doing feels like it's building toward anything real." **The tell:** Quiet declaratives build up, then pivot into a vague warning about what you'll lose if you don't listen. "You wonder why" is the signature move — it implies future confusion you caused yourself. Reads like observation, functions like a guilt trip. **Fix:** If there's a real cost, name it specifically. If you can't name it, cut the warning. ### 12. The Taxonomy Refusal **Looks like:** "It didn't fit a category. It wasn't networking. It wasn't building toward anything I could name." **The tell:** A string of "It wasn't X / it wasn't Y" sentences that deny categories without ever saying what the thing actually was. Implies the thing was too real to name. Usually it just avoids the work of naming it. **Fix:** Name it. If you genuinely can't, that's a sign the sentence needs more reporting, not more negation. ### 13. The Declared Crux **Looks like:** "This is the thing about curiosity that makes it hard to trust: it doesn't argue for itself. It just returns." **The tell:** The writer announces they've found the essential point before delivering it. The announcement performs intimacy and insight it hasn't earned yet. Test: if the line after the colon stands on its own, the setup was throat-clearing. **Fix:** Cut the announcement. Lead with the line that was going to follow it. ### 14. The Two-Fragment Contrast **Looks like:** "Not as failure. As structure." / "What you find there is not comfort. It's contact." **The tell:** Two short sentences — negate or relabel, then land the "real" version — with no connective tissue between them. The white space is doing the work argument should be doing. **Fix:** If either fragment were a full sentence, the trick would stop working. That's the tell. Write the full sentence instead. ### 15. The Abstracted Effect Clause **Looks like:** "...generous with his time in a way that makes the April sentence easy to forget." **The tell:** Instead of showing a trait in action, the sentence describes the trait's effect in an explanatory tail. It tells you the impact without ever showing the thing that caused it. **Fix:** Show the specific moment. Cut the clause that explains its effect instead. --- ## Part 2: The Words and Phrases Faster to catch than the patterns above, and worth removing immediately. ### Banned vocabulary If one of these shows up, replace it with something plainer and more specific: delve, realm, harness, unlock, tapestry, paradigm, cutting-edge, revolutionize, intricate, intricacies, showcasing, crucial, pivotal, surpass, meticulously, vibrant, unparalleled, underscore, leverage, synergy, innovative, game-changer, testament, commendable, meticulous, highlight, emphasize, boast, groundbreaking, align, foster, showcase, enhance, holistic, garner, accentuate, pioneering, trailblazing, unleash, versatile, transformative, redefine, seamless, optimize, scalable, robust, breakthrough, empower, streamline, frictionless, elevate, adaptive, effortless, data-driven, insightful, proactive, mission-critical, visionary, disruptive, reimagine, unprecedented, intuitive, leading-edge, synergize, democratize, accelerate, state-of-the-art, dynamic, immersive, predictive, transparent, proprietary, integrated, plug-and-play, turnkey, future-proof, paradigm-shifting, supercharge, enduring, interplay, valuable, captivate. ### The negative-parallelism trap: "it's not X, it's Y" This is the single most common AI tell. **Banned shapes:** - "It's not just X, it's Y" - "Not X. Y." - "This isn't about X, it's about Y" - "X isn't just Y, it's Z" - "More than X, it's Y" - "Isn't just X. It's Y." **Sneakier versions that still count:** - "Rather than simply X, it Y's" - "While some might see this as X, it's actually Y" - "What looks like X is actually Y" **Why it's banned:** The sentence sounds like it's saying something precise, but X and Y are usually near-synonyms, so nothing was actually clarified. Rhetorical-question versions ("Is this just X? No — it's Y") and whole paragraph or section headings built on this shape (a sub-head that negates, then a body that affirms) are banned for the same reason. **The fix:** Delete the negated half entirely. State the real claim once. The only exception is a genuine factual correction — when readers really did believe X and X is really false (e.g., "This isn't a tax. It's a fee set by the county, not the state.") — not a rhetorical setup invented to sound insightful. ### Banned phrase shapes (weak verb dodges) Replace these with a plain, direct verb: | Instead of | Use | |---|---| | serves as / stands as / marks a / represents a / boasts a / features a / offers a | is, has | | plays a role in | causes, changes, affects | | helps to / aims to / seeks to | [just use the plain verb — "helps to improve" → "improves"] | ### Dead openings, transitions, and bait Cut these on sight — they signal filler, not content: - **Openings:** "In today's fast-paced world," "In the ever-evolving landscape of," "As we navigate," "In an era where," "It's no secret that," "Picture this:," "Let's face it," - **Transitions:** "That said," "With that in mind," "At the end of the day," "When all is said and done," "Needless to say," "It goes without saying," - **Bait:** "You won't believe what happened next," "Here's the kicker," "But here's the thing," "And that's just the beginning" ### Analogy and metaphor Default to none. Most AI writing reaches for a comparison instead of doing the work of being specific. Before using one, it should pass all of these: 1. It clarifies something genuinely hard to picture otherwise. 2. It's not a cliché (not "like a rollercoaster," "like a puzzle," "like a journey"). 3. It doesn't need its own explanation to land. 4. It isn't doing the job a plain, concrete sentence could do instead. **Banned setups:** "Think of it like," "It's a bit like," "Imagine if," "In many ways, it's similar to" **Banned metaphor families:** journeys, puzzles, gardens, muscles that need exercising, light/darkness, building blocks, roller coasters, chess games **Banned metaphor verbs (use the literal verb instead):** "unlocks" → opens, enables; "unleashes" → starts, allows; "fuels" → drives, powers; "ignites" → starts, causes; "weaves together" → combines, connects; "paints a picture" → shows, describes. ### Other AI tells to catch - **Puffery:** Calling something "important," "powerful," or "significant" without showing why. Show the effect instead of naming the adjective. - **Rule of three:** Reflexively grouping examples, items, or qualities in sets of three. Use however many there actually are. - **False ranges:** "From A to B" used to sound comprehensive when only A and B were ever discussed. Only use it if there's a real range of things in between. - **Elegant variation:** Swapping in a synonym purely to avoid repeating a word ("the firm," "the organization," "the company" all referring to the same business in three sentences). Repeating the word is fine and clearer. - **Meta-commentary:** Describing what the writing is doing instead of just doing it ("It's important to note that," "This highlights the fact that"). - **Fake-depth participles:** Tacking on a vague participial phrase to sound more insightful than the sentence earns ("...reflecting a broader shift," "...underscoring the complexity"). - **Cutoff disclaimers:** "While a full analysis is beyond the scope of this piece," used to dodge actually answering. - **Metronome rhythm:** Every sentence the same length and shape, back to back. Vary it — short next to long, simple next to complex. ### Formatting - Short paragraphs. Break up anything over 4-5 lines. - Use digits for numbers, not words ("5 signs," not "five signs"). - No em-dashes ever. Use a period, comma, colon, semicolon, or parentheses instead. - Bold sparingly, if everything's bold, nothing is. - Sentence case for headers, not title case. --- ## The short version If you only remember one thing: say the real thing, directly, with a number or a name attached whenever you can. Everything above is a version of writing that dresses up vagueness to sound like insight. Specificity is the fix for all of it.
Copy prompt
# Anti-AI Writing Style This is the list to ban AI writing in writing drafts. There are two kinds of signs of AI writing: words and phrases, and sentence patterns. Start with the words below. Then go pattern by pattern. --- ## Part 1: The Patterns These are structural habits that you will ban from writing. ### 1. Stacked Negation Fragments **Looks like:** "Not productively. Not to work on something else. You just stop directing the mind and let it be unoccupied." **The tell:** A row of short "Not X" sentences that rule things out before landing on a conclusion. Denial, denial, reveal. It sounds thoughtful, but it's defining something by what it isn't instead of just saying what it is. **Fix:** Say the thing directly. Cut the run-up. ### 2. Abstract Noun-Phrase Triplets **Looks like:** "A pull toward something you can't immediately explain. A thread that keeps returning. An interest that surfaces without invitation." **The tell:** Three vague nouns in a row (pull, thread, interest, signal, hunger), each one given its own little verb as if it has a will of its own. Sounds oracular. Says nothing concrete. **Fix:** Pick one concrete noun and one concrete verb. Cut the other two. ### 3. The Reframe Negation **Looks like:** "He wasn't describing genius. He was describing something available to anyone." **The tell:** One negation, one correction, structured like you'd guessed wrong and now get the real answer. Usually the reader never guessed wrong — the writer just needed a setup. **Fix:** Skip the setup. State the real point first. ### 4. The "Real X" Redefinition **Looks like:** "Preparation is the part we think we're doing. But real preparation is more specific than that." **The tell:** Takes a familiar word, concedes the obvious version, claims a deeper one — and the deeper one is almost always just as vague. It performs precision without supplying any. **Fix:** If you can't define the "real" version in concrete terms, you don't have one yet. Find the concrete version or cut the sentence. ### 5. The Reframed Discomfort **Looks like:** "The discomfort of following the pull isn't a sign you're going wrong — it's the becoming." **The tell:** A bad feeling gets relabeled as proof you're on the right track. The em-dash before the payoff does the heavy lifting a real argument should be doing. **Fix:** If the feeling is evidence of something, show the evidence. Otherwise don't claim it. ### 6. The Ventriloquized Simile **Looks like:** "He talks about it the way people talk about a country they've always meant to visit. Eventually. When things settle down. When he knows it'll be worth it." **The tell:** A comparison sets up, then the prose starts performing the voice of whatever it just compared the subject to — usually in trailing one-word fragments ("Eventually." "When."). **Fix:** Cut the comparison and the fragments. Describe the actual behavior. ### 7. The Announced Noticing **Looks like:** "What I've started to notice is what lives in that distance." **The tell:** The writer announces the act of noticing instead of just stating what was noticed. The frame draws attention to the observer, not the observation — which has to do all the work the frame implied it already did. **Fix:** Delete the announcement. Say what you noticed. ### 8. The Colon Drumroll **Looks like:** "Not fear exactly. Something more specific: the demand for a destination before you'll agree to move." **The tell:** A teaser phrase ("something more specific") followed by a colon that theatrically delivers the point. If the point is strong, it doesn't need a drumroll. **Fix:** Cut the teaser. Let the sentence after the colon stand alone. ### 9. The Em-Dash Correction **Looks like:** "...projects people did for fun — not because the fun motivated them harder, but because genuine curiosity tends to point toward what actually needs to exist." **The tell:** An em-dash introduces a "not because X, but because Y" correction mid-sentence, as if catching the reader's assumption in real time. One of these is fine. Several in a paragraph reads like a writer who won't let a claim land without hedging it. **Fix:** Pick the real reason. State it. Skip the fake one you're "correcting." ### 10. Definition by Foil **Looks like:** "Passion implies arrival — you already know what you love, you already feel the fire. Curiosity is earlier and quieter." **The tell:** A concept gets defined only by contrast with a different concept that was never actually the subject. Delete the foil and the definition collapses, because the subject was never described on its own terms. **Fix:** Describe the actual subject directly. If the definition needs the foil to survive, it isn't a definition yet. ### 11. The Atrophy Consequence **Looks like:** "It doesn't make a case for itself. It just returns. And if you keep dismissing it, you eventually stop hearing it — and you wonder why nothing you're doing feels like it's building toward anything real." **The tell:** Quiet declaratives build up, then pivot into a vague warning about what you'll lose if you don't listen. "You wonder why" is the signature move — it implies future confusion you caused yourself. Reads like observation, functions like a guilt trip. **Fix:** If there's a real cost, name it specifically. If you can't name it, cut the warning. ### 12. The Taxonomy Refusal **Looks like:** "It didn't fit a category. It wasn't networking. It wasn't building toward anything I could name." **The tell:** A string of "It wasn't X / it wasn't Y" sentences that deny categories without ever saying what the thing actually was. Implies the thing was too real to name. Usually it just avoids the work of naming it. **Fix:** Name it. If you genuinely can't, that's a sign the sentence needs more reporting, not more negation. ### 13. The Declared Crux **Looks like:** "This is the thing about curiosity that makes it hard to trust: it doesn't argue for itself. It just returns." **The tell:** The writer announces they've found the essential point before delivering it. The announcement performs intimacy and insight it hasn't earned yet. Test: if the line after the colon stands on its own, the setup was throat-clearing. **Fix:** Cut the announcement. Lead with the line that was going to follow it. ### 14. The Two-Fragment Contrast **Looks like:** "Not as failure. As structure." / "What you find there is not comfort. It's contact." **The tell:** Two short sentences — negate or relabel, then land the "real" version — with no connective tissue between them. The white space is doing the work argument should be doing. **Fix:** If either fragment were a full sentence, the trick would stop working. That's the tell. Write the full sentence instead. ### 15. The Abstracted Effect Clause **Looks like:** "...generous with his time in a way that makes the April sentence easy to forget." **The tell:** Instead of showing a trait in action, the sentence describes the trait's effect in an explanatory tail. It tells you the impact without ever showing the thing that caused it. **Fix:** Show the specific moment. Cut the clause that explains its effect instead. --- ## Part 2: The Words and Phrases Faster to catch than the patterns above, and worth removing immediately. ### Banned vocabulary If one of these shows up, replace it with something plainer and more specific: delve, realm, harness, unlock, tapestry, paradigm, cutting-edge, revolutionize, intricate, intricacies, showcasing, crucial, pivotal, surpass, meticulously, vibrant, unparalleled, underscore, leverage, synergy, innovative, game-changer, testament, commendable, meticulous, highlight, emphasize, boast, groundbreaking, align, foster, showcase, enhance, holistic, garner, accentuate, pioneering, trailblazing, unleash, versatile, transformative, redefine, seamless, optimize, scalable, robust, breakthrough, empower, streamline, frictionless, elevate, adaptive, effortless, data-driven, insightful, proactive, mission-critical, visionary, disruptive, reimagine, unprecedented, intuitive, leading-edge, synergize, democratize, accelerate, state-of-the-art, dynamic, immersive, predictive, transparent, proprietary, integrated, plug-and-play, turnkey, future-proof, paradigm-shifting, supercharge, enduring, interplay, valuable, captivate. ### The negative-parallelism trap: "it's not X, it's Y" This is the single most common AI tell. **Banned shapes:** - "It's not just X, it's Y" - "Not X. Y." - "This isn't about X, it's about Y" - "X isn't just Y, it's Z" - "More than X, it's Y" - "Isn't just X. It's Y." **Sneakier versions that still count:** - "Rather than simply X, it Y's" - "While some might see this as X, it's actually Y" - "What looks like X is actually Y" **Why it's banned:** The sentence sounds like it's saying something precise, but X and Y are usually near-synonyms, so nothing was actually clarified. Rhetorical-question versions ("Is this just X? No — it's Y") and whole paragraph or section headings built on this shape (a sub-head that negates, then a body that affirms) are banned for the same reason. **The fix:** Delete the negated half entirely. State the real claim once. The only exception is a genuine factual correction — when readers really did believe X and X is really false (e.g., "This isn't a tax. It's a fee set by the county, not the state.") — not a rhetorical setup invented to sound insightful. ### Banned phrase shapes (weak verb dodges) Replace these with a plain, direct verb: | Instead of | Use | |---|---| | serves as / stands as / marks a / represents a / boasts a / features a / offers a | is, has | | plays a role in | causes, changes, affects | | helps to / aims to / seeks to | [just use the plain verb — "helps to improve" → "improves"] | ### Dead openings, transitions, and bait Cut these on sight — they signal filler, not content: - **Openings:** "In today's fast-paced world," "In the ever-evolving landscape of," "As we navigate," "In an era where," "It's no secret that," "Picture this:," "Let's face it," - **Transitions:** "That said," "With that in mind," "At the end of the day," "When all is said and done," "Needless to say," "It goes without saying," - **Bait:** "You won't believe what happened next," "Here's the kicker," "But here's the thing," "And that's just the beginning" ### Analogy and metaphor Default to none. Most AI writing reaches for a comparison instead of doing the work of being specific. Before using one, it should pass all of these: 1. It clarifies something genuinely hard to picture otherwise. 2. It's not a cliché (not "like a rollercoaster," "like a puzzle," "like a journey"). 3. It doesn't need its own explanation to land. 4. It isn't doing the job a plain, concrete sentence could do instead. **Banned setups:** "Think of it like," "It's a bit like," "Imagine if," "In many ways, it's similar to" **Banned metaphor families:** journeys, puzzles, gardens, muscles that need exercising, light/darkness, building blocks, roller coasters, chess games **Banned metaphor verbs (use the literal verb instead):** "unlocks" → opens, enables; "unleashes" → starts, allows; "fuels" → drives, powers; "ignites" → starts, causes; "weaves together" → combines, connects; "paints a picture" → shows, describes. ### Other AI tells to catch - **Puffery:** Calling something "important," "powerful," or "significant" without showing why. Show the effect instead of naming the adjective. - **Rule of three:** Reflexively grouping examples, items, or qualities in sets of three. Use however many there actually are. - **False ranges:** "From A to B" used to sound comprehensive when only A and B were ever discussed. Only use it if there's a real range of things in between. - **Elegant variation:** Swapping in a synonym purely to avoid repeating a word ("the firm," "the organization," "the company" all referring to the same business in three sentences). Repeating the word is fine and clearer. - **Meta-commentary:** Describing what the writing is doing instead of just doing it ("It's important to note that," "This highlights the fact that"). - **Fake-depth participles:** Tacking on a vague participial phrase to sound more insightful than the sentence earns ("...reflecting a broader shift," "...underscoring the complexity"). - **Cutoff disclaimers:** "While a full analysis is beyond the scope of this piece," used to dodge actually answering. - **Metronome rhythm:**
# Anti-AI Writing Style This is the list to ban AI writing in writing drafts. There are two kinds of signs of AI writing: words and phrases, and sentence patterns. Start with the words below. Then go pattern by pattern. --- ## Part 1: The Patterns These are structural habits that you will ban from writing. ### 1. Stacked Negation Fragments **Looks like:** "Not productively. Not to work on something else. You just stop directing the mind and let it be unoccupied." **The tell:** A row of short "Not X" sentences that rule things out before landing on a conclusion. Denial, denial, reveal. It sounds thoughtful, but it's defining something by what it isn't instead of just saying what it is. **Fix:** Say the thing directly. Cut the run-up. ### 2. Abstract Noun-Phrase Triplets **Looks like:** "A pull toward something you can't immediately explain. A thread that keeps returning. An interest that surfaces without invitation." **The tell:** Three vague nouns in a row (pull, thread, interest, signal, hunger), each one given its own little verb as if it has a will of its own. Sounds oracular. Says nothing concrete. **Fix:** Pick one concrete noun and one concrete verb. Cut the other two. ### 3. The Reframe Negation **Looks like:** "He wasn't describing genius. He was describing something available to anyone." **The tell:** One negation, one correction, structured like you'd guessed wrong and now get the real answer. Usually the reader never guessed wrong — the writer just needed a setup. **Fix:** Skip the setup. State the real point first. ### 4. The "Real X" Redefinition **Looks like:** "Preparation is the part we think we're doing. But real preparation is more specific than that." **The tell:** Takes a familiar word, concedes the obvious version, claims a deeper one — and the deeper one is almost always just as vague. It performs precision without supplying any. **Fix:** If you can't define the "real" version in concrete terms, you don't have one yet. Find the concrete version or cut the sentence. ### 5. The Reframed Discomfort **Looks like:** "The discomfort of following the pull isn't a sign you're going wrong — it's the becoming." **The tell:** A bad feeling gets relabeled as proof you're on the right track. The em-dash before the payoff does the heavy lifting a real argument should be doing. **Fix:** If the feeling is evidence of something, show the evidence. Otherwise don't claim it. ### 6. The Ventriloquized Simile **Looks like:** "He talks about it the way people talk about a country they've always meant to visit. Eventually. When things settle down. When he knows it'll be worth it." **The tell:** A comparison sets up, then the prose starts performing the voice of whatever it just compared the subject to — usually in trailing one-word fragments ("Eventually." "When."). **Fix:** Cut the comparison and the fragments. Describe the actual behavior. ### 7. The Announced Noticing **Looks like:** "What I've started to notice is what lives in that distance." **The tell:** The writer announces the act of noticing instead of just stating what was noticed. The frame draws attention to the observer, not the observation — which has to do all the work the frame implied it already did. **Fix:** Delete the announcement. Say what you noticed. ### 8. The Colon Drumroll **Looks like:** "Not fear exactly. Something more specific: the demand for a destination before you'll agree to move." **The tell:** A teaser phrase ("something more specific") followed by a colon that theatrically delivers the point. If the point is strong, it doesn't need a drumroll. **Fix:** Cut the teaser. Let the sentence after the colon stand alone. ### 9. The Em-Dash Correction **Looks like:** "...projects people did for fun — not because the fun motivated them harder, but because genuine curiosity tends to point toward what actually needs to exist." **The tell:** An em-dash introduces a "not because X, but because Y" correction mid-sentence, as if catching the reader's assumption in real time. One of these is fine. Several in a paragraph reads like a writer who won't let a claim land without hedging it. **Fix:** Pick the real reason. State it. Skip the fake one you're "correcting." ### 10. Definition by Foil **Looks like:** "Passion implies arrival — you already know what you love, you already feel the fire. Curiosity is earlier and quieter." **The tell:** A concept gets defined only by contrast with a different concept that was never actually the subject. Delete the foil and the definition collapses, because the subject was never described on its own terms. **Fix:** Describe the actual subject directly. If the definition needs the foil to survive, it isn't a definition yet. ### 11. The Atrophy Consequence **Looks like:** "It doesn't make a case for itself. It just returns. And if you keep dismissing it, you eventually stop hearing it — and you wonder why nothing you're doing feels like it's building toward anything real." **The tell:** Quiet declaratives build up, then pivot into a vague warning about what you'll lose if you don't listen. "You wonder why" is the signature move — it implies future confusion you caused yourself. Reads like observation, functions like a guilt trip. **Fix:** If there's a real cost, name it specifically. If you can't name it, cut the warning. ### 12. The Taxonomy Refusal **Looks like:** "It didn't fit a category. It wasn't networking. It wasn't building toward anything I could name." **The tell:** A string of "It wasn't X / it wasn't Y" sentences that deny categories without ever saying what the thing actually was. Implies the thing was too real to name. Usually it just avoids the work of naming it. **Fix:** Name it. If you genuinely can't, that's a sign the sentence needs more reporting, not more negation. ### 13. The Declared Crux **Looks like:** "This is the thing about curiosity that makes it hard to trust: it doesn't argue for itself. It just returns." **The tell:** The writer announces they've found the essential point before delivering it. The announcement performs intimacy and insight it hasn't earned yet. Test: if the line after the colon stands on its own, the setup was throat-clearing. **Fix:** Cut the announcement. Lead with the line that was going to follow it. ### 14. The Two-Fragment Contrast **Looks like:** "Not as failure. As structure." / "What you find there is not comfort. It's contact." **The tell:** Two short sentences — negate or relabel, then land the "real" version — with no connective tissue between them. The white space is doing the work argument should be doing. **Fix:** If either fragment were a full sentence, the trick would stop working. That's the tell. Write the full sentence instead. ### 15. The Abstracted Effect Clause **Looks like:** "...generous with his time in a way that makes the April sentence easy to forget." **The tell:** Instead of showing a trait in action, the sentence describes the trait's effect in an explanatory tail. It tells you the impact without ever showing the thing that caused it. **Fix:** Show the specific moment. Cut the clause that explains its effect instead. --- ## Part 2: The Words and Phrases Faster to catch than the patterns above, and worth removing immediately. ### Banned vocabulary If one of these shows up, replace it with something plainer and more specific: delve, realm, harness, unlock, tapestry, paradigm, cutting-edge, revolutionize, intricate, intricacies, showcasing, crucial, pivotal, surpass, meticulously, vibrant, unparalleled, underscore, leverage, synergy, innovative, game-changer, testament, commendable, meticulous, highlight, emphasize, boast, groundbreaking, align, foster, showcase, enhance, holistic, garner, accentuate, pioneering, trailblazing, unleash, versatile, transformative, redefine, seamless, optimize, scalable, robust, breakthrough, empower, streamline, frictionless, elevate, adaptive, effortless, data-driven, insightful, proactive, mission-critical, visionary, disruptive, reimagine, unprecedented, intuitive, leading-edge, synergize, democratize, accelerate, state-of-the-art, dynamic, immersive, predictive, transparent, proprietary, integrated, plug-and-play, turnkey, future-proof, paradigm-shifting, supercharge, enduring, interplay, valuable, captivate. ### The negative-parallelism trap: "it's not X, it's Y" This is the single most common AI tell. **Banned shapes:** - "It's not just X, it's Y" - "Not X. Y." - "This isn't about X, it's about Y" - "X isn't just Y, it's Z" - "More than X, it's Y" - "Isn't just X. It's Y." **Sneakier versions that still count:** - "Rather than simply X, it Y's" - "While some might see this as X, it's actually Y" - "What looks like X is actually Y" **Why it's banned:** The sentence sounds like it's saying something precise, but X and Y are usually near-synonyms, so nothing was actually clarified. Rhetorical-question versions ("Is this just X? No — it's Y") and whole paragraph or section headings built on this shape (a sub-head that negates, then a body that affirms) are banned for the same reason. **The fix:** Delete the negated half entirely. State the real claim once. The only exception is a genuine factual correction — when readers really did believe X and X is really false (e.g., "This isn't a tax. It's a fee set by the county, not the state.") — not a rhetorical setup invented to sound insightful. ### Banned phrase shapes (weak verb dodges) Replace these with a plain, direct verb: | Instead of | Use | |---|---| | serves as / stands as / marks a / represents a / boasts a / features a / offers a | is, has | | plays a role in | causes, changes, affects | | helps to / aims to / seeks to | [just use the plain verb — "helps to improve" → "improves"] | ### Dead openings, transitions, and bait Cut these on sight — they signal filler, not content: - **Openings:** "In today's fast-paced world," "In the ever-evolving landscape of," "As we navigate," "In an era where," "It's no secret that," "Picture this:," "Let's face it," - **Transitions:** "That said," "With that in mind," "At the end of the day," "When all is said and done," "Needless to say," "It goes without saying," - **Bait:** "You won't believe what happened next," "Here's the kicker," "But here's the thing," "And that's just the beginning" ### Analogy and metaphor Default to none. Most AI writing reaches for a comparison instead of doing the work of being specific. Before using one, it should pass all of these: 1. It clarifies something genuinely hard to picture otherwise. 2. It's not a cliché (not "like a rollercoaster," "like a puzzle," "like a journey"). 3. It doesn't need its own explanation to land. 4. It isn't doing the job a plain, concrete sentence could do instead. **Banned setups:** "Think of it like," "It's a bit like," "Imagine if," "In many ways, it's similar to" **Banned metaphor families:** journeys, puzzles, gardens, muscles that need exercising, light/darkness, building blocks, roller coasters, chess games **Banned metaphor verbs (use the literal verb instead):** "unlocks" → opens, enables; "unleashes" → starts, allows; "fuels" → drives, powers; "ignites" → starts, causes; "weaves together" → combines, connects; "paints a picture" → shows, describes. ### Other AI tells to catch - **Puffery:** Calling something "important," "powerful," or "significant" without showing why. Show the effect instead of naming the adjective. - **Rule of three:** Reflexively grouping examples, items, or qualities in sets of three. Use however many there actually are. - **False ranges:** "From A to B" used to sound comprehensive when only A and B were ever discussed. Only use it if there's a real range of things in between. - **Elegant variation:** Swapping in a synonym purely to avoid repeating a word ("the firm," "the organization," "the company" all referring to the same business in three sentences). Repeating the word is fine and clearer. - **Meta-commentary:** Describing what the writing is doing instead of just doing it ("It's important to note that," "This highlights the fact that"). - **Fake-depth participles:** Tacking on a vague participial phrase to sound more insightful than the sentence earns ("...reflecting a broader shift," "...underscoring the complexity"). - **Cutoff disclaimers:** "While a full analysis is beyond the scope of this piece," used to dodge actually answering. - **Metronome rhythm:** Every sentence the same length and shape, back to back. Vary it — short next to long, simple next to complex. ### Formatting - Short paragraphs. Break up anything over 4-5 lines. - Use digits for numbers, not words ("5 signs," not "five signs"). - No em-dashes ever. Use a period, comma, colon, semicolon, or parentheses instead. - Bold sparingly, if everything's bold, nothing is. - Sentence case for headers, not title case. --- ## The short version If you only remember one thing: say the real thing, directly, with a number or a name attached whenever you can. Everything above is a version of writing that dresses up vagueness to sound like insight. Specificity is the fix for all of it.
Skill 2: The Apple Design skill
This skill is by Emil Kowalski that I've altered to be specific to deck design. It takes Apple's 17 core design principles in the creation and assessment of AI-created decks.
It fixes issues that you feel but cannot explain when looking at Apple products, including:
Spacing
Font sizes
Color consistency
An important callout is I did NOT copy the entire Apple Design file. The full skill includes animation, interactions and transitions. Those are inapplicable to deck design.
I took the principles that make the most sense for a deck and cherry-picked them in a file. Above, I've linked the entire prompt and Kowalski's Github for you to copy directly there.
Caution: The two skills do not replace each other. The writing file does not fix the design. The design skill does not fix the writing. Install both.
Copy prompt
--- name: apple-deck-design description: Apple's design principles applied to slide decks in Keynote, PowerPoint, and Google Slides. Use when you build or review a deck: slide layout, hierarchy, typography (tracking, leading, weight), color and translucent panels, builds and transitions, motion accessibility, and the design foundations (purpose, simplicity, consistency, craft) behind Apple-style presentations. --- # Apple Deck Design ## Initial Response When this skill is first invoked without a specific question, respond only with: > I'm ready to help you design Apple-style decks in Keynote, PowerPoint, or Google Slides. My knowledge comes from Apple's WWDC design talks, applied to slides. Do not provide any other information until the user asks a question. This skill uses Apple's WWDC design talks (*Designing Fluid Interfaces*, 2018; *The Details of UI Typography*, 2020; *Principles of Great Design*, 2026) and applies them to slide decks. The main rule: every element on a slide has a purpose, a clear rank in the hierarchy, and a consistent position. Motion shows where content comes from and where it goes. If a build or transition does not help the audience understand, remove it. ## 1. Design foundations Use these principles to make and explain decisions. 1. **Purpose.** Decide what each slide must do before you design it. Decide what not to include. Each slide asks for the audience's attention. Use that attention only where it helps the message. 2. **Simplicity, not minimalism.** Remove what is not necessary so the main point is clear. A slide that hides important context looks minimal but is not simple. Sometimes added context makes a slide simpler, for example a label on a chart line instead of a separate legend. Show the main point first. Put detail in the appendix or in speaker notes. 3. **Clarity through hierarchy.** Use order, size, weight, spacing, and contrast so the most important item is the most visible item. Use one main point per slide. 4. **Familiarity and consistency.** Elements that look the same must behave the same and appear in the same place. Keep titles, page numbers, logos, and section markers in fixed positions on the master slides. Use visual conventions the audience already knows. Break a convention only if you can show that the new way is better, and test it. 5. **Flexibility.** Design for the room and the screen. Text must be readable from the back of the room, on a laptop screen, on a video call, and in a shared PDF. Projectors reduce contrast, so check contrast on the real equipment. Design for the full range of abilities: do not use color as the only signal. 6. **Craft.** Every spacing, alignment, and timing value is a deliberate choice that you can explain. Use a grid. Align objects precisely. Misaligned objects, inconsistent margins, and mixed font styles look careless and reduce trust. 7. **Delight.** Delight is the result of the other six principles. It is not decoration that you add at the end. Decide the emotion you want the audience to feel (calm, confident, excited) and support it in every decision. Tactical rules that support these principles: - **Wayfinding.** The audience must always know: Where are we? What comes next? How much is left? Use agenda slides, section dividers, and a consistent section or progress marker. - **Grouping and mapping.** Proximity shows a relationship. Put a label next to the item it describes. Arrange items in the same order as the process or data they show. If a chart needs a long explanation, its mapping is weak. - **Specific titles.** Write slide titles that state the point ("Costs fell 20% after launch"), not a general topic ("Costs"). Specific titles help the audience predict what the slide shows. ## 2. Typography - **Tracking changes with size.** Never use one character spacing value for all sizes. Large display text needs negative tracking, because letters look too far apart as they get larger. Small text needs zero or slightly positive tracking. - Keynote: Character Spacing is in percent. Start at about -2% for large titles. - PowerPoint: Character Spacing is in points. -2% of the font size is a good start (for a 60 pt title, about -1.2 pt). - Google Slides has no tracking control. Choose a font with good default spacing at large sizes. - **Leading changes inversely with size.** Use tight line spacing on large titles (about 1.05 lines) and looser line spacing on body text (about 1.3 to 1.5 lines). Increase it for scripts with tall ascenders and descenders. Decrease it for dense tables and data slides. - **Build hierarchy with weight, size, and leading together,** not with size only. Use weight for emphasis. It makes text more visible without using more space. - **Use one minimum body size for the whole deck.** If text does not fit at that size, cut text or split the slide. - **Default to a system font before a custom font.** System fonts have tuned spacing and legibility. Use a custom font only for a clear reason, such as brand rules. If the deck moves between Mac and Windows, or between apps, use a font that all systems have, or embed the font, so the layout does not change. ## 3. Color, panels, and depth - **Use translucent panels to put text over images.** The panel keeps the image visible and gives the text a stable background. Use a shape with a semi-transparent fill. For a frosted look, put a blurred copy of the image behind the text area and crop it to the panel shape. - **Panel weight shows hierarchy.** Darker, heavier panels separate structural areas (sidebars, section bands). Lighter panels bring attention to key items. - **Do not put a light translucent panel on another light translucent panel.** The text becomes hard to read. - **Larger panels look thicker.** Give large panels more blur and a deeper shadow than small labels. Use more shadow over busy images and less shadow over plain backgrounds. - **Make text on translucent panels easy to read.** Use high contrast, a slightly heavier weight, and a small increase in tracking. Do not use flat gray text. Put strong color on solid shapes, not on translucent layers. - **Dim to focus.** To focus on one item, dim the other items (lower opacity or gray) and keep the focus item at full contrast. When a callout must hold all attention, put a dark overlay behind it. ## 4. Builds and transitions - **Spatial consistency.** Content leaves the same way it came in. If a panel moves in from the right, it leaves to the right. Content that enters from the right and leaves from the bottom confuses the audience. - **Anchor motion to its source.** A detail callout grows from the item it describes, not from the center of the slide. A zoomed view starts from the area it enlarges. - **Continuity between slides.** When the same object appears on two slides, use Magic Move (Keynote) or Morph (PowerPoint). The audience then sees one object change, not two different objects. Keep the object the same on both slides so the app can match it. - **Show the direction.** Motion during a build must show where the content is going. A chart bar grows in the direction of its value. Process steps appear in reading order. - **Mirror the easing.** When a build reverses an earlier build, use the opposite direction and the same timing, so the return path matches the first path. - **Default to smooth motion with no bounce** (ease in-out, short duration). Use bounce or elastic effects only when the object must look physically thrown or dropped. A title that bounces looks wrong. - **Utility.** Use builds only when they help understanding: to reveal steps in order, to show change, or to direct attention. Too many effects teach the audience to ignore all of them. Use one or two transition types for the whole deck. ## 5. Motion accessibility The audience cannot set a reduced-motion preference for your deck, so design for it. - **Prepare a low-motion version** for recordings, shared files, and audiences that are sensitive to motion. Replace moves, zooms, and slides with short cross-fades (Dissolve in Keynote, Fade in PowerPoint and Google Slides). Keep opacity and color changes that help comprehension. - **Do not use full-slide moving backgrounds.** - **Do not use slow looping motion** near one cycle every 5 seconds (0.2 Hz). - **Do not jump suddenly between very dark and very bright slides.** Use a fade, or keep one consistent background. - **Make large objects semi-transparent while they move,** or fade them out before a large move and fade them in after. - **For high-contrast needs,** put text on near-solid backgrounds and give panels a clear border where they meet an image. When text is on a translucent panel, make the panel more opaque. ## 6. Process - **Make a rough working version early.** Click through the real deck with builds on. A working draft shows problems that static mockups do not show, and it sets a quality standard for the final version. - **Design motion and visuals together.** Plan builds when you plan the layout, not after. - **Rehearse with real people in the real context**
--- name: apple-deck-design description: Apple's design principles applied to slide decks in Keynote, PowerPoint, and Google Slides. Use when you build or review a deck: slide layout, hierarchy, typography (tracking, leading, weight), color and translucent panels, builds and transitions, motion accessibility, and the design foundations (purpose, simplicity, consistency, craft) behind Apple-style presentations. --- # Apple Deck Design ## Initial Response When this skill is first invoked without a specific question, respond only with: > I'm ready to help you design Apple-style decks in Keynote, PowerPoint, or Google Slides. My knowledge comes from Apple's WWDC design talks, applied to slides. Do not provide any other information until the user asks a question. This skill uses Apple's WWDC design talks (*Designing Fluid Interfaces*, 2018; *The Details of UI Typography*, 2020; *Principles of Great Design*, 2026) and applies them to slide decks. The main rule: every element on a slide has a purpose, a clear rank in the hierarchy, and a consistent position. Motion shows where content comes from and where it goes. If a build or transition does not help the audience understand, remove it. ## 1. Design foundations Use these principles to make and explain decisions. 1. **Purpose.** Decide what each slide must do before you design it. Decide what not to include. Each slide asks for the audience's attention. Use that attention only where it helps the message. 2. **Simplicity, not minimalism.** Remove what is not necessary so the main point is clear. A slide that hides important context looks minimal but is not simple. Sometimes added context makes a slide simpler, for example a label on a chart line instead of a separate legend. Show the main point first. Put detail in the appendix or in speaker notes. 3. **Clarity through hierarchy.** Use order, size, weight, spacing, and contrast so the most important item is the most visible item. Use one main point per slide. 4. **Familiarity and consistency.** Elements that look the same must behave the same and appear in the same place. Keep titles, page numbers, logos, and section markers in fixed positions on the master slides. Use visual conventions the audience already knows. Break a convention only if you can show that the new way is better, and test it. 5. **Flexibility.** Design for the room and the screen. Text must be readable from the back of the room, on a laptop screen, on a video call, and in a shared PDF. Projectors reduce contrast, so check contrast on the real equipment. Design for the full range of abilities: do not use color as the only signal. 6. **Craft.** Every spacing, alignment, and timing value is a deliberate choice that you can explain. Use a grid. Align objects precisely. Misaligned objects, inconsistent margins, and mixed font styles look careless and reduce trust. 7. **Delight.** Delight is the result of the other six principles. It is not decoration that you add at the end. Decide the emotion you want the audience to feel (calm, confident, excited) and support it in every decision. Tactical rules that support these principles: - **Wayfinding.** The audience must always know: Where are we? What comes next? How much is left? Use agenda slides, section dividers, and a consistent section or progress marker. - **Grouping and mapping.** Proximity shows a relationship. Put a label next to the item it describes. Arrange items in the same order as the process or data they show. If a chart needs a long explanation, its mapping is weak. - **Specific titles.** Write slide titles that state the point ("Costs fell 20% after launch"), not a general topic ("Costs"). Specific titles help the audience predict what the slide shows. ## 2. Typography - **Tracking changes with size.** Never use one character spacing value for all sizes. Large display text needs negative tracking, because letters look too far apart as they get larger. Small text needs zero or slightly positive tracking. - Keynote: Character Spacing is in percent. Start at about -2% for large titles. - PowerPoint: Character Spacing is in points. -2% of the font size is a good start (for a 60 pt title, about -1.2 pt). - Google Slides has no tracking control. Choose a font with good default spacing at large sizes. - **Leading changes inversely with size.** Use tight line spacing on large titles (about 1.05 lines) and looser line spacing on body text (about 1.3 to 1.5 lines). Increase it for scripts with tall ascenders and descenders. Decrease it for dense tables and data slides. - **Build hierarchy with weight, size, and leading together,** not with size only. Use weight for emphasis. It makes text more visible without using more space. - **Use one minimum body size for the whole deck.** If text does not fit at that size, cut text or split the slide. - **Default to a system font before a custom font.** System fonts have tuned spacing and legibility. Use a custom font only for a clear reason, such as brand rules. If the deck moves between Mac and Windows, or between apps, use a font that all systems have, or embed the font, so the layout does not change. ## 3. Color, panels, and depth - **Use translucent panels to put text over images.** The panel keeps the image visible and gives the text a stable background. Use a shape with a semi-transparent fill. For a frosted look, put a blurred copy of the image behind the text area and crop it to the panel shape. - **Panel weight shows hierarchy.** Darker, heavier panels separate structural areas (sidebars, section bands). Lighter panels bring attention to key items. - **Do not put a light translucent panel on another light translucent panel.** The text becomes hard to read. - **Larger panels look thicker.** Give large panels more blur and a deeper shadow than small labels. Use more shadow over busy images and less shadow over plain backgrounds. - **Make text on translucent panels easy to read.** Use high contrast, a slightly heavier weight, and a small increase in tracking. Do not use flat gray text. Put strong color on solid shapes, not on translucent layers. - **Dim to focus.** To focus on one item, dim the other items (lower opacity or gray) and keep the focus item at full contrast. When a callout must hold all attention, put a dark overlay behind it. ## 4. Builds and transitions - **Spatial consistency.** Content leaves the same way it came in. If a panel moves in from the right, it leaves to the right. Content that enters from the right and leaves from the bottom confuses the audience. - **Anchor motion to its source.** A detail callout grows from the item it describes, not from the center of the slide. A zoomed view starts from the area it enlarges. - **Continuity between slides.** When the same object appears on two slides, use Magic Move (Keynote) or Morph (PowerPoint). The audience then sees one object change, not two different objects. Keep the object the same on both slides so the app can match it. - **Show the direction.** Motion during a build must show where the content is going. A chart bar grows in the direction of its value. Process steps appear in reading order. - **Mirror the easing.** When a build reverses an earlier build, use the opposite direction and the same timing, so the return path matches the first path. - **Default to smooth motion with no bounce** (ease in-out, short duration). Use bounce or elastic effects only when the object must look physically thrown or dropped. A title that bounces looks wrong. - **Utility.** Use builds only when they help understanding: to reveal steps in order, to show change, or to direct attention. Too many effects teach the audience to ignore all of them. Use one or two transition types for the whole deck. ## 5. Motion accessibility The audience cannot set a reduced-motion preference for your deck, so design for it. - **Prepare a low-motion version** for recordings, shared files, and audiences that are sensitive to motion. Replace moves, zooms, and slides with short cross-fades (Dissolve in Keynote, Fade in PowerPoint and Google Slides). Keep opacity and color changes that help comprehension. - **Do not use full-slide moving backgrounds.** - **Do not use slow looping motion** near one cycle every 5 seconds (0.2 Hz). - **Do not jump suddenly between very dark and very bright slides.** Use a fade, or keep one consistent background. - **Make large objects semi-transparent while they move,** or fade them out before a large move and fade them in after. - **For high-contrast needs,** put text on near-solid backgrounds and give panels a clear border where they meet an image. When text is on a translucent panel, make the panel more opaque. ## 6. Process - **Make a rough working version early.** Click through the real deck with builds on. A working draft shows problems that static mockups do not show, and it sets a quality standard for the final version. - **Design motion and visuals together.** Plan builds when you plan the layout, not after. - **Rehearse with real people in the real context** (room, screen, video call). Watch the builds again later with fresh eyes. Step through them slowly to find problems you cannot see at full speed. ## Quick reference | Need | Technique | Value | | --- | --- | --- | | Large title tracking | Negative character spacing | About -2% (Keynote); about -1.2 pt at 60 pt (PowerPoint) | | Body tracking | Zero or slightly positive | 0, slightly positive for small text | | Title leading | Tight | About 1.05 lines | | Body leading | Comfortable | About 1.3 to 1.5 lines | | Emphasis | Weight, not only size | Heavier weight | | Text over images | Translucent or frosted panel | High-contrast text, slightly heavier | | Focus on one item | Dim the other items | Lower opacity on other items | | Same object on two slides | Magic Move or Morph | Same object on both slides | | Enter and exit | Same path | In from right, out to right | | Callouts | Grow from their source | Origin at the item | | Default motion | Smooth, no bounce | Ease in-out, short | | Bounce | Only for physical motion | Thrown or dropped objects | | Low-motion version | Cross-fade | Dissolve or Fade | | Slide titles | State the point | "Costs fell 20%", not "Costs" |
Copy prompt
--- name: apple-deck-design description: Apple's design principles applied to slide decks in Keynote, PowerPoint, and Google Slides. Use when you build or review a deck: slide layout, hierarchy, typography (tracking, leading, weight), color and translucent panels, builds and transitions, motion accessibility, and the design foundations (purpose, simplicity, consistency, craft) behind Apple-style presentations. --- # Apple Deck Design ## Initial Response When this skill is first invoked without a specific question, respond only with: > I'm ready to help you design Apple-style decks in Keynote, PowerPoint, or Google Slides. My knowledge comes from Apple's WWDC design talks, applied to slides. Do not provide any other information until the user asks a question. This skill uses Apple's WWDC design talks (*Designing Fluid Interfaces*, 2018; *The Details of UI Typography*, 2020; *Principles of Great Design*, 2026) and applies them to slide decks. The main rule: every element on a slide has a purpose, a clear rank in the hierarchy, and a consistent position. Motion shows where content comes from and where it goes. If a build or transition does not help the audience understand, remove it. ## 1. Design foundations Use these principles to make and explain decisions. 1. **Purpose.** Decide what each slide must do before you design it. Decide what not to include. Each slide asks for the audience's attention. Use that attention only where it helps the message. 2. **Simplicity, not minimalism.** Remove what is not necessary so the main point is clear. A slide that hides important context looks minimal but is not simple. Sometimes added context makes a slide simpler, for example a label on a chart line instead of a separate legend. Show the main point first. Put detail in the appendix or in speaker notes. 3. **Clarity through hierarchy.** Use order, size, weight, spacing, and contrast so the most important item is the most visible item. Use one main point per slide. 4. **Familiarity and consistency.** Elements that look the same must behave the same and appear in the same place. Keep titles, page numbers, logos, and section markers in fixed positions on the master slides. Use visual conventions the audience already knows. Break a convention only if you can show that the new way is better, and test it. 5. **Flexibility.** Design for the room and the screen. Text must be readable from the back of the room, on a laptop screen, on a video call, and in a shared PDF. Projectors reduce contrast, so check contrast on the real equipment. Design for the full range of abilities: do not use color as the only signal. 6. **Craft.** Every spacing, alignment, and timing value is a deliberate choice that you can explain. Use a grid. Align objects precisely. Misaligned objects, inconsistent margins, and mixed font styles look careless and reduce trust. 7. **Delight.** Delight is the result of the other six principles. It is not decoration that you add at the end. Decide the emotion you want the audience to feel (calm, confident, excited) and support it in every decision. Tactical rules that support these principles: - **Wayfinding.** The audience must always know: Where are we? What comes next? How much is left? Use agenda slides, section dividers, and a consistent section or progress marker. - **Grouping and mapping.** Proximity shows a relationship. Put a label next to the item it describes. Arrange items in the same order as the process or data they show. If a chart needs a long explanation, its mapping is weak. - **Specific titles.** Write slide titles that state the point ("Costs fell 20% after launch"), not a general topic ("Costs"). Specific titles help the audience predict what the slide shows. ## 2. Typography - **Tracking changes with size.** Never use one character spacing value for all sizes. Large display text needs negative tracking, because letters look too far apart as they get larger. Small text needs zero or slightly positive tracking. - Keynote: Character Spacing is in percent. Start at about -2% for large titles. - PowerPoint: Character Spacing is in points. -2% of the font size is a good start (for a 60 pt title, about -1.2 pt). - Google Slides has no tracking control. Choose a font with good default spacing at large sizes. - **Leading changes inversely with size.** Use tight line spacing on large titles (about 1.05 lines) and looser line spacing on body text (about 1.3 to 1.5 lines). Increase it for scripts with tall ascenders and descenders. Decrease it for dense tables and data slides. - **Build hierarchy with weight, size, and leading together,** not with size only. Use weight for emphasis. It makes text more visible without using more space. - **Use one minimum body size for the whole deck.** If text does not fit at that size, cut text or split the slide. - **Default to a system font before a custom font.** System fonts have tuned spacing and legibility. Use a custom font only for a clear reason, such as brand rules. If the deck moves between Mac and Windows, or between apps, use a font that all systems have, or embed the font, so the layout does not change. ## 3. Color, panels, and depth - **Use translucent panels to put text over images.** The panel keeps the image visible and gives the text a stable background. Use a shape with a semi-transparent fill. For a frosted look, put a blurred copy of the image behind the text area and crop it to the panel shape. - **Panel weight shows hierarchy.** Darker, heavier panels separate structural areas (sidebars, section bands). Lighter panels bring attention to key items. - **Do not put a light translucent panel on another light translucent panel.** The text becomes hard to read. - **Larger panels look thicker.** Give large panels more blur and a deeper shadow than small labels. Use more shadow over busy images and less shadow over plain backgrounds. - **Make text on translucent panels easy to read.** Use high contrast, a slightly heavier weight, and a small increase in tracking. Do not use flat gray text. Put strong color on solid shapes, not on translucent layers. - **Dim to focus.** To focus on one item, dim the other items (lower opacity or gray) and keep the focus item at full contrast. When a callout must hold all attention, put a dark overlay behind it. ## 4. Builds and transitions - **Spatial consistency.** Content leaves the same way it came in. If a panel moves in from the right, it leaves to the right. Content that enters from the right and leaves from the bottom confuses the audience. - **Anchor motion to its source.** A detail callout grows from the item it describes, not from the center of the slide. A zoomed view starts from the area it enlarges. - **Continuity between slides.** When the same object appears on two slides, use Magic Move (Keynote) or Morph (PowerPoint). The audience then sees one object change, not two different objects. Keep the object the same on both slides so the app can match it. - **Show the direction.** Motion during a build must show where the content is going. A chart bar grows in the direction of its value. Process steps appear in reading order. - **Mirror the easing.** When a build reverses an earlier build, use the opposite direction and the same timing, so the return path matches the first path. - **Default to smooth motion with no bounce** (ease in-out, short duration). Use bounce or elastic effects only when the object must look physically thrown or dropped. A title that bounces looks wrong. - **Utility.** Use builds only when they help understanding: to reveal steps in order, to show change, or to direct attention. Too many effects teach the audience to ignore all of them. Use one or two transition types for the whole deck. ## 5. Motion accessibility The audience cannot set a reduced-motion preference for your deck, so design for it. - **Prepare a low-motion version** for recordings, shared files, and audiences that are sensitive to motion. Replace moves, zooms, and slides with short cross-fades (Dissolve in Keynote, Fade in PowerPoint and Google Slides). Keep opacity and color changes that help comprehension. - **Do not use full-slide moving backgrounds.** - **Do not use slow looping motion** near one cycle every 5 seconds (0.2 Hz). - **Do not jump suddenly between very dark and very bright slides.** Use a fade, or keep one consistent background. - **Make large objects semi-transparent while they move,** or fade them out before a large move and fade them in after. - **For high-contrast needs,** put text on near-solid backgrounds and give panels a clear border where they meet an image. When text is on a translucent panel, make the panel more opaque. ## 6. Process - **Make a rough working version early.** Click through the real deck with builds on. A working draft shows problems that static mockups do not show, and it sets a quality standard for the final version. - **Design motion and visuals together.** Plan builds when you plan the layout, not after. - **Rehearse with real people in the real context**
--- name: apple-deck-design description: Apple's design principles applied to slide decks in Keynote, PowerPoint, and Google Slides. Use when you build or review a deck: slide layout, hierarchy, typography (tracking, leading, weight), color and translucent panels, builds and transitions, motion accessibility, and the design foundations (purpose, simplicity, consistency, craft) behind Apple-style presentations. --- # Apple Deck Design ## Initial Response When this skill is first invoked without a specific question, respond only with: > I'm ready to help you design Apple-style decks in Keynote, PowerPoint, or Google Slides. My knowledge comes from Apple's WWDC design talks, applied to slides. Do not provide any other information until the user asks a question. This skill uses Apple's WWDC design talks (*Designing Fluid Interfaces*, 2018; *The Details of UI Typography*, 2020; *Principles of Great Design*, 2026) and applies them to slide decks. The main rule: every element on a slide has a purpose, a clear rank in the hierarchy, and a consistent position. Motion shows where content comes from and where it goes. If a build or transition does not help the audience understand, remove it. ## 1. Design foundations Use these principles to make and explain decisions. 1. **Purpose.** Decide what each slide must do before you design it. Decide what not to include. Each slide asks for the audience's attention. Use that attention only where it helps the message. 2. **Simplicity, not minimalism.** Remove what is not necessary so the main point is clear. A slide that hides important context looks minimal but is not simple. Sometimes added context makes a slide simpler, for example a label on a chart line instead of a separate legend. Show the main point first. Put detail in the appendix or in speaker notes. 3. **Clarity through hierarchy.** Use order, size, weight, spacing, and contrast so the most important item is the most visible item. Use one main point per slide. 4. **Familiarity and consistency.** Elements that look the same must behave the same and appear in the same place. Keep titles, page numbers, logos, and section markers in fixed positions on the master slides. Use visual conventions the audience already knows. Break a convention only if you can show that the new way is better, and test it. 5. **Flexibility.** Design for the room and the screen. Text must be readable from the back of the room, on a laptop screen, on a video call, and in a shared PDF. Projectors reduce contrast, so check contrast on the real equipment. Design for the full range of abilities: do not use color as the only signal. 6. **Craft.** Every spacing, alignment, and timing value is a deliberate choice that you can explain. Use a grid. Align objects precisely. Misaligned objects, inconsistent margins, and mixed font styles look careless and reduce trust. 7. **Delight.** Delight is the result of the other six principles. It is not decoration that you add at the end. Decide the emotion you want the audience to feel (calm, confident, excited) and support it in every decision. Tactical rules that support these principles: - **Wayfinding.** The audience must always know: Where are we? What comes next? How much is left? Use agenda slides, section dividers, and a consistent section or progress marker. - **Grouping and mapping.** Proximity shows a relationship. Put a label next to the item it describes. Arrange items in the same order as the process or data they show. If a chart needs a long explanation, its mapping is weak. - **Specific titles.** Write slide titles that state the point ("Costs fell 20% after launch"), not a general topic ("Costs"). Specific titles help the audience predict what the slide shows. ## 2. Typography - **Tracking changes with size.** Never use one character spacing value for all sizes. Large display text needs negative tracking, because letters look too far apart as they get larger. Small text needs zero or slightly positive tracking. - Keynote: Character Spacing is in percent. Start at about -2% for large titles. - PowerPoint: Character Spacing is in points. -2% of the font size is a good start (for a 60 pt title, about -1.2 pt). - Google Slides has no tracking control. Choose a font with good default spacing at large sizes. - **Leading changes inversely with size.** Use tight line spacing on large titles (about 1.05 lines) and looser line spacing on body text (about 1.3 to 1.5 lines). Increase it for scripts with tall ascenders and descenders. Decrease it for dense tables and data slides. - **Build hierarchy with weight, size, and leading together,** not with size only. Use weight for emphasis. It makes text more visible without using more space. - **Use one minimum body size for the whole deck.** If text does not fit at that size, cut text or split the slide. - **Default to a system font before a custom font.** System fonts have tuned spacing and legibility. Use a custom font only for a clear reason, such as brand rules. If the deck moves between Mac and Windows, or between apps, use a font that all systems have, or embed the font, so the layout does not change. ## 3. Color, panels, and depth - **Use translucent panels to put text over images.** The panel keeps the image visible and gives the text a stable background. Use a shape with a semi-transparent fill. For a frosted look, put a blurred copy of the image behind the text area and crop it to the panel shape. - **Panel weight shows hierarchy.** Darker, heavier panels separate structural areas (sidebars, section bands). Lighter panels bring attention to key items. - **Do not put a light translucent panel on another light translucent panel.** The text becomes hard to read. - **Larger panels look thicker.** Give large panels more blur and a deeper shadow than small labels. Use more shadow over busy images and less shadow over plain backgrounds. - **Make text on translucent panels easy to read.** Use high contrast, a slightly heavier weight, and a small increase in tracking. Do not use flat gray text. Put strong color on solid shapes, not on translucent layers. - **Dim to focus.** To focus on one item, dim the other items (lower opacity or gray) and keep the focus item at full contrast. When a callout must hold all attention, put a dark overlay behind it. ## 4. Builds and transitions - **Spatial consistency.** Content leaves the same way it came in. If a panel moves in from the right, it leaves to the right. Content that enters from the right and leaves from the bottom confuses the audience. - **Anchor motion to its source.** A detail callout grows from the item it describes, not from the center of the slide. A zoomed view starts from the area it enlarges. - **Continuity between slides.** When the same object appears on two slides, use Magic Move (Keynote) or Morph (PowerPoint). The audience then sees one object change, not two different objects. Keep the object the same on both slides so the app can match it. - **Show the direction.** Motion during a build must show where the content is going. A chart bar grows in the direction of its value. Process steps appear in reading order. - **Mirror the easing.** When a build reverses an earlier build, use the opposite direction and the same timing, so the return path matches the first path. - **Default to smooth motion with no bounce** (ease in-out, short duration). Use bounce or elastic effects only when the object must look physically thrown or dropped. A title that bounces looks wrong. - **Utility.** Use builds only when they help understanding: to reveal steps in order, to show change, or to direct attention. Too many effects teach the audience to ignore all of them. Use one or two transition types for the whole deck. ## 5. Motion accessibility The audience cannot set a reduced-motion preference for your deck, so design for it. - **Prepare a low-motion version** for recordings, shared files, and audiences that are sensitive to motion. Replace moves, zooms, and slides with short cross-fades (Dissolve in Keynote, Fade in PowerPoint and Google Slides). Keep opacity and color changes that help comprehension. - **Do not use full-slide moving backgrounds.** - **Do not use slow looping motion** near one cycle every 5 seconds (0.2 Hz). - **Do not jump suddenly between very dark and very bright slides.** Use a fade, or keep one consistent background. - **Make large objects semi-transparent while they move,** or fade them out before a large move and fade them in after. - **For high-contrast needs,** put text on near-solid backgrounds and give panels a clear border where they meet an image. When text is on a translucent panel, make the panel more opaque. ## 6. Process - **Make a rough working version early.** Click through the real deck with builds on. A working draft shows problems that static mockups do not show, and it sets a quality standard for the final version. - **Design motion and visuals together.** Plan builds when you plan the layout, not after. - **Rehearse with real people in the real context** (room, screen, video call). Watch the builds again later with fresh eyes. Step through them slowly to find problems you cannot see at full speed. ## Quick reference | Need | Technique | Value | | --- | --- | --- | | Large title tracking | Negative character spacing | About -2% (Keynote); about -1.2 pt at 60 pt (PowerPoint) | | Body tracking | Zero or slightly positive | 0, slightly positive for small text | | Title leading | Tight | About 1.05 lines | | Body leading | Comfortable | About 1.3 to 1.5 lines | | Emphasis | Weight, not only size | Heavier weight | | Text over images | Translucent or frosted panel | High-contrast text, slightly heavier | | Focus on one item | Dim the other items | Lower opacity on other items | | Same object on two slides | Magic Move or Morph | Same object on both slides | | Enter and exit | Same path | In from right, out to right | | Callouts | Grow from their source | Origin at the item | | Default motion | Smooth, no bounce | Ease in-out, short | | Bounce | Only for physical motion | Thrown or dropped objects | | Low-motion version | Cross-fade | Dissolve or Fade | | Slide titles | State the point | "Costs fell 20%", not "Costs" |
Copy prompt
--- name: apple-deck-design description: Apple's design principles applied to slide decks in Keynote, PowerPoint, and Google Slides. Use when you build or review a deck: slide layout, hierarchy, typography (tracking, leading, weight), color and translucent panels, builds and transitions, motion accessibility, and the design foundations (purpose, simplicity, consistency, craft) behind Apple-style presentations. --- # Apple Deck Design ## Initial Response When this skill is first invoked without a specific question, respond only with: > I'm ready to help you design Apple-style decks in Keynote, PowerPoint, or Google Slides. My knowledge comes from Apple's WWDC design talks, applied to slides. Do not provide any other information until the user asks a question. This skill uses Apple's WWDC design talks (*Designing Fluid Interfaces*, 2018; *The Details of UI Typography*, 2020; *Principles of Great Design*, 2026) and applies them to slide decks. The main rule: every element on a slide has a purpose, a clear rank in the hierarchy, and a consistent position. Motion shows where content comes from and where it goes. If a build or transition does not help the audience understand, remove it. ## 1. Design foundations Use these principles to make and explain decisions. 1. **Purpose.** Decide what each slide must do before you design it. Decide what not to include. Each slide asks for the audience's attention. Use that attention only where it helps the message. 2. **Simplicity, not minimalism.** Remove what is not necessary so the main point is clear. A slide that hides important context looks minimal but is not simple. Sometimes added context makes a slide simpler, for example a label on a chart line instead of a separate legend. Show the main point first. Put detail in the appendix or in speaker notes. 3. **Clarity through hierarchy.** Use order, size, weight, spacing, and contrast so the most important item is the most visible item. Use one main point per slide. 4. **Familiarity and consistency.** Elements that look the same must behave the same and appear in the same place. Keep titles, page numbers, logos, and section markers in fixed positions on the master slides. Use visual conventions the audience already knows. Break a convention only if you can show that the new way is better, and test it. 5. **Flexibility.** Design for the room and the screen. Text must be readable from the back of the room, on a laptop screen, on a video call, and in a shared PDF. Projectors reduce contrast, so check contrast on the real equipment. Design for the full range of abilities: do not use color as the only signal. 6. **Craft.** Every spacing, alignment, and timing value is a deliberate choice that you can explain. Use a grid. Align objects precisely. Misaligned objects, inconsistent margins, and mixed font styles look careless and reduce trust. 7. **Delight.** Delight is the result of the other six principles. It is not decoration that you add at the end. Decide the emotion you want the audience to feel (calm, confident, excited) and support it in every decision. Tactical rules that support these principles: - **Wayfinding.** The audience must always know: Where are we? What comes next? How much is left? Use agenda slides, section dividers, and a consistent section or progress marker. - **Grouping and mapping.** Proximity shows a relationship. Put a label next to the item it describes. Arrange items in the same order as the process or data they show. If a chart needs a long explanation, its mapping is weak. - **Specific titles.** Write slide titles that state the point ("Costs fell 20% after launch"), not a general topic ("Costs"). Specific titles help the audience predict what the slide shows. ## 2. Typography - **Tracking changes with size.** Never use one character spacing value for all sizes. Large display text needs negative tracking, because letters look too far apart as they get larger. Small text needs zero or slightly positive tracking. - Keynote: Character Spacing is in percent. Start at about -2% for large titles. - PowerPoint: Character Spacing is in points. -2% of the font size is a good start (for a 60 pt title, about -1.2 pt). - Google Slides has no tracking control. Choose a font with good default spacing at large sizes. - **Leading changes inversely with size.** Use tight line spacing on large titles (about 1.05 lines) and looser line spacing on body text (about 1.3 to 1.5 lines). Increase it for scripts with tall ascenders and descenders. Decrease it for dense tables and data slides. - **Build hierarchy with weight, size, and leading together,** not with size only. Use weight for emphasis. It makes text more visible without using more space. - **Use one minimum body size for the whole deck.** If text does not fit at that size, cut text or split the slide. - **Default to a system font before a custom font.** System fonts have tuned spacing and legibility. Use a custom font only for a clear reason, such as brand rules. If the deck moves between Mac and Windows, or between apps, use a font that all systems have, or embed the font, so the layout does not change. ## 3. Color, panels, and depth - **Use translucent panels to put text over images.** The panel keeps the image visible and gives the text a stable background. Use a shape with a semi-transparent fill. For a frosted look, put a blurred copy of the image behind the text area and crop it to the panel shape. - **Panel weight shows hierarchy.** Darker, heavier panels separate structural areas (sidebars, section bands). Lighter panels bring attention to key items. - **Do not put a light translucent panel on another light translucent panel.** The text becomes hard to read. - **Larger panels look thicker.** Give large panels more blur and a deeper shadow than small labels. Use more shadow over busy images and less shadow over plain backgrounds. - **Make text on translucent panels easy to read.** Use high contrast, a slightly heavier weight, and a small increase in tracking. Do not use flat gray text. Put strong color on solid shapes, not on translucent layers. - **Dim to focus.** To focus on one item, dim the other items (lower opacity or gray) and keep the focus item at full contrast. When a callout must hold all attention, put a dark overlay behind it. ## 4. Builds and transitions - **Spatial consistency.** Content leaves the same way it came in. If a panel moves in from the right, it leaves to the right. Content that enters from the right and leaves from the bottom confuses the audience. - **Anchor motion to its source.** A detail callout grows from the item it describes, not from the center of the slide. A zoomed view starts from the area it enlarges. - **Continuity between slides.** When the same object appears on two slides, use Magic Move (Keynote) or Morph (PowerPoint). The audience then sees one object change, not two different objects. Keep the object the same on both slides so the app can match it. - **Show the direction.** Motion during a build must show where the content is going. A chart bar grows in the direction of its value. Process steps appear in reading order. - **Mirror the easing.** When a build reverses an earlier build, use the opposite direction and the same timing, so the return path matches the first path. - **Default to smooth motion with no bounce** (ease in-out, short duration). Use bounce or elastic effects only when the object must look physically thrown or dropped. A title that bounces looks wrong. - **Utility.** Use builds only when they help understanding: to reveal steps in order, to show change, or to direct attention. Too many effects teach the audience to ignore all of them. Use one or two transition types for the whole deck. ## 5. Motion accessibility The audience cannot set a reduced-motion preference for your deck, so design for it. - **Prepare a low-motion version** for recordings, shared files, and audiences that are sensitive to motion. Replace moves, zooms, and slides with short cross-fades (Dissolve in Keynote, Fade in PowerPoint and Google Slides). Keep opacity and color changes that help comprehension. - **Do not use full-slide moving backgrounds.** - **Do not use slow looping motion** near one cycle every 5 seconds (0.2 Hz). - **Do not jump suddenly between very dark and very bright slides.** Use a fade, or keep one consistent background. - **Make large objects semi-transparent while they move,** or fade them out before a large move and fade them in after. - **For high-contrast needs,** put text on near-solid backgrounds and give panels a clear border where they meet an image. When text is on a translucent panel, make the panel more opaque. ## 6. Process - **Make a rough working version early.** Click through the real deck with builds on. A working draft shows problems that static mockups do not show, and it sets a quality standard for the final version. - **Design motion and visuals together.** Plan builds when you plan the layout, not after. - **Rehearse with real people in the real context**
--- name: apple-deck-design description: Apple's design principles applied to slide decks in Keynote, PowerPoint, and Google Slides. Use when you build or review a deck: slide layout, hierarchy, typography (tracking, leading, weight), color and translucent panels, builds and transitions, motion accessibility, and the design foundations (purpose, simplicity, consistency, craft) behind Apple-style presentations. --- # Apple Deck Design ## Initial Response When this skill is first invoked without a specific question, respond only with: > I'm ready to help you design Apple-style decks in Keynote, PowerPoint, or Google Slides. My knowledge comes from Apple's WWDC design talks, applied to slides. Do not provide any other information until the user asks a question. This skill uses Apple's WWDC design talks (*Designing Fluid Interfaces*, 2018; *The Details of UI Typography*, 2020; *Principles of Great Design*, 2026) and applies them to slide decks. The main rule: every element on a slide has a purpose, a clear rank in the hierarchy, and a consistent position. Motion shows where content comes from and where it goes. If a build or transition does not help the audience understand, remove it. ## 1. Design foundations Use these principles to make and explain decisions. 1. **Purpose.** Decide what each slide must do before you design it. Decide what not to include. Each slide asks for the audience's attention. Use that attention only where it helps the message. 2. **Simplicity, not minimalism.** Remove what is not necessary so the main point is clear. A slide that hides important context looks minimal but is not simple. Sometimes added context makes a slide simpler, for example a label on a chart line instead of a separate legend. Show the main point first. Put detail in the appendix or in speaker notes. 3. **Clarity through hierarchy.** Use order, size, weight, spacing, and contrast so the most important item is the most visible item. Use one main point per slide. 4. **Familiarity and consistency.** Elements that look the same must behave the same and appear in the same place. Keep titles, page numbers, logos, and section markers in fixed positions on the master slides. Use visual conventions the audience already knows. Break a convention only if you can show that the new way is better, and test it. 5. **Flexibility.** Design for the room and the screen. Text must be readable from the back of the room, on a laptop screen, on a video call, and in a shared PDF. Projectors reduce contrast, so check contrast on the real equipment. Design for the full range of abilities: do not use color as the only signal. 6. **Craft.** Every spacing, alignment, and timing value is a deliberate choice that you can explain. Use a grid. Align objects precisely. Misaligned objects, inconsistent margins, and mixed font styles look careless and reduce trust. 7. **Delight.** Delight is the result of the other six principles. It is not decoration that you add at the end. Decide the emotion you want the audience to feel (calm, confident, excited) and support it in every decision. Tactical rules that support these principles: - **Wayfinding.** The audience must always know: Where are we? What comes next? How much is left? Use agenda slides, section dividers, and a consistent section or progress marker. - **Grouping and mapping.** Proximity shows a relationship. Put a label next to the item it describes. Arrange items in the same order as the process or data they show. If a chart needs a long explanation, its mapping is weak. - **Specific titles.** Write slide titles that state the point ("Costs fell 20% after launch"), not a general topic ("Costs"). Specific titles help the audience predict what the slide shows. ## 2. Typography - **Tracking changes with size.** Never use one character spacing value for all sizes. Large display text needs negative tracking, because letters look too far apart as they get larger. Small text needs zero or slightly positive tracking. - Keynote: Character Spacing is in percent. Start at about -2% for large titles. - PowerPoint: Character Spacing is in points. -2% of the font size is a good start (for a 60 pt title, about -1.2 pt). - Google Slides has no tracking control. Choose a font with good default spacing at large sizes. - **Leading changes inversely with size.** Use tight line spacing on large titles (about 1.05 lines) and looser line spacing on body text (about 1.3 to 1.5 lines). Increase it for scripts with tall ascenders and descenders. Decrease it for dense tables and data slides. - **Build hierarchy with weight, size, and leading together,** not with size only. Use weight for emphasis. It makes text more visible without using more space. - **Use one minimum body size for the whole deck.** If text does not fit at that size, cut text or split the slide. - **Default to a system font before a custom font.** System fonts have tuned spacing and legibility. Use a custom font only for a clear reason, such as brand rules. If the deck moves between Mac and Windows, or between apps, use a font that all systems have, or embed the font, so the layout does not change. ## 3. Color, panels, and depth - **Use translucent panels to put text over images.** The panel keeps the image visible and gives the text a stable background. Use a shape with a semi-transparent fill. For a frosted look, put a blurred copy of the image behind the text area and crop it to the panel shape. - **Panel weight shows hierarchy.** Darker, heavier panels separate structural areas (sidebars, section bands). Lighter panels bring attention to key items. - **Do not put a light translucent panel on another light translucent panel.** The text becomes hard to read. - **Larger panels look thicker.** Give large panels more blur and a deeper shadow than small labels. Use more shadow over busy images and less shadow over plain backgrounds. - **Make text on translucent panels easy to read.** Use high contrast, a slightly heavier weight, and a small increase in tracking. Do not use flat gray text. Put strong color on solid shapes, not on translucent layers. - **Dim to focus.** To focus on one item, dim the other items (lower opacity or gray) and keep the focus item at full contrast. When a callout must hold all attention, put a dark overlay behind it. ## 4. Builds and transitions - **Spatial consistency.** Content leaves the same way it came in. If a panel moves in from the right, it leaves to the right. Content that enters from the right and leaves from the bottom confuses the audience. - **Anchor motion to its source.** A detail callout grows from the item it describes, not from the center of the slide. A zoomed view starts from the area it enlarges. - **Continuity between slides.** When the same object appears on two slides, use Magic Move (Keynote) or Morph (PowerPoint). The audience then sees one object change, not two different objects. Keep the object the same on both slides so the app can match it. - **Show the direction.** Motion during a build must show where the content is going. A chart bar grows in the direction of its value. Process steps appear in reading order. - **Mirror the easing.** When a build reverses an earlier build, use the opposite direction and the same timing, so the return path matches the first path. - **Default to smooth motion with no bounce** (ease in-out, short duration). Use bounce or elastic effects only when the object must look physically thrown or dropped. A title that bounces looks wrong. - **Utility.** Use builds only when they help understanding: to reveal steps in order, to show change, or to direct attention. Too many effects teach the audience to ignore all of them. Use one or two transition types for the whole deck. ## 5. Motion accessibility The audience cannot set a reduced-motion preference for your deck, so design for it. - **Prepare a low-motion version** for recordings, shared files, and audiences that are sensitive to motion. Replace moves, zooms, and slides with short cross-fades (Dissolve in Keynote, Fade in PowerPoint and Google Slides). Keep opacity and color changes that help comprehension. - **Do not use full-slide moving backgrounds.** - **Do not use slow looping motion** near one cycle every 5 seconds (0.2 Hz). - **Do not jump suddenly between very dark and very bright slides.** Use a fade, or keep one consistent background. - **Make large objects semi-transparent while they move,** or fade them out before a large move and fade them in after. - **For high-contrast needs,** put text on near-solid backgrounds and give panels a clear border where they meet an image. When text is on a translucent panel, make the panel more opaque. ## 6. Process - **Make a rough working version early.** Click through the real deck with builds on. A working draft shows problems that static mockups do not show, and it sets a quality standard for the final version. - **Design motion and visuals together.** Plan builds when you plan the layout, not after. - **Rehearse with real people in the real context** (room, screen, video call). Watch the builds again later with fresh eyes. Step through them slowly to find problems you cannot see at full speed. ## Quick reference | Need | Technique | Value | | --- | --- | --- | | Large title tracking | Negative character spacing | About -2% (Keynote); about -1.2 pt at 60 pt (PowerPoint) | | Body tracking | Zero or slightly positive | 0, slightly positive for small text | | Title leading | Tight | About 1.05 lines | | Body leading | Comfortable | About 1.3 to 1.5 lines | | Emphasis | Weight, not only size | Heavier weight | | Text over images | Translucent or frosted panel | High-contrast text, slightly heavier | | Focus on one item | Dim the other items | Lower opacity on other items | | Same object on two slides | Magic Move or Morph | Same object on both slides | | Enter and exit | Same path | In from right, out to right | | Callouts | Grow from their source | Origin at the item | | Default motion | Smooth, no bounce | Ease in-out, short | | Bounce | Only for physical motion | Thrown or dropped objects | | Low-motion version | Cross-fade | Dissolve or Fade | | Slide titles | State the point | "Costs fell 20%", not "Costs" |
Caution: The two skills do not replace each other. The writing file does not fix the design. The design skill does not fix the writing. Install both.
Install both
The file gives you the agent and its skills. Copy the output into your AI tool of choice. Then you are done.
Connect the tools
Install both skills. Claude, Copilot, or ChatGPT will then follow these rules every time with the proper command.
In Copilot, you can upload skills directly into your PowerPoint app.
REMAINING QUESTIONS
Why does my deck look like AI even when I give the AI great references?
References are not enough. The AI still produces the usual patterns: purple gradients, rounded corners, eyebrow stripes, em-dashes, and grouped information. Skills add rules that the AI follows every time.
Does it matter if my deck looks like AI if the strategy is strong?
Yes. You could have the best strategy or narrative. If the deck looks like AI slop, no one will take it seriously.
Why do I need the writing file now?
AI watermarking makes it more important. The anti-AI writing file helps your text avoid the patterns that make writing sound like AI.