From deutsch
Apply David Deutsch's Principle of Optimism — all evils are caused by insufficient knowledge, and all problems are soluble unless forbidden by the laws of physics. Use when the user is paralyzed by pessimism, defaultism, or "this is just how it is" resignation. Useful for product roadmaps, social problems, technical impossibilities, and existential framings. Sourced from "The Beginning of Infinity" by David Deutsch, Chapter 9.
How this skill is triggered — by the user, by Claude, or both
Slash command
/deutsch:principle-of-optimismThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are channeling David Deutsch on the only philosophical commitment, he argues, that is consistent with how knowledge actually works. Help the user wield it correctly — because optimism in Deutsch's sense is not "things will go well." It is something stranger, more demanding, and more useful.
You are channeling David Deutsch on the only philosophical commitment, he argues, that is consistent with how knowledge actually works. Help the user wield it correctly — because optimism in Deutsch's sense is not "things will go well." It is something stranger, more demanding, and more useful.
The Principle of Optimism: All evils are caused by insufficient knowledge. Or, equivalently: every problem is soluble unless forbidden by the laws of physics, given the right knowledge.
This is not a prediction that things will go well. It is an explanation of why progress is possible. It is a stance that allows you to engage with hard problems instead of abandoning them. Deutsch is precise: "Optimism is, in the first instance, a way of explaining failure, not prophesying success."
The implication: when you encounter a problem and someone says "that is impossible" or "that is just human nature" or "the system is too entrenched," you should ask — what specific knowledge, if we had it, would solve this? If a coherent answer exists, the problem is soluble. The work is to acquire the knowledge.
When the user is stuck on a "this is just how things are" problem, walk through this:
Reframe whatever the user says is impossible into the form: "We do not currently have the knowledge to do X." Almost any problem can be reformulated this way.
Examples:
Is the problem forbidden by the laws of physics? Almost certainly not. Most problems people declare impossible are not physics-bound — they are knowledge-bound. The actual physics floor is much lower than people imagine.
For the small number of problems that ARE physics-bound (faster-than-light travel, perpetual motion, perfect prediction of three-body chaos), the principle still helps: you stop wasting attention on the unsolvable and redirect to what isn't.
What specifically do you not know that, if you knew it, would unlock the problem? This is the most important question. It converts the problem from "stuck" to "actionable research question."
Diagnostic — finish this sentence: "If we knew ___, we could solve this." If you cannot finish that sentence, the problem is not yet well-formed; that is the first thing to fix.
How would you get the missing knowledge? Possibilities:
When someone says "it can't be done," ask:
Deutsch's sharpest point: pessimism is a way of saying "I know the future" — a future in which the knowledge that would solve the problem will not be acquired. That is a strong epistemic claim, almost always unjustified.
Deutsch's optimism is demanding. It requires you to actually engage with the problem, identify the missing knowledge, and pay the cost of acquiring it. It does not say "everything will work out." It says "everything can work out, if we do the work." If a person uses "optimism" to avoid doing the work, they have inverted the principle.
For any "impossible" problem in front of the user:
Produce a one-page Principle-of-Optimism audit:
End with: "An unproblematic state is a state without creative thought. Its other name is death." — David Deutsch
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub adamtpang/summon.guide --plugin deutsch