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 a visual needs repeatable fixed-view rendering and independent rubric scoring: render the fixed view through a specified interface, score it against a frozen rubric, and prove the saved render clears the threshold. Not for free-form visual review or subjective critique.
OutlineDriven/outline-driven-development
Skill Codex
Use when a rendering path needs stable frame-time, CPU, GPU, and memory evidence against fixed targets: stabilize the configuration, define a sampling window, and prove every target with two consecutive comparable runs. Not for one-shot profiling or visual quality review.
OutlineDriven/outline-driven-development
Skill Codex
Use when a user suspects the current direction is tunnel-visioned or inherited its framing: spawn 2-5 independent reads, classify each, cluster by shared root, and surface divergent-incompatible reads first. Not for framing-bias checks on a question — use prism.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked to cold-read an artifact with fresh zero-context eyes and cut whatever a stranger cannot follow. Dispatches blind sub-sessions that read only the inline artifact, compares their understanding against a private intent note, and reports severity-ordered defects. Not for criteria-review of requirements…
OutlineDriven/outline-driven-development
Skill Codex
Use when a user wants an answer only from the breaking seat (stakeholders, dependencies, accounting, compatibility under destructive pressure). A breaking-perspective answer is emitted without blending. Not for any other from- lens seat or multi-lens synthesis.
OutlineDriven/outline-driven-development
Skill Codex
Use when the user wants an answer only from the business seat, to produce a business-perspective analysis of money, customers, and timing without blending other lenses. Not for any other from- lens seat or multi-lens synthesis.
OutlineDriven/outline-driven-development
Skill Codex
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.
OutlineDriven/outline-driven-development
Skill Codex
Use when configuring ADC sampling time, DMA-driven ADC, calibration, or DAC channel setup on bare-metal MCUs. Not for the DMA stream itself: use dma-baremetal.
OutlineDriven/outline-driven-development
Skill Codex
Use when creating AFXDP sockets, configuring UMEM and XSK rings, writing an XDP redirect program, or choosing copy versus zero-copy mode. Not for full kernel bypass: use dpdk.
OutlineDriven/outline-driven-development
Skill Codex
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.
OutlineDriven/outline-driven-development
Skill Codex
Use when writing or porting AArch64 SIMD to SVE or SVE2: armsve.h intrinsics, predicates, vector-length-agnostic loops, auto-vectorization, or SVE registers in GDB. Not for NEON: use simd-intrinsics.
OutlineDriven/outline-driven-development
Skill Codex
Use when reading or writing AArch64 or AArch32 Thumb assembly, inline asm in C, AAPCS64 register roles, or NEON and SVE vector code. Not for ABI detail across ISAs: use abi-and-calling-conventions.
OutlineDriven/outline-driven-development
Skill Codex
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.
OutlineDriven/outline-driven-development
Skill Codex
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.
OutlineDriven/outline-driven-development
Skill Codex
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.
OutlineDriven/outline-driven-development
Skill Codex
Use when writing Bazel BUILD files with cclibrary or ccbinary rules, Bzlmod dependencies, toolchain registration, remote execution, sandbox debugging, or bazel query and cquery graphs.
OutlineDriven/outline-driven-development
Skill Codex
Use when enabling RELRO, PIE, stack canaries, FORTIFYSOURCE, CET, CFI, or seccomp filters, or checking a binary with checksec. Not for runtime sanitizer builds: use sanitizers.
OutlineDriven/outline-driven-development
Skill Codex
Use when building static archives with ar, stripping or converting binaries, mapping crash addresses with addr2line, or demangling C++ symbols. Not for ELF analysis: use elf-inspection.
OutlineDriven/outline-driven-development
Skill Codex
Use when writing a custom bootloader, jumping to application code, relocating VTOR, or implementing DFU/USB firmware update on Cortex-M. Not for reset-to-main: use baremetal-startup.
OutlineDriven/outline-driven-development
Skill Codex
Use when C or C++ code needs memory-safety or undefined-behavior guarantees proved with CBMC, or ACSL contracts checked with Frama-C Eva or WP. Not for choosing the proof policy: use proof-driven.
OutlineDriven/outline-driven-development
Skill Codex
Use when explaining branch predictors, mispredict penalties, speculative execution, Spectre or Meltdown mitigations, or branchless code. Not for pipeline stage theory: use cpu-pipelines-and-hazards.
OutlineDriven/outline-driven-development
Skill Codex
Use when reducing C/C++ compilation times with ccache, sccache, distcc, unity builds, precompiled headers, split DWARF, IWYU, or link time reduction.
OutlineDriven/outline-driven-development
Skill Codex
Use when writing a Linux i2cdriver or spidriver, doing bus register access, DMA-safe SPI transfers, or debugging -EREMOTEIO. Not for MMIO platform drivers: use platform-device-model.
OutlineDriven/outline-driven-development
Skill Codex
Use when C code is written or audited and needs a pure-C baseline: standard, undefined behavior, integer and buffer safety, sanitizers, fuzzing, build flags. Not for C++: use modern-cpp-practices.
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: