kcc-direct-resource-scaffolder

Scaffolding a KCC direct resource requires providing the GCP service name and KCC Kind-to-resource mapping. The skill automates setting up the generate.sh entry under apis/<service_short>/<api_version>/ and generates the required CRD Go types.

Inconsistent CRD generation often occurs when standards are applied manually. This skill enforces required kubebuilder validation tags, standard CRD labels, and correct enum Go typing rules during the initial scaffolding to ensure consistency.

The correct path for KCC direct resource CRD generation is apis/<service_short>/<api_version>/. The skill verifies that generation.sh exists in this exact location to ensure repo tooling can generate the required types.

No, manual typing is unnecessary. The scaffolding process automatically enforces status.observedGeneration as *int64, along with required copyright text and enum typing strategies, to align with project reconciliation expectations.

No, this skill applies specifically to new direct implementations. It is designed to kick off initial scaffolding where Go types, CRD fields, and status typing must be standardized from the start.

The best way to standardize enum typing is through automated scaffolding. The skill guides you to verify enum Go typing strategy and kubebuilder validation tags during the initial CRD generation for your GCP resource.