What problem does it solve? Security researchers need a structured methodology to find memory-safety and logic bugs in parsers, kernels, drivers, and runtimes, but choosing fuzzers, writing harnesses, and triaging crashes correctly is error-prone without deep tooling knowledge. ## Core Features & Use Cases - Fuzzer Selection & Setup: Compares BlackBox, GreyBox, Snapshot, WhiteBox, and Ensemble fuzzing with concrete build commands for AFL++, libFuzzer, Honggfuzz, syzkaller, and wtf. - Harness & Corpus Engineering: Provides persistent-mode harness templates (HF_ITER, __AFL_LOOP), seed corpus minimization with afl-cmin/afl-tmin, and sanitizer oracle selection (ASan, MSan, TSan, KASAN, KCFI). - Specialized Targets: Covers Linux kernel fuzzing with syzkaller, Windows EDR/mpengine snapshot fuzzing, Rust pipelines (cargo-fuzz, Miri, loom), and binary-only targets via QEMU, Nyx, and LibAFL. - Use Case: A researcher auditing a file parser builds an AFL++ CmpLog target, runs a parallel campaign with a dictionary, then minimizes, symbolizes, and buckets the resulting crashes for reporting. ## Quick Start Help me set up an AFL++ fuzzing campaign with a persistent harness and seed corpus for my C++ file parser target.