What problem does it solve? Setting up a Kubernetes GitOps repository often leads to inconsistent folder structures, duplicated manifests across environments, and confusion between Kustomize files and Flux custom resources. This Skill enforces a predictable base/overlay layout so FluxCD reconciliation and CI validation work reliably. ## Core Features & Use Cases - Standard Layout Scaffolding: Creates the canonical kustomization/base plus overlays/dev and overlays/prod directory structure with valid kustomization.yaml files. - Manifest Organization Rules: Moves shared manifests into the base, keeps environment-specific patches, images, labels, and namespaces in the matching overlay, and keeps base manifests environment-neutral. - Validation Workflow: Inspects existing Kubernetes and Flux files before editing and validates the result with kustomize build or kubectl kustomize when available. - Use Case: When starting a new microservice deployment, ask the agent to scaffold the repo layout and it will produce a base with deployment and service resources plus dev and prod overlays referencing ../../base. ## Quick Start Use the flux-kustomize-layout skill to scaffold a FluxCD Kustomize repository layout with a shared base and dev and prod overlays for my application.
