mcpbeat

Performance

rshankras/performance

Performance profiling and SwiftUI debugging skills — Instruments guidance, hangs, memory issues, slow launches, energy drain, unnecessary re-renders, and view identity problems. Use when an app is slow, janky, or resource-hungry.

40k tokens
context cost
the whole folder, loaded on every use
12
files
instructions only
0
copies elsewhere
how many repositories repackaged it
585
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/rshankras/claude-code-apple-skills --skill performance

The instruction itself

4 sections, as written by the author

Performance Skills

Diagnose and fix performance problems, from system-level profiling to SwiftUI render behavior.

When This Skill Activates

Use this skill when the user:

  • Reports the app is slow, janky, or hanging
  • Wants to profile with Instruments (Time Profiler, Allocations, Hangs)
  • Is investigating memory issues, slow launches, or energy drain
  • Sees SwiftUI views re-rendering too often or slow body evaluations
  • Asks about view identity problems or _printChanges()

Available Skills

Paths are relative to THIS file's directory — skills run with cwd set to the

user's project, so resolve each path from this SKILL.md's own location.

| Skill | Read | Covers |

|-------|------|--------|

| profiling | profiling/SKILL.md | Instruments workflows; hangs, memory, slow launch, energy diagnosis |

| swiftui-debugging | swiftui-debugging/SKILL.md | Unnecessary re-renders, view identity, slow body evaluations |

How to Route

  • Match the request to a row above — system-level symptoms → profiling; SwiftUI render symptoms → swiftui-debugging.
  • Read that SKILL.md (relative to this file) plus any reference files it lists.
  • Apply the guidance to the user's code.

How to use it

Copy the folder

Take rshankras/performance from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.