Help us improve
Share bugs, ideas, or general feedback.
From nuclear-grade
Designs clean folder/file layouts from work breakdowns or existing trees, grouping by change cohesion and disposition. Use when laying out a repo, deciding where a file belongs, or fixing a junk-drawer folder.
npx claudepluginhub flyfission/nuclear-grade-context-engineering --plugin nuclear-gradeHow this skill is triggered — by the user, by Claude, or both
Slash command
/nuclear-grade:organizing-project-foldersThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Folders are a real engineering decision, not an afterthought. Each folder is a choice about what to group. A good folder maps to one piece of the work breakdown or one disposition rule (what eventually happens to its contents: kept, temporary, archived, or generated). It holds things that change together. In other words, it has high cohesion (its contents share one reason to change) and low cou...
Detects repository directory conventions, audits file placement, and moves files with import-path updates. Never changes code inside files.
Organizes project folders with a standard research skeleton (data, src, models, results, figures, docs, paper, etc.) and enforces DAG-based data flow, immutable raw data, and DVC versioning. Use when scaffolding new projects or restructuring existing ones for reproducibility.
Sets up project directories and organizes artifacts (specs/, scripts/, notebooks/) when starting or resuming work, and associates PLAN.md with a project folder.
Share bugs, ideas, or general feedback.
Folders are a real engineering decision, not an afterthought. Each folder is a choice about what to group. A good folder maps to one piece of the work breakdown or one disposition rule (what eventually happens to its contents: kept, temporary, archived, or generated). It holds things that change together. In other words, it has high cohesion (its contents share one reason to change) and low coupling (it does not depend tightly on other folders). Its name is safe on any platform, sorts cleanly, and is easy for tools to read.
This skill puts a folder-decision checklist in front of the agent, so folders get reasoned about instead of created by default. When the structure is a step-by-step agent workflow, it also applies the Model Workspace Protocol: numbered stage folders, a context file per stage, layered context, and review gates between stages.
choosing-what-to-control, checking-release-readiness, and vetting-outside-code-and-models.templates/standard/wbs.md or a wbs.md) when there is one. Otherwise the scope, which you will break down in reverse.breaking-down-the-work.01_..., 02_...). Each stage has a context file with Inputs, Process, and Outputs. Keep lasting reference material separate from each run's working output. Scripts do the mechanical work. Every output is something you can open and edit, with a human review gate at each boundary.NN_ (a zero-padded number then an underscore, as in 01_research), where the underscore marks the sequence boundary. Files that are normally capitalized by convention (README.md, LICENSE, and Model Workspace Protocol context files such as CONTEXT.md and CLAUDE.md) are an accepted exception to the lowercase rule. Ban junk-drawer names (misc, stuff, tmp, new, old, backup, final, bare utils).README.md and CONTEXT.md), uses the chosen word separator (with the Model Workspace Protocol NN_ stage prefix excepted), uses ISO-8601 dates, has one dot, and has no spaces or special characters.recording-a-known-good-version).breaking-down-the-work when there is no breakdown to build from.misc, utils, temp, or stuff folders, or folders holding one unrelated file each.README.md, CONTEXT.md).This skill is an original software workflow influenced by public folder-as-architecture and records-management practice: the Model Workspace Protocol (Van Clief and McDermott, "Interpretable Context Methodology", arXiv:2603.16021; numbered stage folders, layered context, stage contracts, review gates), NARA Bulletin 2015-04 and NIST file-naming guidance (platform-safe naming, ISO-8601 dates, depth and path limits, folder-to-disposition mapping), the DOE Work Breakdown Structure Handbook (common element structures), and Unix-pipeline and modular-decomposition principles encoded as original workflow, all mapped in docs/00-standards-foundation/source-map.md. It does not create compliance, formal assurance, certification, or regulatory adequacy.