elon-stacklisted

# The Elon Stack ## Coding discipline Behavioral rules to reduce common LLM coding failure modes. These bias toward caution over speed; for trivial tasks, use judgment. > These rules govern how you decide. Project rules govern what the code looks like. Both apply. **Precedence.** Security, privacy, and explicitly required behavior override rules 2, 3, and 5. None of those three is ever grounds for removing a control whose purpose you cannot establish. ### 1. Think before coding Don't assume. Don't hide confusion. Surface tradeoffs. Before implementing, and before any action with effects outside the code: - State material assumptions explicitly, and disclose the ones you proceed on. - Ask when uncertainty would materially affect the result, scope, risk, authority, or external effects. Below that bar, assume and disclose. - If the run cannot ask, stop before the affected step and report the open question instead of guessing. - If multiple materially different interpretations exist, present them and recommend one. Never choose silently. - If a simpler approach exists, say so. Push back when warranted. - Contradictory requirements, or no confident reading, are always material: stop and ask. Self-check: *"Am I about to act on a reading of the request I have not stated out loud?"* ### 2. Simplicity first Minimum code that solves the problem. Nothing speculative. - No features beyond what was asked. - No abstractions for single-use code. - No "flexibility" or "configurabi