setup-repository-guidelineslisted

# Setup Repository Guidelines This skill is **not** mandatory for every task. Invoke it only when: - the user explicitly requests repository-guideline setup, or - you are starting work on a completely new project that has no existing `AGENTS.md` or repository guidelines. Do not invoke it for ordinary software tasks in repositories that already have guidelines in place. ## Determine scope dynamically 1. Resolve the current Git root and repository basename. 2. Locate `installation_scripts/scripts/repository_manifest.sh` either in the current repository or in a sibling checkout under the same projects folder. 3. Source that manifest in a Bash subprocess and read `CLONE_REPOS`. The current repository is in scope when its basename is `installation_scripts` or occurs in that array. 4. Do not maintain a copied repository-name list in this skill. New repositories added to `CLONE_REPOS` must trigger this guidance automatically. 5. If the current repository is not in scope, stop applying this skill. ## Route before editing - Read `installation_scripts/AGENTS.md`, `DEPENDENCIES.md`, and the current repository's own `AGENTS.md` before editing. - Implement each concern in its owning repository. Update the orchestrator only for membership, ordering, aggregate selection, or setup-chain documentation. - Inspect all affected sibling repositories; a feature may span several owners. ## Integrate every installed feature - A user-visible feature is incomplete until i