Loading source
Pulling the file list, source metadata, and syntax-aware rendering for this listing.
Files
Skill
Size
Entrypoint
Format
Open file
Syntax-highlighted preview of this file as included in the skill package.
references/examples.md
1# Before/After Examples23## Example 1: Throat-Clearing + Binary Contrast45**Before:**6> "Here's the thing: building products is hard. Not because the technology is complex. Because people are complex. Let that sink in."78**After:**9> "Building products is hard. Technology is manageable. People aren't."1011**Changes:** Removed opener, binary contrast structure, and emphasis crutch. Direct statements.1213---1415## Example 2: Filler + Unnecessary Reassurance1617**Before:**18> "It turns out that most teams struggle with alignment. The uncomfortable truth is that nobody wants to admit they're confused. And that's okay."1920**After:**21> "Teams struggle with alignment. Nobody admits confusion."2223**Changes:** Cut hedging ("most"), removed throat-clearing phrases, deleted permission-granting ending.2425---2627## Example 3: Business Jargon Stack2829**Before:**30> "In today's fast-paced landscape, we need to lean into discomfort and navigate uncertainty with clarity. This matters because your competition isn't waiting."3132**After:**33> "Move faster. Your competition is."3435**Changes:** Eliminated jargon entirely. Core message in six words.3637---3839## Example 4: Dramatic Fragmentation4041**Before:**42> "Speed. Quality. Cost. You can only pick two. That's it. That's the tradeoff."4344**After:**45> "Speed, quality, cost—pick two."4647**Changes:** Single sentence. No performative emphasis.4849---5051## Example 5: Rhetorical Setup5253**Before:**54> "What if I told you that the best teams don't optimize for productivity? Here's what I mean: they optimize for learning. Think about it."5556**After:**57> "The best teams optimize for learning, not productivity."5859**Changes:** Direct claim. No rhetorical scaffolding.60