菜单
Automate the initial scaffolding of a KCC "direct" resource, including CRD types and generation scripts. Use this when starting a new "direct" implementation for a GCP resource.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Creates or updates the _identity.go and _reference.go files for a Config Connector resource, ensuring they follow the canonical gcpurls.Template pattern. Use this when you need to make sure the identity and reference is up to date for a KCC resource or when implementing IdentityV2 and refs.Ref for a resource.
Standards and workflows for creating direct KRM Go types for an existing CRD while maintaining strict schema compatibility.
Comprehensive review guide and criteria for PRs adding or modifying features in legacy resources (TF patches, DCL patches, CRD changes, MockGCP alignment, and Direct Controller alignment).
Implement the controller, mappers, and fuzzer for a direct KCC resource, ensuring package isolation and CI compliance. Use this when implementing the main reconciliation logic for a "direct" resource.
Guides modifying, patching, and updating resources and fields managed by the Terraform/legacy controller, including patching the local/vendored Terraform Google Beta provider.
Guides the implementation of export support for a direct controller, including implementing AdapterForURL and verifying it through the unified test runner.
| name | kcc-direct-greenfield-types-implementer |
| description | Automate the initial scaffolding of a KCC "direct" resource, including CRD types and generation scripts. Use this when starting a new "direct" implementation for a GCP resource. |
This skill guides the initial scaffolding of new (greenfield) KCC "direct" resources, ensuring standardized CRD generation and adherence to project-wide validation patterns.
You must also apply the standards from the base skill: .gemini/skills/kcc-direct-base-types-implementer/SKILL.md.
service: The Google API service name (e.g., google.cloud.aiplatform.v1).resource: The mapping of KCC Kind to GCP Resource (e.g., VertexAIExampleStore:ExampleStore).api_version: The KCC API version (default: v1alpha1).Locate apis/<service_short>/<api_version>/generate.sh. If it doesn't exist, create it following the standard KCC template:
#!/bin/bash
set -e
go run ../../../tooling/main.go generate-types \
--service <service> \
--api-version <group>.cnrm.cloud.google.com/<api_version> \
--resource <resource>
Run the generate.sh script.
Apply the baseline validations from kcc-direct-base-types-implementer, plus these greenfield-specific rules:
// +kubebuilder:metadata:labels="cnrm.cloud.google.com/stability-level=alpha".// +kubebuilder:validation:Required for fields that are mandatory in the GCP API.// +kubebuilder:validation:Optional for all other fields.*string for the Go type of proto enum fields (do NOT use custom wrapped string types).// +kubebuilder:validation:Enum=VALUE1;VALUE2 to provide validation in the CRD while keeping the Go type simple.Append any quirks about the proto-to-struct mapping (e.g., field name collisions) to .gemini/journals/<service>.md using the format described in the kcc-agentic-journaler skill.