file-organization skillA
file-organization is agent-read markdown (skill) from akillness/jeo-skills: Design or refactor project structure around the right boundary unit: feature, shared layer, route segment, or workspace package. Use when a repo feels scattered, a team needs naming/import conventions, or the user must choose between type-based, feature-based, framework-colocated, and workspace layouts. Triggers on: file organization, folder structure, project structure, reorganize repo, feature folders, shared vs feature code, where should this file live, apps/packages split, and project layout.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# File Organization Use this skill when the main question is **"what structural boundary should this codebase use, and how do we move toward it without turning a reorg into chaos?"** The job is not to dump a giant folder tree and pretend it fits every repo. The job is to: 1. identify the real organizing unit, 2. separate feature/shared/framework/package boundaries, 3. define naming and import rules that prevent drift, 4. plan the migration safely, 5. return a structure brief another engineer or agent can apply immediately. Read [references/boundary-decision-matrix.md](references/boundary-decision-matrix.md) before recommending a structure. Read [references/migration-checklist.md](references/migration-checklist.md) before moving files or renaming directories. Read [references/naming-and-import-rules.md](references/naming-and-import-rules.md) when the problem includes barrel files, alias paths, or team conventions. ## When to use this skill - Choose a maintainable folder strategy for a new repo or app - Refactor a repo whose `components/`, `hooks/`, `utils/`, and `store/` folders no longer match business boundaries …
Read the whole file at its exact version.
How to install
mdr add akillness/jeo-skills/file-organization@v2.0mdr add akillness/jeo-skills/file-organization@sha256:20317f79befcde7dPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_kaeyvuwgc22e2y5t)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v2.0 latest | 2026-07-28 | 4f971c4 | 13,709 B | A | view · diff |
| v2.0 | 2026-06-16 | ceeea9d | 13,721 B | A | view · diff |
| v2.0 | 2026-04-14 | 79a6cb4 | 13,723 B | A | view · diff |
| git:20260306.b04d94a | 2026-03-06 | b04d94a | 8,713 B | A | view · diff |
| git:20260211.af4d63f | 2026-02-11 | af4d63f | 8,727 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (13709 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
akillness/jeo-skills · 47 stars · license none · pushed 2026-09-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_kaeyvuwgc22e2y5t GET https://markdownregistry.com/api/v1/resolve?ref=akillness/jeo-skills/file-organization GET https://markdownregistry.com/api/v1/blob/20317f79befcde7d489ead91a1587f28740b254f672fe078bb83d1cb02041661
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.