القائمة
Use when profiling native macOS or iOS apps with Instruments/xctrace. Covers correct binary selection, CLI arguments, exports, and common gotchas.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Context pressure checkpoint, self-handoff, and durable lesson capture workflow. Use when an agent is near the context limit, context usage is above 98%, auto-compaction or context warnings appear, the user says high tide, before `/clear`, or after a long confusing/debugging session where lessons learned should be preserved for the next fresh session or written to project-local `docs/.ai/lessons/`.
Generate execution-ready, model-specific prompts for handing work to a different LLM agent or fresh session. Use for shared-workspace delegation, cold-start continuation, cross-model transfer, one-shot worker directives, or requests such as "create a handoff prompt", "delegate this", "hand this off", and "prepare context for another agent". Supports current Anthropic Claude, OpenAI GPT/Codex, Google Gemini, and xAI Grok families.
Surface hidden unknowns before, during, and after implementation using structured techniques — clickable mocks, intervention brainstorms, semantics maps, tweakable plans, implementation notes, buy-in docs, and more. Use PROACTIVELY when entering an unfamiliar codebase or domain, when a feature request is ambiguous or underspecified, when the user says "I'm not sure", "I'll know it when I see it", or has no design direction, when porting from a reference implementation, when writing an implementation plan, before merging a large diff, or when packaging work for reviewer sign-off. Also triggers on explicit asks: "blindspot pass", "interview me", "quiz me before I merge", "show me design directions", "teach me <domain>", "what am I missing?".
Profile Rust code using samply and related evidence to identify CPU bottlenecks, allocation hot paths, and allocator-fragmentation symptoms. Use when performance is slow, RSS grows unexpectedly, before optimizing, or when the user asks to profile.
Measure and improve Go program performance on modern Go (1.24+). Use when profiling Go code, diagnosing CPU or memory bottlenecks, investigating latency or contention, writing or fixing benchmarks, comparing benchmark results, using pprof or trace data, applying PGO, or tuning hot-path Go code.
Behavior-preserving cleanup for recently changed code. Use after implementing or modifying code, when explicitly invoked as `$code-simplifier`, or when the user asks to simplify, clean up, or refactor the current diff without widening scope.
| name | instruments-profiling |
| description | Use when profiling native macOS or iOS apps with Instruments/xctrace. Covers correct binary selection, CLI arguments, exports, and common gotchas. |
| metadata | {"short-description":"Instruments profiling for macOS/iOS apps"} |
Use this skill when the user wants performance profiling or stack analysis for native apps.
Focus: Time Profiler, xctrace CLI, and picking the correct binary/app instance.
xcrun xctrace list templatesxcrun xctrace record --template 'Time Profiler' --time-limit 60s --output /tmp/App.trace --launch -- /path/To/App.appxcrun xctrace record --template 'Time Profiler' --time-limit 60s --output /tmp/App.trace --attach <pid>open -a Instruments /tmp/App.traceNote: xcrun xctrace --help is not a valid subcommand. Use xcrun xctrace help record.
Gotcha: Instruments may profile the wrong app (e.g., one in /Applications) if LaunchServices resolves a different bundle.
Use these rules:
xcrun xctrace record ... --launch -- /path/App.app/Contents/MacOS/App.app, ensure it’s the intended bundle:
open -n /path/App.appps -p <pid> -o comm= -o command=/Applications/App.app and a local build exist, explicitly target the local build path.--template 'Time Profiler': template name from xctrace list templates.--launch -- <cmd>: everything after -- is the target command (binary or app bundle).--attach <pid|name>: attach to running process.--output <path>: .trace output. If omitted, file saved in CWD.--time-limit 60s|5m: set capture duration.--device <name|UDID>: required for iOS device runs.--target-stdout -: stream launched process stdout to terminal (useful for CLI tools).xcrun xctrace export --input /tmp/App.trace --tocxcrun xctrace export --input /tmp/App.trace --xpath '/trace-toc/run[@number="1"]/data/table[@schema="time-profile"]' --output /tmp/time-profile.xml--attach with known PID.xctrace may need Developer Tools permission.
time-profile exports are huge.
xcrun xctrace list devices and --device <UDID>.xctrace --attach.