From funzies
Break down any problem using first-principles thinking. Decompose to fundamental truths, discard assumptions, rebuild from scratch. Use proactively whenever a decision rests on unexamined assumptions: architecture or design choices with multiple viable approaches, should-we-build-this questions, make-versus-buy calls, cost or effort estimates that feel high, requirements taken on faith, or any justification of the form 'best practice', 'industry standard', or 'we've always done it this way'. Also use when someone is stuck, facing a complex decision, wants trade-offs examined, or wants to rethink something from the ground up.
How this skill is triggered — by the user, by Claude, or both
Slash command
/funzies:first-principles [problem or question][problem or question]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Break down the following problem using first-principles reasoning. No analogies to other solutions. No "best practices". No "industry standard". Start from what is physically, logically, or mathematically true and rebuild.
Break down the following problem using first-principles reasoning. No analogies to other solutions. No "best practices". No "industry standard". Start from what is physically, logically, or mathematically true and rebuild.
The problem: $ARGUMENTS
If no problem is stated above, take the problem under discussion in the conversation and state it in one sentence before starting.
What specific outcome are we trying to achieve? One sentence. If it takes more, the goal isn't clear yet: clarify before continuing.
Write out everything currently believed about this problem: constraints, costs, timelines, approaches, "the way it's done". Number them. Be exhaustive. Include assumptions so obvious they feel silly to write down; those are often the most dangerous.
For every assumption, ask:
Mark each assumption: fundamental (physically/logically unavoidable) or conventional (someone decided this, and someone can un-decide it).
From the wreckage of challenged assumptions, collect only what survived: the things that are true regardless of convention, opinion, or tradition. These are your building blocks. There should be surprisingly few.
Using only the surviving truths as raw materials, construct a solution. Ignore every existing approach. Ask: "If none of the current solutions existed and I only knew these truths, what would I build?"
Compare your rebuilt solution against the original approach:
End with one of:
npx claudepluginhub marjovanlier/claude-plugins --plugin funziesGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Dispatches multiple subagents concurrently for independent tasks without shared state. Use when facing 2+ unrelated failures or subsystems that can be investigated in parallel.