file-organization SKILL.md skillA
file-organization from akillness/jeo-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add akillness/jeo-skills/file-organization@v2.0Pins v2.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- akillness/jeo-skills
- Path
.agent-skills/file-organization/SKILL.md- Versions recorded
- 5
- Latest version
- v2.0, committed Jul 28, 2026
- First version recorded
- Feb 11, 2026
- Size
- 13,709 bytes
- Repository stars
- 52
- License
- none declared
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…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file 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@sha256:20317f79befcde7dThe line at the top of this page pins the label v2.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_kaeyvuwgc22e2y5t)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Feb 11, 2026 and Jul 28, 2026, about one every 42 days.
| 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 · 52 stars · license none declared · pushed 2026-11-05 · 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 AI assistant 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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from akillness/jeo-skills
Every file in akillness/jeo-skills