project-structure-governance
Skill0 starsChanged 2 months agoMITView on GitHub
Define, initialize, locate, and audit the canonical structure of a software repository, including source code, tests, scripts, configuration, documentation, assets, automation, generated output, and runtime files. Use when Codex needs to scaffold a project, decide where a new file belongs, name a repository-owned artifact, inspect or reorganize a repository, add a new project directory, or give another agent an authoritative directory index.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- farfarfun-skills/farfarfun--project-managerword for word, first seen Sep 16, 2026
Other versions1 project uses a version of this.
Word for word · 1
- farfarfun-skills/farfarfun--project-manager★ 0100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository2 other files it gives its agents.
- github-repo-standardsSkill
- project-managerSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Treat repository structure as an interface shared by people, tools, and agents.
- Very specific: line 12
Read project-layout.json before creating or moving a file.
- Very specific: line 14
Read the target repository's .project-structure.json next.
- Distinctive: line 20
Stop and extend the index when no rule owns the file.
- Distinctive: line 22
Read project-structure-standard.md when classifying an unfamiliar file, choosing a name, or changing the index.
- Distinctive: line 23
Read document-bundle-standard.md before creating or reorganizing PRD, design, development, testing, release, or retrospective artifacts.
- Distinctive: line 27
Run from this skill directory:
- Very specific: line 47
Use --format json for machine consumption.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Project Structure Governance
Treat repository structure as an interface shared by people, tools, and agents. Govern file placement and naming; leave product, architecture, and content-quality decisions to their owning workflows.
Resolve A Path
Read project-layout.json before creating or moving a file. Use its zones and artifact patterns as the global index.
Read the target repository's .project-structure.json next. It selects one or more technology profiles and records project-specific zones or root files. Apply rules in this order:
- Determine whether the file belongs to one registered application, a shared package, or the repository as a whole.
- For application-owned code, resolve the registered
apps/<name>path before applying that application's profiles. - Preserve paths required by the selected framework or build tool inside that ownership boundary.
- Apply the repository manifest's explicit additions, then the global baseline and artifact index.
- Stop and extend the index when no rule owns the file; do not invent an arbitrary directory.
Read project-structure-standard.md when classifying an unfamiliar file, choosing a name, or changing the index. Read document-bundle-standard.md before creating or reorganizing PRD, design, development, testing, release, or retrospective artifacts. Require the total-part directory structure and three-digit chapter numbering defined there.
Initialize A Repository
Run from this skill directory:
python3 scripts/project_structure_bootstrap.py --workspace /path/to/repoUse repeatable --profile options for a single root application. The initializer automatically discovers existing direct children of apps/ and their profile markers. For a new multi-application repository, use --application web=node --application api=go; this selects the root monorepo profile and creates each profile's structure under apps/<name>. Record custom Owner and Purpose values in the generated manifest, then rerun the initializer to synchronize the application table in docs/project/project-overview.md. Keep shared libraries in packages/<name> rather than registering them as applications.
Supported profiles are generic, node, python, go, rust, java, dotnet, ruby, php, flutter, and monorepo; generic cannot be combined. The command creates baseline/profile directories, .project-structure.json, docs/project/project-overview.md, and a managed .gitignore baseline while preserving existing content. Use --dry-run to inspect the plan, --no-gitignore to leave ignore rules unmanaged, and --keep-empty when initialized empty directories must be committed.
Existing version 1 or 2 manifests and profile/application changes require --migrate; never migrate them implicitly.
Audit A Repository
Run:
python3 scripts/project_structure_checker.py --workspace /path/to/repoUse --format json for machine consumption. Use --fail-on revise or --fail-on block in CI. Treat automated language detection as a baseline and inspect substantial project documentation manually.
Before changing an existing repository, inspect current framework conventions and references. In a multi-application repository, audit every direct child of apps/ against applications and verify that every application appears in the project overview table. Do not move framework-required paths merely to match the generic profile; record legitimate exceptions in .project-structure.json.
Extend The Structure
Register a new independently deployable unit in applications; do not model it as an additional_zones entry. Put a genuinely shared library in packages/<name>. For any other project-only path, add a narrowly scoped additional_zones or allowed_root_files entry to .project-structure.json. For a reusable path, update references/project-layout.json, the standard when policy changes, and checker tests in the same change. Every application and zone must state one owner and one purpose.
Return Results
Return allow, revise, or block. Include exact offending paths, their classification, and concrete target zones. State when a target requires owner confirmation instead of guessing.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

