- 16 cross-shell utilities converted to sh/bash chezmoi executables: ai c2p cp-appid extract_agents fab gdc gh-sonr-org-migrate ghg-clone ghn gho git-summary launch_omp_livediff_overlay lc-elir mdcp mdp pj (ghg-clone not named ghg: unrelated cargo binary owns that name) - cwd/history helpers stay per-shell: yy c cd clip-last + ghg/ghn/gho cd-wrappers in bash/functions/ and zsh/functions/, loaded by rc files - fish keeps only shell-state functions; converted ones now hit PATH - cp-appid ignore gating moved to .local/bin path - dot_agents/skills: 82 skills materialized from dotstate storage so dot_claude skill symlinks resolve on fresh bootstrap; dotstate profile/symlinks.json released .agents/skills .bashrc .zshrc
1.6 KiB
Before/After Examples
Example 1: Throat-Clearing + Binary Contrast
Before:
"Here's the thing: building products is hard. Not because the technology is complex. Because people are complex. Let that sink in."
After:
"Building products is hard. Technology is manageable. People aren't."
Changes: Removed opener, binary contrast structure, and emphasis crutch. Direct statements.
Example 2: Filler + Unnecessary Reassurance
Before:
"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."
After:
"Teams struggle with alignment. Nobody admits confusion."
Changes: Cut hedging ("most"), removed throat-clearing phrases, deleted permission-granting ending.
Example 3: Business Jargon Stack
Before:
"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."
After:
"Move faster. Your competition is."
Changes: Eliminated jargon entirely. Core message in six words.
Example 4: Dramatic Fragmentation
Before:
"Speed. Quality. Cost. You can only pick two. That's it. That's the tradeoff."
After:
"Speed, quality, cost—pick two."
Changes: Single sentence. No performative emphasis.
Example 5: Rhetorical Setup
Before:
"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."
After:
"The best teams optimize for learning, not productivity."
Changes: Direct claim. No rhetorical scaffolding.