compfuzor

What problem does it solve?

This Skill solves the pain of inconsistent, hard-to-maintain compfuzor playbooks and subsystems that ignore project conventions, leading to duplicated logic, brittle deployments, and hours of unnecessary debugging and rework.

Core Features & Use Cases

• Standardized Conventions: Defines non-negotiable mental models, naming rules, and artifact taxonomies (ETC_FILES, BINS, ENV) to ensure all compfuzor implementations follow a consistent, inspectable contract.
• Subsystem Design Guidance: Teaches the data-first generator pattern, ordered domain tables, and file-backed script best practices to build reusable, maintainable subsystems that reduce custom task code.
• Legacy Modernization: Provides step-by-step migration guidance to update old playbooks to current compfuzor conventions without losing critical functionality like rerunnable generated scripts and instance multiplicity.
• Use Case: A DevOps team managing dozens of compfuzor playbooks for kernel and subsystem deployments can use this Skill to standardize all implementations, cut custom task code by over half, and make playbooks easy to scan and debug in a single screenful.

Quick Start

Use the compfuzor skill to review your existing subsystem playbook, identify 3 changes to align it with the standard pipeline shape and artifact taxonomy, then implement those changes to reduce custom task code and improve maintainability.