repo-structure
Canonical source layout, test mirroring, root cleanliness, gitignore, docs classification, and committed artifact rules for all workspace-hub tier-1 repos. Consult before creating directories or files in any submodule.
Best use case
repo-structure is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Canonical source layout, test mirroring, root cleanliness, gitignore, docs classification, and committed artifact rules for all workspace-hub tier-1 repos. Consult before creating directories or files in any submodule.
Teams using repo-structure should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/repo-structure/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How repo-structure Compares
| Feature / Agent | repo-structure | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Canonical source layout, test mirroring, root cleanliness, gitignore, docs classification, and committed artifact rules for all workspace-hub tier-1 repos. Consult before creating directories or files in any submodule.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Repo Structure ## Sub-Skills - [Tier Classification (Determines Which Rules Apply)](tier-classification-determines-which-rules-apply/SKILL.md) - [Canonical Structure (+1)](canonical-structure/SKILL.md) - [Allowed at Repo Root (+2)](allowed-at-repo-root/SKILL.md) - [Gitignore Enforcement: Root-Level Output Artifacts](gitignore-enforcement-root-level-output-artifacts/SKILL.md) - [Allowed in docs/ (+1)](allowed-in-docs/SKILL.md) - [Agent Infrastructure Rules](agent-infrastructure-rules/SKILL.md) - [Compliance Quick-Check](compliance-quick-check/SKILL.md) - [NEVER: tests/ inside src/ (+7)](never-tests-inside-src/SKILL.md) - [See Also](see-also/SKILL.md) ## Iron Law > No file or directory shall be created outside the canonical structure without consulting this skill first — ever. ## Rationalization Defense | Excuse | Reality | |--------|---------| | "I just need a quick temp directory at the root" | Root-level clutter is permanent. Use the canonical location or it does not get created. | | "Tests next to source files are easier to find" | Tests inside src/ is an explicit NEVER rule (+7 violations tracked). Use the tests/ mirror. | | "This output file is small, no need for .gitignore" | Committed artifacts accumulate. If it is generated, it belongs in .gitignore, regardless of size. | | "The user didn't specify where to put this" | That is exactly when you consult repo-structure. Silence is not permission to improvise. | ## Red Flags These phrases signal you are about to violate the Iron Law: - "I'll just put this here for now" - "it doesn't matter where this file goes" - "this is a temporary file" - "the existing structure doesn't have a place for this" - "tests/ is too far from the code"
Related Skills
interactive-report-generator
Generate interactive HTML reports with Plotly visualizations from data analysis results. Supports dashboards, charts, and professional styling.
data-validation-reporter
Generate interactive validation reports with quality scoring, missing data analysis, and type checking. Combines Pandas validation, Plotly visualization, and YAML configuration for comprehensive data quality reporting.
repo-ecosystem-hygiene
Interpret the daily read-only repo ecosystem hygiene audit and route remediation through approved workflows.
orcaflex-reporting-fixture-proof-pattern
Build and extend fixture-backed OrcaFlex reporting proof paths in digitalmodel using stable metadata baselines, normalized HTML snapshots, and reusable reporting test helpers.
repo-sync
Smart repository synchronization across workspace-hub ecosystem — diagnoses and fixes pull failures (detached HEAD, diverged branches, uncommitted changes)
repo-portfolio-steering
Generate a one-page portfolio steering report for workspace-hub. Use when the user invokes /repo-portfolio-steering, asks about harness vs engineering balance, wants a portfolio health check, or asks which repos to fund next. Reports on portfolio steering, GTM readiness, and provider activity balance.
repo-mission-portfolio-audit
Audit the workspace-hub repo portfolio to extract each repo's mission, identify documentation gaps, and prioritize a plan/approval sequence with explicit LLM-wiki weighting for future issue triage.
mixed-ops-vs-repo-fix-plan-boundary
Plan mixed operational-vs-repo remediation issues by proving live-state classification first, then only proposing code changes for confirmed repo-owned failure paths.
repo-separation-for-sensitive-data
Architecture pattern for splitting confidential data and reusable algorithms across repos
nested-git-repo-stash-safety
How to safely stash changes in a parent repo containing dirty nested git repositories
multi-repo-sync-diagnosis-repair
Diagnose and repair failed pulls across multi-repo ecosystems with stale locks, submodule conflicts, and untracked files
multi-repo-sync-diagnosis-and-repair
Systematic approach to diagnosing and repairing failures across a multi-repo workspace