agentleFS
saitarrunsaitarrun/Devforge-ai/skills/performance-optimization/SKILL.md

performance-optimization

Skill4 starsChanged 5 months agoApache-2.0View on GitHub

Profile systems, identify bottlenecks, optimize code and infrastructure for speed, throughput, and resource efficiency.

125 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use constraint-driven-development, git-workflow-and-versioning and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MrCipherSmithSkill

    constraint-driven-development

    Use when a project needs a persistent, measurable quality bar — starting a project without documented standards, 'set up constraints', or when coverage/perf/a11y thresholds get re-debated per-PR. Produces CONSTRAINTS.md with enforceable numbers, ratchets, and a guard against silent weakening. NOT for throwaway prototypes or a one-off CI setup.

    Also in 15 projects that use this

  • LLl0k0laDSkill

    git-workflow-and-versioning

    Use when making any code change. Use when committing, branching, resolving conflicts, or when you need to organize work across multiple parallel streams.

    Also in 42 projects that use this

  • LLl0k0laDSkill

    using-agent-skills

    Use when starting a session or when you need to discover which skill applies to the current task. This is the meta-skill that governs how all other skills are discovered and invoked.

    Also in 33 projects that use this

  • HK-hubSkill

    deprecation-and-migration

    Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code.

    Also in 39 projects that use this

  • ukanwatSkill

    input-systems

    Architect game input — action mapping (abstracting keys into named actions), rebinding with conflict detection and persistence, multi-device support (keyboard, gamepad, touch), analog deadzones, and feel features like input buffering and coyote time, plus accessibility. Engine-neutral. Use when the user mentions input mapping, rebind controls, gamepad support, deadzone, input buffering, coyote time, or accessible controls.

    Also in 4 projects that use this

  • HK-hubSkill

    observability-and-instrumentation

    Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.

    Also in 31 projects that use this

  • +6 more from LLl0k0laD

The file

Files
SKILL.md

Skill: Performance Optimization

Systematic approach to identifying and eliminating performance bottlenecks through profiling, benchmarking, and data-driven optimization.

Process

  1. Establish Baselines — Measure current performance (latency, throughput, memory, CPU)
  2. Profile — Identify where time/resources are spent (flame graphs, traces, logs)
  3. Find Bottlenecks — Rank by impact (80/20 rule: fix the top bottlenecks first)
  4. Optimize — Apply targeted fixes (algorithm, caching, parallelization, resource allocation)
  5. Verify — Re-measure to confirm improvements
  6. Prevent Regressions — Add performance tests, monitoring, budgets

Key Metrics

  • Latency: p50, p95, p99 response time
  • Throughput: Requests per second, transactions per minute
  • Resource Usage: CPU %, memory consumption, disk I/O
  • Cost: Infrastructure cost per unit work

Common Bottlenecks

  • Inefficient algorithms (O(n²) instead of O(n log n))
  • Missing indexes on database queries
  • Synchronous operations that should be async
  • Excessive logging or serialization
  • Memory leaks or inefficient data structures
  • Network calls without batching/caching
  • Single-threaded workloads that could parallelize

Optimization Strategies

  1. Algorithmic: Better algorithm selection
  2. Caching: Reduce computation, add layer caching
  3. Async: Non-blocking operations, parallelization
  4. Resource Allocation: CPU, memory, connections tuning
  5. Infrastructure: Scaling, CDN, geographic distribution
  6. Monitoring: Real-time alerting on perf regressions

Status: Ready for profiling, optimization, and performance tuning Best for: Latency reduction, throughput improvement, resource efficiency

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.