agentleFS
alamenaialamenai/terrae/.claude/skills/perf/SKILL.md

perf

Skill245 starsChanged 9 months agoMITView on GitHub

Audit component performance and identify optimization opportunities with actionable fixes

21 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use incident, refactor and 7 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.
  • JkudjoSkill

    incident

    Production incident response — structured triage, hypothesis tree, safe remediation, incident record

    Also in 3 projects that use this

  • GitHubSkill

    refactor

    Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.

    Also in 6 projects that use this

  • 0xSeroSkill

    security

    Also in 4 projects that use this

  • AnthropicSkill

    debug

    Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious.

    Also in 7 projects that use this

  • Microsoft AzureSkill

    design

    Design rules and conventions for the API Center Portal. Use when editing detail pages, card components, badges, layout, navigation, sidebars, or headers. Covers badge styling, metadata placement, page navigation patterns, and layout alignment.

    Also in 4 projects that use this

  • SentrySkill

    onboard

    Onboard a service to sentry-options. Use when integrating a new service, creating schemas, or setting up the multi-repo sentry-options workflow.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If $ARGUMENTS is provided, audit only that component.

    line 12
  2. Very specific:

    If a component name is provided, locate it in src/registry/map/.

    line 20
  3. Distinctive:

    10/10: No issues found, follows all best practices

    line 73

“Common” is measured: kept by at least 6 in 10 of the 16 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

Performance Audit Skill

Audit Terrae components for performance issues. Identifies problems, explains their impact, and provides actionable fixes.

If $ARGUMENTS is provided, audit only that component. Otherwise, audit all components in src/registry/map/.

Performance patterns and best practices are defined in .claude/rules/react/performance.md.

Instructions

Step 1: Identify Target

If a component name is provided, locate it in src/registry/map/. Otherwise, scan all component files.

Step 2: Run the Audit

For each component, read the full file and check every rule in .claude/rules/react/performance.md:

  1. Resource cleanup (RAF, timers, listeners, markers, layers, sources, images, observers, canvas)
  2. Recursive requestAnimationFrame polling
  3. Untracked timers in renderers
  4. Mapbox objects in state vs refs
  5. useEffect dependency arrays (oversized, unstable references, callbacks)
  6. Layer and source management (setPaintProperty vs remove/re-add, existence checks)
  7. GeoJSON data handling (recomputation, update frequency)
  8. Canvas performance (pixel ratio, size, getImageData, off-screen canvas)
  9. DOM manipulation (innerHTML, style injection)
  10. Memory leaks (event listeners, growing collections, stale closures)

Also check for:

  • Component re-render cost (expensive computations in render path, large JSX trees)
  • Duplicate utility functions across files (DRY violations that bloat bundle size)

Step 3: Report

Structure the report as:

## Performance Audit: [Component Name]

### Score: [X/10]

### Critical Issues
Issues that cause measurable performance degradation or memory leaks.

### Warnings
Patterns that could degrade performance under load or over time.

### Best Practices
Recommendations for following optimal patterns.

### Passed Checks
Checks that the component already handles correctly.

For each issue found, include:

  • What: Description of the problem
  • Where: File path and line number
  • Impact: What happens if not fixed (memory leak, jank, unnecessary re-renders, etc.)
  • Fix: Concrete code example showing the solution

Scoring Guide

  • 10/10: No issues found, follows all best practices
  • 8-9/10: Minor warnings only, no performance impact
  • 6-7/10: Some warnings that could cause issues under load
  • 4-5/10: Has performance issues that affect user experience
  • 2-3/10: Critical issues causing memory leaks or severe jank
  • 0-1/10: Fundamentally broken performance patterns

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.