kcc-direct-controller-implementer

What problem does it solve?

It solves the challenge of implementing direct Config Connector (KCC) reconciliation logic safely and consistently while avoiding Go package symbol collisions and ensuring CI-ready generated artifacts.

Core Features & Use Cases

• Package-isolated controller implementation: Ensures all controller, mapper, and fuzzer logic lives in the provided isolated package_path so generated code does not collide across resources.
• Correct reference mapping and update behavior: Implements and validates mapper.generated.go plus manual mappers, using the standard Ref pattern, and supports correct update-mask generation for direct resources.
• End-to-end quality gates for CI: Runs generation and last-mile checks (including fuzzing, e2e scaffolding fixtures, CRD template tests, and API field coverage) and commits resulting changes.

Quick Start

Use the kcc-direct-controller-implementer skill to implement the direct KCC controller, mappers, and fuzzer for your resource kind by working inside the isolated package directory, then run the repository generation and CI validation steps so all required artifacts and reports are updated.