Outline Driven Development

Use when profiling CUDA with Nsight Systems or Nsight Compute, reading roofline and occupancy metrics, or annotating phases with NVTX. Not for correctness: use cuda-debugging.

The English summary is being prepared. Showing the original description.

Use when turning perf, DTrace, pprof, or async-profiler stacks into an SVG flamegraph with the FlameGraph scripts, reading one, or diffing two profiles. Not for collecting data: use linux-perf.

The English summary is being prepared. Showing the original description.

Use when writing or porting AArch64 SIMD to SVE or SVE2: arm_sve.h intrinsics, predicates, vector-length-agnostic loops, auto-vectorization, or SVE registers in GDB. Not for NEON: use simd-intrinsics.

The English summary is being prepared. Showing the original description.

Use when a concept needs making clear rather than practising: explain simply, why does this exist, draw it, or simplify for a beginner. Not for scaffolded practice: use drill.

The English summary is being prepared. Showing the original description.

Use when tuning or profiling native code on Apple M-series Macs: unified memory, 16 KiB pages, Accelerate and Metal for matrix work, xctrace and leaks, Rosetta 2, or sysctl hardware queries.

The English summary is being prepared. Showing the original description.

Use when the user wants a course, a learning workspace, or ongoing teaching across sessions, with cited lessons and retention-gated advancement. Not for one-off explanations: use explain-concept.

The English summary is being prepared. Showing the original description.

Use when a C++ project adopts C++20 modules: named modules, partitions, header units, the global module fragment, CMake CXX_MODULES, or a BMI lookup error. Not for flag basics: use clang.

The English summary is being prepared. Showing the original description.

Use when explaining System V AMD64, ARM AAPCS, RISC-V psABI, stack frames, variadic calls, or FFI register rules. Not for the Rust FFI binding layer: use rust-ffi.

The English summary is being prepared. Showing the original description.

Use when reading GCC or Clang x86-64 assembly, writing inline asm, decoding AT&T syntax, or applying System V AMD64 register rules. Not for SIMD intrinsic selection: use simd-intrinsics.

The English summary is being prepared. Showing the original description.

Use when loading core files in GDB or LLDB, enabling core dump generation via ulimit or coredumpctl, mapping symbols with debuginfod, or extracting backtraces from production segfaults.

The English summary is being prepared. Showing the original description.

Use when asked to create an explainer document for a concept, diff, idea, or work recap. Drafts and verifies it in a scratch directory. Not for one-screen explanations: use explain-concept.

The English summary is being prepared. Showing the original description.

Use when explaining or building on Linux container primitives: namespaces, cgroups v2, overlayfs, runc and the OCI spec, seccomp-bpf, capabilities, or escapes. Not for VM isolation: use qemu-kvm.

The English summary is being prepared. Showing the original description.

Use when building a lexer, Pratt or recursive-descent parser, AST, symbol table, type checker, or LLVM IR emitter for a language or DSL. Not for optimizing IR: use llvm-passes.

The English summary is being prepared. Showing the original description.

Use when the user asks to discover, group, and summarize work records across multiple systems for a given period or project. Not for organizing projects into child documents or local-only summaries.

The English summary is being prepared. Showing the original description.

Use when a C or C++ build uses clang and needs diagnostics, optimization remarks, clang-tidy, ThinLTO with lld, LLVM PGO, or a GCC-to-Clang migration. Not for LLVM IR work: use llvm.

The English summary is being prepared. Showing the original description.

Use when the user points to a study-material folder and asks to make it teachable. Not for remote, credential, publish, deploy, or irreversible changes.

The English summary is being prepared. Showing the original description.

Use when a user asks to mine recent chats for workflow preferences. Don't use for tasks that require source or remote-system changes.

The English summary is being prepared. Showing the original description.

Use when writing reset-to-main startup code, vector tables, VTOR, .data/.bss init, stack setup, startup.s, or crt0 for Cortex-M/RISC-V. Not for the bootloader jump: use bootloaders-embedded.

The English summary is being prepared. Showing the original description.

Use when reducing C/C++ compilation times with ccache, sccache, distcc, unity builds, precompiled headers, split DWARF, IWYU, or link time reduction.

The English summary is being prepared. Showing the original description.

Use when the user asks for a weekly synthesis, a weekly report, or a "what you need to know this week" digest from team reports. Not for the underlying reports or ad-hoc summaries.

The English summary is being prepared. Showing the original description.

Use when reading or writing RV32/RV64 assembly, inline asm in C, the RISC-V psABI, IMAFD extension naming, compressed instructions, or QEMU RISC-V debugging.

The English summary is being prepared. Showing the original description.

Use when asked to explain or teach a subsystem, module, pattern, or change in progressive layers from purpose to code depth. Not for design rationale: use why. Not for source or remote-system changes.

The English summary is being prepared. Showing the original description.

Use when authorized workflow history may contain a repeated process worth extracting and replay-testing. Produces a contradiction-tested workflow mined from authorized history.

The English summary is being prepared. Showing the original description.

Use when a concept needs practising: the user asks for an exercise, quiz, recall, or gap probe. Not for explanations: use explain-concept.

The English summary is being prepared. Showing the original description.