inversion-exercise
Flip core assumptions to reveal hidden constraints and alternative approaches - "what if the opposite were true?"
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install paopp2-dotfiles-inversion-exercise
Repository
Skill path: .claude/skills/problem-solving/inversion-exercise
Flip core assumptions to reveal hidden constraints and alternative approaches - "what if the opposite were true?"
Open repositoryBest for
Primary workflow: Ship Full Stack.
Technical facets: Full Stack.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: paopp2.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install inversion-exercise into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/paopp2/dotfiles before adding inversion-exercise to shared team environments
- Use inversion-exercise for development workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
--- name: Inversion Exercise description: Flip core assumptions to reveal hidden constraints and alternative approaches - "what if the opposite were true?" when_to_use: when stuck on unquestioned assumptions or feeling forced into "the only way" to do something version: 1.1.0 --- # Inversion Exercise ## Overview Flip every assumption and see what still works. Sometimes the opposite reveals the truth. **Core principle:** Inversion exposes hidden assumptions and alternative approaches. ## Quick Reference | Normal Assumption | Inverted | What It Reveals | |-------------------|----------|-----------------| | Cache to reduce latency | Add latency to enable caching | Debouncing patterns | | Pull data when needed | Push data before needed | Prefetching, eager loading | | Handle errors when occur | Make errors impossible | Type systems, contracts | | Build features users want | Remove features users don't need | Simplicity >> addition | | Optimize for common case | Optimize for worst case | Resilience patterns | ## Process 1. **List core assumptions** - What "must" be true? 2. **Invert each systematically** - "What if opposite were true?" 3. **Explore implications** - What would we do differently? 4. **Find valid inversions** - Which actually work somewhere? ## Example **Problem:** Users complain app is slow **Normal approach:** Make everything faster (caching, optimization, CDN) **Inverted:** Make things intentionally slower in some places - Debounce search (add latency → enable better results) - Rate limit requests (add friction → prevent abuse) - Lazy load content (delay → reduce initial load) **Insight:** Strategic slowness can improve UX ## Red Flags You Need This - "There's only one way to do this" - Forcing solution that feels wrong - Can't articulate why approach is necessary - "This is just how it's done" ## Remember - Not all inversions work (test boundaries) - Valid inversions reveal context-dependence - Sometimes opposite is the answer - Question "must be" statements