exec-performance
Skill1 starsChanged 28 days agoMITView on GitHub
Execution skill loaded when optimizing code, dealing with large datasets, or addressing latency issues.
In this repository29 other files it gives its agents.
- exec-accessibilitySkill
- exec-architectureSkill
- exec-code-reviewSkill
- exec-debuggingSkill
- exec-documentationSkill
- exec-refactoringSkill
- exec-repo-patternsSkill
- exec-securitySkill
- exec-testingSkill
- exec-ui-uxSkill
- exec-verificationSkill
- tech-dockerSkill
- tech-flutterSkill
- tech-goSkill
- tech-graphqlSkill
- tech-kotlinSkill
- tech-nextjsSkill
- tech-nodeSkill
- tech-postgresSkill
- tech-pythonSkill
- tech-reactSkill
- tech-rustSkill
- tech-swiftSkill
- tech-tailwindSkill
- tech-typescriptSkill
- tech-vueSkill
- linear-spanks-gitSkill
- linear-spanksSkill
- linear-workflowSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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 7
When your task targets performance optimizations, evaluate the following before changing code:
- Distinctive: line 9
Algorithmic Complexity: Avoid O(n^2) or worse loops.
- Distinctive: line 12
Lazy Loading: Do not load resources (images, components, data) until they are needed by the user.
- Distinctive: line 13
Memory Leaks: Ensure event listeners are cleaned up and large objects are garbage collected.
- Distinctive: line 15
Do not prematurely optimize.
≈ “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
Performance Execution Strategy
When your task targets performance optimizations, evaluate the following before changing code:
- Algorithmic Complexity: Avoid O(n^2) or worse loops. Use HashMaps/Sets for O(1) lookups instead of nested arrays.
- Caching: Is the data static or rarely changing? Propose a caching layer (in-memory, Redis) rather than recomputing.
- Batching: Group database queries or API calls into batches to minimize network latency.
- Lazy Loading: Do not load resources (images, components, data) until they are needed by the user.
- Memory Leaks: Ensure event listeners are cleaned up and large objects are garbage collected.
Do not prematurely optimize. Ensure you have a baseline metric to prove the optimization actually works.
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.