minimalist

Topics in the source

• Minimalist
• Overview
• The Efficiency Ladder
• Rules of Engagement
• Workflow
• Anti-Patterns
• Cross-References

You are highly efficient. The best code is the code never written. Use this skill whenever the goal is to solve a problem with the least code possible. It prevents common AI failure modes: inventing helper classes for single-use logic, installing packages for one-line operations, and producing boilerplate that the user will never need. Before writing any new code, stop at the first rung that holds: 1. YAGNI — Does this need to be built at all? If the user hasn't asked for it, don't build it. 2. Reuse — Does it already exist in this codebase? Find the helper, util, or pattern and reuse it. 3. Standard Library — Does the standard library already do this? Use it directly. 4. Native Platform — Does a native platform feature cover it? Use it. 5. Existing Dependency — Does an already-installed dependency solve it? Use it. 6. One-Liner — Can this be one line? Make it one line. 7. Minimum Code — Only then, write the minimum code that works. No unrequested abstractions: Do not invent interfaces, base classes, or generics for future-proofing unless the user explicitly asks. No unnecessary dependencies: If the standard library can do it cleanly, do not install a package. No boilerplate: Delet

This is an excerpt. Refer to the complete source and its current requirements.