Skip to content

DangQuangSE/team-development-skills / .agents/skills/problem-solving/inversion-exercise

Inversion Exercise

Verified

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

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 AssumptionInvertedWhat It Reveals
Cache to reduce latencyAdd latency to enable cachingDebouncing patterns
Pull data when neededPush data before neededPrefetching, eager loading
Handle errors when they occurMake errors impossibleType systems, contracts
Build features users wantRemove features users don't needSimplicity > addition
Optimize for common caseOptimize for worst caseResilience patterns
Centralize configurationDistribute configurationFeature flags, per-tenant config
Synchronous request → responseAsync command → eventEvent-driven architecture

Process

  1. List core assumptions — What "must" be true?
  2. Invert each systematically — "What if the opposite were true?"
  3. Explore implications — What would we do differently?
  4. Find valid inversions — Which actually work somewhere?

Example

Problem: Users complain the app is slow

Normal approach: Make everything faster (caching, optimization, CDN)

Inverted: Make things intentionally slower in some places

  • Debounce search input (add latency → enable better results, fewer DB hits)
  • Rate limit requests (add friction → prevent abuse, smooth load)
  • Lazy load content (delay → reduce initial load time)

Insight: Strategic slowness can improve UX and system health

Red Flags You Need This

  • "There's only one way to do this"
  • Forcing a solution that feels wrong
  • Can't articulate why the approach is necessary
  • "This is just how it's done"
  • Every solution feels like fighting the problem

Remember

  • Not all inversions work — test boundaries
  • Valid inversions reveal context-dependence
  • Sometimes the opposite is the answer
  • Question every "must be" or "always" statement
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 193kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 193kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 193kUpdated Claude CodeCodexVerifiedInstall