inversion-exercise

Flip core assumptions to reveal hidden constraints and alternative approaches - "what if the opposite were true?"

⭐1.1kstars🔀227forks📁View on GitHub🕐Updated Dec 30, 2025⬇️2downloads

When & Why to Use This Skill

The Inversion Exercise Claude skill is a strategic problem-solving framework designed to break through cognitive biases and technical stalemates. By systematically flipping core assumptions—asking 'what if the opposite were true?'—this skill helps developers and architects uncover hidden constraints, identify alternative system designs, and discover innovative solutions that traditional forward-thinking approaches often overlook. It is an essential tool for high-level technical decision-making and architectural refactoring.

Use Cases

  • Software Architecture Refactoring: Challenge existing system bottlenecks by inverting performance assumptions to discover more resilient design patterns like prefetching or eager loading.
  • Product Feature Prioritization: Identify 'feature bloat' and simplify product roadmaps by assuming the opposite of common user requests to find the most impactful core functionality.
  • System Reliability Engineering: Shift from reactive error handling to proactive system design by exploring how to make specific failure states impossible through type systems and strict contracts.
  • UX and Performance Optimization: Use 'strategic slowness' (such as debouncing or lazy loading) to improve perceived performance and resource management in complex web applications.
nameInversion Exercise
descriptionFlip core assumptions to reveal hidden constraints and alternative approaches - "what if the opposite were true?"
when_to_usewhen stuck on unquestioned assumptions or feeling forced into "the only way" to do something
version1.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