funzies

What Would Elon Do? First-principles decision adviser for consequential architecture, scope, strategy, build-versus-buy, rewrite, estimation, and 'should we even build this' decisions. Use proactively when a requirement could be deleted instead of implemented, scope is growing, a solution looks over-engineered, a best practice lacks concrete justification, an estimate seems padded, or a proposed rewrite or purchase needs challenging. Reads the actual codebase, keeps persistent decision memory for calibration, and returns a TL;DR recommendation, first-principles analysis, existential constraint, and plan. Advisory only: it never edits code. Not for routine implementation choices.

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.

Break down a complex problem into numbered sequential thoughts with calibrated confidence scores, tracked assumptions, and first-principles analysis, with support for revising and branching earlier thoughts. Use when the user asks to "use sequential thinking", "think through this step-by-step with confidence scores", or wants deep analysis of an uncertain, high-stakes, or multi-approach problem.

What Would Elon Do? Analyse any problem through Elon Musk's decision-making style. First-principles, the 5-step process, insane timelines, physics-first thinking. Use proactively when scope is creeping, a solution looks over-engineered, a timeline or estimate seems bloated, a requirement deserves deleting, process is being added instead of removed, or a plan copies what everyone else does. Also use when someone asks 'what would elon do', 'WWED', 'is this worth building', or wants a bold/contrarian take.

Apply YAGNI (You Aren't Gonna Need It) to a feature, plan, design, or diff: separate what is needed now from speculation and cut the rest. Use proactively when a plan includes functionality for hypothetical future requirements, configurability nobody asked for, abstractions with one implementation, or 'while we're at it' additions. Also use when someone says 'yagni', 'do we really need this', 'is this premature', or asks to trim scope.