layout
Skill2 starsChanged 19 days agoMITView on GitHub
Decide where a file, artifact, run or branch goes and what to name it, or reorganize a messy folder with named, reversible moves.
14 other projects use a version of this.
Adopted by
Most recently taken up by
- fracazo/design-systemtheir own version, first seen Nov 8, 2026
- theexperiencecompany/gaiatheir own version, first seen Nov 3, 2026
- vijaysuperpositionist/skillstheir own version, first seen Nov 1, 2026
- The-Utopia-Studio/skillstheir own version, first seen Oct 13, 2026
- excatt/superclaude-plusplustheir own version, first seen Oct 13, 2026
- IamK77/Skilltheir own version, first seen Oct 12, 2026
Used with
Projects with it also use motion and accessibility.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
leonaaardobSkillmotion
Complete Motion.dev documentation - modern animation library for React, JavaScript, and Vue (formerly Framer Motion)
Also in 3 projects that use this
ElasticSkillaccessibility
Accessibility guidance for Kibana. Use this skill when working with or reviewing EUI components, resolving a11y-related (@elastic/eui) ESLint issues, and ensuring proper use of ARIA attributes, focus management, keyboard interactions, and accessible naming conventions.
Also in 3 projects that use this
Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 14
- 10xChengTu/Mux0★ 337same name
- theexperiencecompany/gaia★ 325same name
- owshq-mec/semana-ai-data-engineer★ 122same name
- StyleSwift/StyleSwift★ 61same name
- excatt/superclaude-plusplus★ 14same name
- The-Utopia-Studio/skills★ 6same name
- fracazo/design-system★ 4same name
- moasq/ios-dev-agent★ 4same name
- tyfarrago-hub/taste★ 3same name
- IamK77/Skill★ 2same name
4 more not listed
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 repository10 other files it gives its agents.
- cards-readmeSkill
- cleanupSkill
- deepsearchSkill
- engineer-mindsetSkill
- grill-meSkill
- investigateSkill
- presentSkill
- review-prSkill
- sentry-cliSkill
- toolchainSkill
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 14 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 8
Use the existing repository layout first.
“Common” is measured: kept by at least 6 in 10 of the 14 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
Layout
Use the existing repository layout first. Keep scratch/generated files out of its root. Names should sort and be searchable: date first for dated artifacts, hyphens inside words, underscores between fields; no final/v2/new-copy names.
Place project code/config/tests/docs in the repo. Put expensive non-project-curated results in the user's durable artifact location and add a pointer to the artifact index; MEMORY holds one link to that index. Temporary work is for reproducible intermediates, never the only copy of costly results. A run's log stays with its outputs.
- Creating a normal file: follow its neighbors and the closest instructions; no additional reference needed.
- Naming a branch, experiment/run or durable artifact: read naming and storage for the relevant convention.
- Designing docs/spec/report or experiment directory structure: read directory conventions, only the relevant section.
- Starting a new repo or organizing a messy folder: read organizing and the matching skeleton if useful. An established project keeps its own skeleton.
For reorganization, inspect status and boundaries and show from/to/reason for each move. Unrelated work stays where it is; archive named targets when appropriate. Moves the user explicitly requested go ahead without a second confirmation.
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.