Fengxiaoxx

为中国专利交底书生成高质量目录，适用于计算机/软件领域发明，输出符合专利法规范的七部分结构目录

Integrates newly written LibFuzzer harnesses (along with their seed corpora and dictionaries) into an existing OSS-Fuzz project, then builds and packages both AddressSanitizer (asan) and UndefinedBehaviorSanitizer (ubsan) versions, saving each to a separate backup directory so neither build is overwritten. Use this skill whenever the user wants to: - Add new fuzz harnesses to an OSS-Fuzz project - Package new harnesses using the OSS-Fuzz container workflow - Produce asan + ubsan instrumented fuzzer binaries via OSS-Fuzz - Integrate locally written drivers into an existing oss-fuzz build.sh / Dockerfile - "用oss-fuzz打包我写的harness" / "把新harness加入oss-fuzz构建" Trigger proactively whenever the user has written new .c/.cpp harnesses in a target_project directory and mentions OSS-Fuzz, packaging, or sanitizers.

Use this skill whenever the user wants to compile LibFuzzer harnesses into binaries and package them into OSS-Fuzz-compatible zip archives. Triggers on phrases like "打包 fuzz harness", "编译 fuzzer", "package fuzzers", "build fuzzers", "oss-fuzz package", "生成压缩包", "build_fuzzers", "sanitizer zip", "address sanitizer build", "memory sanitizer build", or when the user has written harness .c/.cpp files and wants to produce distributable fuzz binaries. Also trigger when the user says "模拟 oss-fuzz 产物", "simulate oss-fuzz output", or "package for fuzzing platform". Use proactively any time harnesses are ready and the user wants to compile or distribute them.

Use this skill whenever the user wants to build or compile a C or C++ library with LibFuzzer + sanitizer instrumentation as the prerequisite step before writing or running fuzz harnesses. Triggers on phrases like "build the library for fuzzing", "compile with sanitizer instrumentation", "instrument the library", "构建插桩版本", "为 fuzzing 编译库", "build_harness", "fuzzer-no-link", "asan build", "msan build", "为库插桩", or when the user asks how ASan and MSan differ in the context of fuzzing. Also trigger proactively when the user is setting up a fuzzing environment and the target library has not been built yet — this skill must run before libfuzzer-harness-writer or libfuzzer-oss-packager can proceed. Use this skill for any C/C++ library regardless of build system (CMake, autoconf, meson, make).

Generate high-quality initial seed corpora for LibFuzzer / AFL fuzz harnesses written for a C or C++ library. Use this skill whenever a user has one or more fuzz harness (.c/.cpp) files and wants to create, improve, or evaluate the seed corpus that bootstraps fuzzing. Also trigger when the user asks about "initial seeds", "seed corpus", "corpus generation", "fuzzing inputs", or says something like "the fuzzer isn't finding anything" or "how do I start fuzzing". Works with OSS-Fuzz projects and custom harnesses alike.

Use this skill whenever a user wants to write, improve, or generate LibFuzzer fuzz drivers (harnesses) for a C or C++ library. Triggers when you see words like "fuzz", "fuzzing", "harness", "fuzz driver", "libfuzzer", "afl", "oss-fuzz", "coverage", or when the user has a compiled library (.so / .a) and wants to find bugs in it via fuzzing. Also use this skill if the user asks to "improve fuzzing coverage", "add more fuzz targets", or "write libfuzzer tests". Use this skill proactively — if the user is working with a C/C++ library and mentions security or robustness testing, this skill is almost certainly relevant.

Use this skill for the complete end-to-end LibFuzzer workflow: writing harnesses, generating seeds, and building OSS-Fuzz-compatible packages — all in one go. Trigger when the user mentions doing the full fuzzing pipeline, or phrases like "从零开始对这个库进行fuzz", "complete fuzzing setup", "fuzz this library end to end", "set up fuzzing for X", "全流程", "write harnesses and package them", "prepare this library for oss-fuzz", or when the user has a C/C++ library and wants to go from source code all the way to distributable fuzz binaries. Also trigger when the user mentions two or more of: harness writing, seed generation, packaging, oss-fuzz — as this signals they want the full pipeline, not just one step. Use this skill proactively when the user's goal is to produce a complete, ready-to-deploy fuzz setup for a library, even if they only describe the end goal ("I want to fuzz libpng" / "我想对 cJSON 做模糊测试").