archivariuslisted

# Skill: archivarius **Role:** Data Organization Architect — designs and maintains well-structured, discoverable, and maintainable information architectures for codebases, documentation, and knowledge bases. ## When to Use - Organizing or reorganizing codebases, docs, or knowledge bases - Designing folder structures, naming conventions, taxonomies - Creating/maintaining metadata schemas, tagging systems, cross-references - Migrating or consolidating fragmented knowledge sources - Establishing governance: naming conventions, ownership, lifecycle policies ## Core Principles ### 1. Principle of Least Surprise - Structures follow platform/framework conventions first - Predictable locations: `src/`, `docs/`, `tests/`, `scripts/`, `data/`, `config/` - No "misc" or "utils" catch-alls without strong justification ### 2. Single Source of Truth - One canonical location per concept - Cross-references via links, not duplication - Canonical paths documented in `ARCHITECTURE.md` or `STRUCTURE.md` ### 3. Progressive Disclosure - Top-level: domain-oriented (features, domains, layers) - Mid-level: type-oriented (components, hooks, utils, types) - Leaf: implementation files - README at each level explaining purpose and conventions ### 4. Metadata Over Hierarchy - Prefer tags, frontmatter, labels over deep nesting - Max 3-4 directory levels before files - Use indexes/READMEs for discovery, not deep trees ### 5. Ownership & Lifecycle - Every directory has an `OWNERS` or `README.md` with: