kcc-direct-resource-scaffolder

What problem does it solve?

Creating a new KCC direct resource can be error-prone and inconsistent across services, especially when CRD generation, kubebuilder validation tags, and reconciliation expectations must match project standards.

Core Features & Use Cases

• Automated scaffold setup: Ensures the correct generate.sh entry exists under the expected apis/<service_short>/<api_version>/ path for direct resource development.
• Deterministic type generation: Runs the repo tooling to generate CRD types and related artifacts from the specified Google API service and KCC resource mapping.
• Validation-focused hardening: Guides you to verify standard copyright text, CRD labels, kubebuilder validation tags, enum typing strategy, and status.observedGeneration typing.
• Use case: Kick off a new “direct” implementation for a GCP resource when you need CRDs and code generation to align with validation and reconciliation patterns used across the project.

Quick Start

Use this skill to scaffold a new direct resource for the Google API service you are implementing by providing the service name, the KCC Kind-to-GCP resource mapping, and (optionally) the KCC API version.