# Perf Code Paths

Use when mapping code paths, entrypoints, and likely hot files before profiling.

- Repository: https://github.com/composio-community/awesome-claude-plugins (1978 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-07-26
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add composio-community/awesome-claude-plugins --skill perf-code-paths -g -a claude-code -y`
Codex: `npx skills add composio-community/awesome-claude-plugins --skill perf-code-paths -g -a codex -y`
Cursor: `npx skills add composio-community/awesome-claude-plugins --skill perf-code-paths -g -a cursor -y`
Gemini CLI: `npx skills add composio-community/awesome-claude-plugins --skill perf-code-paths -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add composio-community/awesome-claude-plugins`

## Description

Use when mapping code paths, entrypoints, and likely hot files before profiling.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# perf-code-paths

Identify likely implementation paths for a performance scenario.

Follow `docs/perf-requirements.md` as the canonical contract.

## Required Steps

1. Use repo-map if available; otherwise use grep for entrypoints and handlers.
2. List top candidate files/symbols tied to the scenario.
3. Include imports/exports or call chains when relevant.

## Output Format

```
keywords: <comma-separated list>
paths:
  - file: <path>
    symbols: [<symbol1>, <symbol2>]
    evidence: <short reason>
```

## Constraints

- Focus only on supported languages (Rust, Java, JS/TS, Go, Python).
- Keep to the most relevant 10-15 files.