shape
Skill0 starsChanged 4 months agoMITView on GitHub
Clarify a complex or ambiguous request before execution by establishing the real problem, outcome, audience, scope, constraints, current state, and owner. Use when acting immediately risks solving the wrong problem.
36 other projects use a version of this.
Adopted by
Most recently taken up by
- jskswamy/skillstheir own version, first seen Nov 8, 2026
- Belweave/hstacktheir own version, first seen Nov 8, 2026
- Mrbaeksang/skillstheir own version, first seen Nov 8, 2026
- edwinidrus/dragonhoardtheir own version, first seen Nov 8, 2026
- chrislacey89/skillstheir own version, first seen Nov 4, 2026
- theexperiencecompany/gaiatheir own version, first seen Nov 3, 2026
Used with
Projects with it also use layout, explore and 6 more.
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.
owshq-mecSkilllayout
Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.
Also in 8 projects that use this
genomewalkerSkillexplore
RLM-style recursive memory exploration - dynamically navigate the memory graph
Also in 3 projects that use this
Microsoft AzureSkillbuild
Build the TypeSpec Rust emitter from source. Run this after cloning the repo, after pulling changes, or when TypeScript source files have been modified.
Also in 5 projects that use this
jaydubya818Skillwhy
Use when design rationale must be recovered from source history and available records.
Also in 3 projects that use this
AWSSkillship
Finalize dev work on an issue branch — update docs, push, and open a PR.
Also in 4 projects that use this
nicolasestremSkillbrainstorm
Structured idea generation and solution exploration with systematic analysis.
Also in 3 projects that use this
Other versions36 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 36
- hoophq/hoop★ 848same name
- educlopez/ui-craft★ 441same name
- 10xChengTu/Mux0★ 337same name
- theexperiencecompany/gaia★ 325same name
- jagrat7/linux-wallpaper-engine★ 227same name
- owshq-mec/semana-ai-data-engineer★ 122same name
- StyleSwift/StyleSwift★ 61same name
- tdimino/claude-code-minoan★ 41same name
- saltandsilicon/game-theorist★ 16same name
- excatt/superclaude-plusplus★ 14same name
26 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 repository35 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- briefSkill
- closeoutSkill
- decisionSkill
- deskSkill
- doctorSkill
- editorSkill
- grillSkill
- handoffSkill
- morningSkill
- openSkill
- recentSkill
- researchSkill
- rfcSkill
- setupSkill
- specSkill
- weekly-reviewSkill
- briefSkill
- closeoutSkill
- decisionSkill
- deskSkill
- doctorSkill
- editorSkill
- grillSkill
- handoffSkill
- morningSkill
- openSkill
- recentSkill
- researchSkill
- rfcSkill
- setupSkill
- shapeSkill
- specSkill
- weekly-reviewSkill
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 34 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 16
Ask only high-impact questions that cannot be answered from available context.
“Common” is measured: kept by at least 6 in 10 of the 34 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
Shape work
Remain read-only while shaping.
- Inspect discoverable repository and binder context before asking questions.
- State the problem in plain language, why it matters, the desired outcome, audience, constraints, and known current state.
- Separate facts, assumptions, preferences, and unresolved decisions.
- Define “done” and name the owner-of-record artifact or workstream.
- Recommend the smallest appropriate next move: answer directly, research,
$grill, draft an artifact, plan implementation, or execute.
Ask only high-impact questions that cannot be answered from available context. If multiple interdependent decisions remain, route to $grill. Do not create durable state unless the user asks.
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.