structural-refactor
Skill116 starsChanged 7 months agoMITView on GitHub
Project structural organization rules for Bun/TypeScript CLI. Proactively scans for organizational issues and produces a prioritized plan. Defines file, folder, and module structure preferences.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- wilfreud/skills-or-somethingtheir own version, first seen Aug 19, 2026
- rolandbrecht/agent-skillstheir own version, first seen Aug 13, 2026
- Bot2353/skillstheir own version, first seen Aug 3, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- rolandbrecht/agent-skills★ 4same name
- wilfreud/skills-or-something★ 2same name
- Bot2353/skills★ 0same name
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 repository6 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- patternsSkill
- prompt-authorSkill
- prompt-evaluateSkill
- stylistic-refactorSkill
- sync-upstreamSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 30
Write the refactoring plan to docs/structural-refactor-plan.md.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Structural Refactor
Scan the codebase for organizational issues based on these structural rules. Each rule has a reference file with rationale, examples, and exceptions.
Rules
| Rule | Summary (one line) | Reference |
| Flat by Default | Keep src/ flat; group into subdirectories only when 3+ files share a concern | details |
| Soft 300-Line Limit | Implementation files should stay under 300 lines; split when single-domain logic exceeds it | details |
| Test Co-location | Unit tests next to source (file.test.ts); integration/e2e tests also in src/ | details |
| Centralized Types | All domain types/interfaces/enums in types.ts; no local type definitions | details |
| No Barrel Exports | No index.ts re-export files; always import directly from the source module | details |
| Prompt Domain Organization | Prompts organized by domain concept (axis/modifier), not by implementation | details |
| kebab-case Files | All source files use kebab-case; test files use {source}.test.ts suffix | details |
Output
Write the refactoring plan to docs/structural-refactor-plan.md.
The document should be a prioritized refactoring plan with these sections:
High Value
Implement-ready entries with file paths, current layout, target layout, and acceptance criteria.
Worth Considering
Valid reorganizations with moderate impact. Brief entries with paths and rationale.
Not Worth It
Code that technically violates a rule but should NOT be reorganized, with explanation why.
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.