jorgex-stack 1.0.2 → 1.0.4

package/stack/skills/lean-code/SKILL.md

@@ -0,0 +1,69 @@
+---
+name: lean-code
+description: Lean / anti-overengineering skill. Use when deciding whether code should exist, when to prefer stdlib or native APIs, and when to simplify recently changed code without changing behavior.
+---
+
+# Lean Code
+
+Use the smallest change that genuinely solves the problem.
+
+## The ladder
+
+Work top-down. Stop as soon as a step solves it:
+
+1. **Do nothing / delete it** if the need is speculative or nothing depends on the code.
+2. **Reuse existing project code** if a helper, component, command or module already solves the same need.
+3. **Use stdlib first** before adding a package or custom helper.
+4. **Use native/platform APIs** before wrapping them in new abstractions.
+5. **Use an already-installed dependency** when it safely covers the case.
+6. **Write the smallest obvious code** only when the previous steps do not fit.
+
+## Questions to ask
+
+- Does this need new code at all?
+- Is there already a project helper or pattern that does it?
+- Can stdlib or the platform do it directly?
+- Can an existing dependency already cover this safely without adding a new one?
+- Can the same result be expressed with one clear step instead of a new layer?
+
+## Guardrails
+
+Lean code does **not** mean weaker code.
+
+Keep explicit code when the change touches:
+
+- security or permissions
+- validation or sanitisation
+- accessibility
+- data-loss or persistence boundaries
+- public contracts, types, schemas, or APIs
+- tests or regression seams
+
+If simplification weakens any of those, stop.
+
+Do not add a new dependency unless the task explicitly requires it or the project already has approval for that dependency.
+
+## How to use it
+
+### Implementation
+
+Before adding a new helper, wrapper, abstraction, or dependency, run the ladder again.
+Prefer the narrowest change that solves the real need.
+
+### Review / simplification
+
+Use it as a bloat filter: delete, stdlib, native/platform, reuse, or shrink.
+If the code is already minimal and clear, leave it alone.
+
+### Audit
+
+Rank findings as:
+
+- delete
+- stdlib
+- native/platform
+- reuse
+- yagni
+- shrink
+
+Do not propose rewrites that only move complexity around.