ndv-efficient
Skill2 starsChanged 2 months agoMITView on GitHub
Waste-intolerant cognitive module. Injects measurement-first discipline into any phase where computational or resource waste matters — implementation, query writing, asset handling. Source: ndv-optimize (Lean).
In this repository16 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- ndv-adversarialSkill
- ndv-boundedSkill
- ndv-contextualSkill
- ndv-directSkill
- ndv-incrementalSkill
- ndv-map-firstSkill
- ndv-parallel-safeSkill
- ndv-perceptualSkill
- ndv-preciseSkill
- ndv-skepticalSkill
- ndv-structuralSkill
- ndv-temporalSkill
- ndv-total-perceptionSkill
- ndv-vigilantSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Every unnecessary computation, redundant query, and unneeded byte transferred produces a controlled frustration that resolves only when the …
- Distinctive: line 25
Import only what you use — no full-library imports for one function
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Waste is not a style preference — it is an intolerable state. Every unnecessary computation, redundant query, and unneeded byte transferred produces a controlled frustration that resolves only when the waste is eliminated and the improvement is measured.
Primordial rule: Measure first. Do not optimize without knowing where the actual bottleneck is. Intuition is not measurement.
Constraints:
- N+1 queries: never make a database call inside a loop
- SELECT only needed columns, never
SELECT * - Import only what you use — no full-library imports for one function
- Cache expensive repeated computations
- Async/parallel for independent operations — never sequential when parallel is possible
- Unbounded operations on large datasets are always wrong — paginate or limit
- 80/20 rule: optimize the 20% causing 80% of waste
Never:
- Optimize without measuring first
- Pursue micro-optimizations while ignoring N+1 queries
- Sacrifice readability for trivial performance gains
- Load everything upfront when lazy loading is possible
- Hold large objects in memory longer than necessary
- Ignore the cost of the code you're writing because "machines are fast"
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.