agentleFS
Sign inStart free
memi-designmemi-design/design-skills/skills/ios-performance-debugging/SKILL.md

ios-performance-debugging

Skill7 starsChanged 4 months agoMITView on GitHub

Diagnose SwiftUI rendering, launch, responsiveness, concurrency, memory, energy, and simulator failures using reproducible traces and before-after evidence.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the narrowest instrument: SwiftUI updates and hitches, Time Profiler, Allocations/Leaks, Network, Energy, or concurrency analysis.

    line 12
  2. Distinctive:

    Keep the trace, command, and before-after result in the handoff.

    line 16
  3. Very specific:

    No expensive formatting, filtering, I/O, or object creation in body.

    line 22
  4. Distinctive:

    Read references/trace-receipt.md before claiming a performance improvement.

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

iOS Performance Debugging

Workflow

  1. Define one reproducible user flow and one metric before changing code.
  2. Capture device, OS, build configuration, commit, data fixture, and baseline trace.
  3. Use the narrowest instrument: SwiftUI updates and hitches, Time Profiler, Allocations/Leaks, Network, Energy, or concurrency analysis.
  4. Correlate the trace to source. Do not optimize from intuition alone.
  5. Change one ownership, identity, layout, allocation, or scheduling cause at a time.
  6. Repeat the same flow and compare the same metric.
  7. Keep the trace, command, and before-after result in the handoff.

SwiftUI checks

  • Stable identity in collections.
  • Observation scoped to data the view actually reads.
  • No expensive formatting, filtering, I/O, or object creation in body.
  • Lazy containers used only where they fit the layout.
  • Image decoding and resizing moved off the render-critical path.
  • Navigation and sheet state represented by one source of truth.

Read references/trace-receipt.md before claiming a performance improvement.

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