Reference vocabulary for designing instrumented harnesses that drive vulnerability discovery — design classes (trigger-driven vs coverage-driven), tiered scope (T1 isolated function / T2 multi-component / T3 full build), systematic input exploration, the two-coverage distinction (fuzzer-feedback vs audit), existing-fuzzer selection (libFuzzer / AFL++ / Jazzer / atheris / go test -fuzz), seed-corpus discipline, diagnostic checkpoints, common pitfalls, and design-document scope. Read when designing or reviewing a harness specification. Stays neutral on language and stack — pulls in the relevant surface skill (e.g. memory-safety-c-cpp) for bug-class taxonomy.
$npx -y skills add provos/ironcurtain --skill harness-design-fuzzingInstalls into the current project.
Run `npx skills use "https://github.com/provos/ironcurtain" --skill "provos/ironcurtain/harness-design-fuzzing"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/provos/ironcurtain" that are relevant to the current task. Run `npx skills add "https://github.com/provos/ironcurtain"` and select the relevant skills, then follow their instructions.