AaronFriel

Profile flameview itself under high sample rates and heavy folded inputs, identify parser/viewer hotspots, and validate improvements with benches/tests. Use when optimizing flameview performance or verifying regressions after profiler-related changes.

Profile Rust binaries on Linux using cargo flamegraph/perf custom events, keep folded stacks, and inspect them with flameview. Use when you need repeatable CPU/custom-event profiling with minimal dependencies, or when converting allocation profiles into flameview-ingestible folded stacks.

Drive interactive flameview terminal sessions and verify UX behavior (columns, filters, navigation, auto-expand). Use when a task requires launching flameview on folded stacks, exercising key bindings, reproducing TUI bugs, or capturing manual UX validation steps.

Create and maintain snapshot-style regression tests for flameview interactive UI by replaying key sequences and asserting textual screen snapshots with Insta. Use when UI layout, key handling, filters, or heuristics change and you need deterministic regression coverage.

Create and maintain concrete plans.md, plan.md, record.md, and records.md files for substantial Codex work. Use when the user asks to plan work, organize several related tasks, continue until done, delegate to subagents, run experiments, design an app, perform security review, or avoid vague planning language.

Revise writing so it is easy to understand, specific, and useful. Use for documentation, design documents, plans, proposals, launch notes, reviews, PR descriptions, status updates, and multi-paragraph messages. Remove vague nouns and measures, canned phrases, sentences with too many ideas, empty claims, repeated writing patterns, and needless formatting. Preserve facts, uncertainty, technical terms, and the author's voice. Skip tiny mechanical edits.