agentleFS
Sign inStart free
emaraschioemaraschio/cursor-commands/.cursor/skill-contracts/optimize-performance/SKILL.md

optimize-performance

Skill9 starsChanged 3 months agoMITView on GitHub

Profile and optimize performance bottlenecks

7 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 4

    Distinctive

    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
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Consider trade-offs between performance and maintainability

    line 27
  2. Distinctive:

    Do not trade readability for unmeasured micro-gains.

    line 44
  3. Distinctive:

    Do not commit, push, merge, or run production scripts without consent.

    line 45
  4. Distinctive:

    Do not print, log, or commit secrets or credentials encountered while profiling or optimizing.

    line 46

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Overview

Analyze the current code for performance bottlenecks and provide optimization recommendations, focusing on measurable improvements while maintaining code quality and readability.

Steps

  1. Performance Analysis
    • Identify slow algorithms and inefficient data structures
    • Find memory leaks and excessive allocations
    • Identify slow queries and improve them specifically for Solid Queue and n+1 queries
    • Detect unnecessary computations and redundant operations
    • Analyze database queries and API calls
  2. Optimization Strategies
    • Suggest algorithm improvements and better data structures
    • Recommend caching strategies where appropriate
    • Propose lazy loading and pagination solutions
    • Identify opportunities for parallel processing
  3. Implementation
    • Provide optimized code with explanations
    • Include performance impact estimates
    • Suggest profiling and monitoring approaches
    • Consider trade-offs between performance and maintainability

Optimize Performance Checklist

  • Identified slow algorithms and inefficient data structures
  • Found memory leaks and excessive allocations
  • Detected unnecessary computations and redundant operations
  • Analyzed database queries and API calls
  • Suggested algorithm improvements and better data structures
  • Recommended caching strategies where appropriate
  • Provided optimized code with explanations
  • Included performance impact estimates
  • Considered trade-offs between performance and maintainability

Guardrails

  • Measure first: profile to find the real bottleneck before changing code.
  • Do not trade readability for unmeasured micro-gains.
  • Do not commit, push, merge, or run production scripts without consent; wait for an explicit request before any destructive git action.
  • Do not print, log, or commit secrets or credentials encountered while profiling or optimizing; flag any exposed secret instead.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free