What problem does it solve? New files in a multi-component Go monorepo often arrive with scaffolded license headers, missing opening comments, wrong directory placement, or stale generated artifacts, causing lint failures and CI drift. This Skill codifies the repository's rules so every new file starts correctly. ## Core Features & Use Cases - Header and opening-comment rules: Prohibits license headers, copyright lines, and SPDX identifiers on new files, and requires an opening comment stating what the file contains and why it exists, with per-language mechanics for Go, Python, shell, YAML, Makefile, and Markdown. - Placement and regeneration guidance: Maps each file type (CRD types, reconcilers, atlas-lib primitives, CSI logic, Helm templates) to its correct directory and lists the exact make targets to regenerate manifests, deepcopy code, and Helm chart syncs. - Use Case: When scaffolding a new CRD kind with kubebuilder, use this Skill to strip the injected Apache header, write the opening comment, hand-wire the kustomization and main.go registration, and run make -C operator manifests generate plus make helm-sync before committing. ## Quick Start Use the new-files skill to review the Go file I just created and tell me what to fix before committing it.
