organize-repository
Decide where code, tests, docs, scripts, config, generated files, and knowledge (notes, research, captured sources) belong, so placement and names stay predictable across projects instead of being re-decided each time. Use when starting a repository or knowledge store, saving something whose home is not obvious, adding a documentation site such as Mintlify, moving, retiring, or reorganizing files, auditing a layout for drift, or writing layout rules into AGENTS.md. Not for choosing application architecture or dependency boundaries.
Pinned to revision 9702033b2178, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/organize-repository/SKILL.md
- skills/organize-repository/references/documentation-sites.md
- skills/organize-repository/references/knowledge-store.md
- skills/organize-repository/references/moving-files.md
- skills/organize-repository/references/profiles.md
- skills/organize-repository/scripts/check_knowledge_store.py
- skills/organize-repository/scripts/check_layout.py
Every link opens the file at its source, pinned to the revision this page describes.