code-structure
Skill2 starsChanged 6 months agoNo licenceView on GitHub
Use this skill whenever you're designing or refactoring backend code architecture — especially when multiple workflows duplicate operational logic, when deciding what belongs in actions vs shared services, when extracting repeated blocks across domain flows, or when adding features that share mechanics with existing ones. Trigger this skill for questions like "where should this logic live?", "how do I avoid copy-pasting this?", "should this be a service?", "how do I structure this new feature?", or any time someone is untangling messy action/handler files. Also use when reviewing PRs for architectural smells like god services, leaky services, or over-abstraction.
- Reads credentials
16 other projects use a version of this, 12 of them edited.
Adopted by
Most recently taken up by
- NemesLaszlo/claude-code-harnessedited, first seen Nov 8, 2026
- kellykampen/agent-skillsedited, first seen Nov 1, 2026
- vijaysuperpositionist/skillsedited, first seen Nov 1, 2026
- michaelshimeles/rstackedited, first seen Nov 1, 2026
- jars-demo/jars-skillstheir own version, first seen Oct 25, 2026
- Rajveerx11/skillstheir own version, first seen Oct 25, 2026
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 12
- michaelshimeles/rstack★ 1.4k31% same
- michaelshimeles/skills★ 1.4k31% same
- The-Utopia-Studio/skills★ 648% same
- jaydubya818/MissionControl★ 230% same
- kellykampen/agent-skills★ 248% same
- voundbrand/overnight★ 247% same
- Nagacash/nagacodex-factory-skill★ 148% same
- NemesLaszlo/Agent-Collection★ 141% same
- NemesLaszlo/claude-code-harness★ 141% same
- IcodeNet/agent-skills★ 048% same
2 more not listed
Wrote their own version · 4
- Spardutti/claude-skills★ 3same name
- rikvanriel/code-hygiene★ 2same name
- Rajveerx11/skills★ 1same name
- jars-demo/jars-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 repository5 other files it gives its agents.
- greploopSkill
- opensrcSkill
- qwegle-project-managerSkill
- qwegle-skillsSkill
- designerSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 9 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 16 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.
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.