repository-structure-governance

Repository Structure Governance

Purpose

Decide where each generated file lives and validate it before any code is written. This skill embeds the project's complete file/folder structure and naming rules — no external guideline lookup required.

Core Principles

• Naming signals intent. Casing tells you what a thing is before you open it — PascalCase = component/type/service, camelCase = hook, SCREAMING_SNAKE_CASE = constants.
• Location signals ownership. Every file lives in exactly one place reflecting who owns it and why.
• Structure is enforced, not optional. Naming and placement are backed by ESLint and CI. Violations fail linting, not just review.
• When in doubt, match the nearest existing example.

1. Ownership Resolution (Do This First for Every File)