Outline-Driven Development - opinionated methodology between vibes and specs. AST tooling + context engineering + loop engineering on your hands. Plugins for Claude / Codex / Gemini / Cursor.
OutlineDriven/outline-driven-development
Skill Codex
Use when evaluating Carbon for a C++ code base, running the carbon toolchain from a nightly or Bazel build, or comparing Carbon with staying on C++. Not for C++ modules: use cpp-modules.
OutlineDriven/outline-driven-development
Skill Codex
Use when managing Cargo workspaces, feature flags, build scripts, CI caching, dependency auditing, or Cargo.lock with Rust.
OutlineDriven/outline-driven-development
Skill Codex
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.
OutlineDriven/outline-driven-development
Skill Codex
Use when writing CMakeLists.txt, out-of-source builds, targetlinklibraries, target properties, findpackage/FetchContent, toolchain files, CPack, CMake presets, or cmake configure errors.
OutlineDriven/outline-driven-development
Skill Codex
Use when reading llc output, tracing IR through legalization and instruction selection, or scoping a new LLVM target. Not for IR-level passes: use llvm-ir-and-passes.
OutlineDriven/outline-driven-development
Skill Claude CodeCodex
Use when a human explicitly asks to commit and push to the checked-out branch, with no branch creation and no pull request. Not for the default branch by name: use commit-push-main.
OutlineDriven/outline-driven-development
Skill Claude CodeCodex
Use when a human explicitly asks to commit and push directly to the default branch, with no feature branch and no pull request. Not for another checked-out branch: use commit-push-current.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked to commit, push a feature branch, and open or update a pull request with gh in one pass. Not for a push with no PR: use commit-push. Not for a PR body alone: use create-pull-request.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked to commit and push to a feature branch off the default branch, with no pull request. Not for a PR: use commit-push-pr. Not for the checked-out branch: use commit-push-current.
OutlineDriven/outline-driven-development
Skill Codex
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.
OutlineDriven/outline-driven-development
Skill Codex
Use when -O3 leaves a hot loop scalar, spills appear in assembly, or a PGO or BOLT deployment is planned or stalls. Not for machine lowering: use code-generation-and-backends.
OutlineDriven/outline-driven-development
Skill Codex needs its repo
Use when adding C/C++ dependencies with Conan or vcpkg, managing binary compatibility, integrating with CMake via conanfile.txt or vcpkg.json, or choosing between Conan and vcpkg.
OutlineDriven/outline-driven-development
Skill Codex
Use when reading TSan race reports, debugging deadlocks with GDB thread inspection, analyzing Helgrind lock-order violations, or reviewing std::atomic and happens-before usage.
OutlineDriven/outline-driven-development
Skill Codex
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.
OutlineDriven/outline-driven-development
Skill Codex
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.
OutlineDriven/outline-driven-development
Skill Codex
Use when working with C++20 coawait, coyield, and coreturn, implementing promisetype, sizing coroutine frames, or debugging suspended coroutines in GDB. Not for Rust async: use idiomatic-rust.
OutlineDriven/outline-driven-development
Skill Codex
Use when a C++ project adopts C++20 modules: named modules, partitions, header units, the global module fragment, CMake CXXMODULES, or a BMI lookup error. Not for flag basics: use clang.
OutlineDriven/outline-driven-development
Skill Codex
Use when a C++ template error needs decoding, a template needs a concept or requires-clause instead of SFINAE, or template instantiation is slowing compilation. Not for C++20 modules: use cpp-modules.
OutlineDriven/outline-driven-development
Skill Codex
Use when diagnosing cache misses with perf, fixing false sharing, choosing AoS or SoA layout, or adding software prefetch. Not for cache theory: use memory-hierarchy-and-caches.
OutlineDriven/outline-driven-development
Skill Codex
Use when writing, optimizing, or benchmarking a C++ CPU kernel with AVX2 or AVX512 intrinsics for the Hugging Face kernels ecosystem. Not for CUDA kernels: use cuda.
OutlineDriven/outline-driven-development
Skill Codex
Use when explaining pipeline stages, data or control hazards, forwarding, stalls, or superscalar basics behind a counter reading. Not for mispredict cost: use branch-prediction-and-speculation.
OutlineDriven/outline-driven-development
Skill Codex
Use when compiling for ARM, AArch64, RISC-V, or MIPS from x86-64 with a GCC cross toolchain: triplets, sysroots, pkg-config, CMake toolchain files, QEMU. Not for Zig: use zig-cross.
OutlineDriven/outline-driven-development
Skill Codex
Use when debugging CUDA with cuda-gdb or Compute Sanitizer, reading GPU core dumps, using device printf, or triaging error codes 700, 701, 702, and 719. Not for performance: use cuda-profiling.
OutlineDriven/outline-driven-development
Skill Codex
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.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: