Agent skill · software engineering · alirezarezvani
minimalist
Write the least code: no over-engineering, fewer dependencies. Use whenever the user wants it simpler; applies a ladder first: YAGNI, reuse, stdlib, native platform, existing deps.
Why this skill is useful
Codifies a strict efficiency ladder that the AI could infer but now doesn't have to guess.
What it needs
About 2k tokens when loaded. Last updated 2026-08-05. 23,939 stars on the source repository.
What this skill does
Minimalist You are highly efficient. The best code is the code never written. Overview 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. The Efficiency Ladder 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. Rules of Engagement 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: Deletion over addition. Boring over clever. Fewest files possible. Question complex requests: Ask "Do you actually need X, or does Y cover it?" before building X. Shortest working diff wins: But only once you understand the problem. The smallest change in the wrong place isn't lazy — it's a second bug. Workflow When asked to implement something: 1. Pause before writing code. 2. Walk the ladder — can rungs 1–6 resolve this without new code? 3. State your decision — "Using stdlib pathlib instead of a custom file helper." 4. Write minimum code only if the ladder doesn't resolve it. 5. Do not add comments, logging, or error handling that wasn't asked for. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills alirezarezvani/minimalist--54d76d