how
Skill7 starsChanged 34 days agoMITView on GitHub
Use for \"how does X work\", code walkthroughs before changing something, and placement, ownership, or layering questions. Explains subsystem architecture, runtime flow, and onboarding mental models. Use why for motivation.
98 other projects use a version of this, 51 of them edited.
Adopted by
Most recently taken up by
- shiwenbin1617/pstackedited, first seen Nov 16, 2026
- therealtinhtute/mono-harnesstheir own version, first seen Nov 15, 2026
- pantheon-org/tekhnetheir own version, first seen Nov 15, 2026
- backnotprop/pstackedited, first seen Nov 15, 2026
- sammyjoyce/prime-pstackedited, first seen Nov 15, 2026
- pronvis/skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use ketchup-video, poteto-help and 2 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.
tristanphvnSkillketchup-video
Catch the user up like /keel:ketchup, with a short silent video of slides for what happened and the waiting calls as text under it. Use for /keel:ketchup-video.
Also in 13 projects that use this
ianclearySkillpoteto-help
Guides users through pstack setup, /poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help with a question.
Also in 14 projects that use this
eryzerzSkillmake-bot-ui
Use when building a custom UI (page, dashboard, buttons) that should wake a Grok Bot over a webhook, when the user must provide a webhook sender key, or when exposing that UI on Tailscale.
Also in 19 projects that use this
TheOnlyFusionCubeSkillstatechart
Draw what an app's user sees as a Mermaid statechart from a TLA+ model. States are gray if they work, red if still wrong, and green if fixed. Each bug TLC finds is a numbered path. Use for /statechart, \"show the PM the bug\", or to turn an agreed chart into a TLA+ skeleton.
Also in 16 projects that use this
Other versions98 projects use a version of this.
Word for word · 0
None found.
Edited · 51
- backnotprop/pstack★ 4.2k20% same
- moeru-ai/xsai★ 66715% same
- uzairansaruzi/p3-stack★ 12618% same
- Dimon94/dverity★ 10717% same
- Dimon94/skills★ 10717% same
- dsebban/skills★ 7116% same
- painhardcore/pstack★ 2217% same
- creedants/pstack-t3★ 1815% same
- mariusflorescu/pstack-t3★ 1314% same
- Scino/fstack★ 1318% same
41 more not listed
Wrote their own version · 47
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- poteto/how★ 878same name
- jtaroreh/agystack★ 128same name
- roerohan/skills★ 29same name
- overextended/skills★ 22same name
- TheOnlyFusionCube/potetos-for-everyone★ 21same name
- pantheon-org/tekhne★ 10same name
- kkgogogo17/pi-pstack★ 9same name
- ex3ndr/skills★ 5same name
37 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 repository53 other files it gives its agents.
- architectSkill
- arenaSkill
- automate-meSkill
- benchmark-checklistSkill
- blast-radiusSkill
- broSkill
- correctSkill
- create-formal-verification-skillSkill
- create-verification-skillSkill
- figure-it-outSkill
- interrogateSkill
- in-your-own-wordsSkill
- ketchupSkill
- maintain-formal-verification-skillSkill
- maintain-verification-skillSkill
- no-commentsSkill
- poteto-modeSkill
- principle-attack-the-premiseSkill
- principle-boundary-disciplineSkill
- principle-build-the-leverSkill
- principle-encode-lessons-in-structureSkill
- principle-exhaust-the-design-spaceSkill
- principle-experience-firstSkill
- principle-explain-the-numberSkill
- principle-fix-root-causesSkill
- principle-foundational-thinkingSkill
- principle-guard-the-context-windowSkill
- principle-laziness-protocolSkill
- principle-make-operations-idempotentSkill
- principle-migrate-callers-then-delete-legacy-apisSkill
- principle-minimize-reader-loadSkill
- principle-model-the-domainSkill
- principle-never-block-on-the-humanSkill
- principle-outcome-oriented-executionSkill
- principle-prove-it-worksSkill
- principle-redesign-from-first-principlesSkill
- principle-separate-before-serializing-shared-stateSkill
- principle-sequence-verifiable-unitsSkill
- principle-subtract-before-you-addSkill
- principle-test-behavior-not-implementationSkill
- principle-type-system-disciplineSkill
- recallSkill
- reflectSkill
- setup-pstackSkill
- sharpenSkill
- show-me-your-workSkill
- swarmSkill
- tddSkill
- teachSkill
- technical-writingSkill
- typescript-best-practicesSkill
- unslopSkill
- whySkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 97 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Use pstack_task with agent: "general-purpose" and readonly: true for every delegation.
- Distinctive: line 15
If the scope is ambiguous, state your interpretation and explore.
- Distinctive: line 20
When in doubt, use the simple path.
- Very specific: line 28
After all explorers return, spawn one explainer with role: "how-explainer".
- Very specific: line 36
Use the applicable sections from references/explainer-prompt.md: Overview, Key Concepts, How It Works, Where Things Live, and Gotchas.
“Common” is measured: kept by at least 6 in 10 of the 97 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
How
Explore the codebase to answer "how does X work?" questions. Produce architectural explanations at the level of a senior engineer onboarding onto a subsystem. Build a working mental model instead of annotating source code.
Use pstack_task with agent: "general-purpose" and readonly: true for every delegation.
1. Assess complexity
If the scope is ambiguous, state your interpretation and explore. The user can redirect.
- Simple. For one module, utility, or narrow question, skip explorers. Spawn one explainer with
role: "how-explainer". Build its prompt fromreferences/explainer-prompt.mdwithout the explorer-findings section. Continue at step 4. - Complex. For a subsystem spanning files or services, continue at step 2.
When in doubt, use the simple path.
2. Explore complex questions
Decompose the question into two to four distinct angles. Spawn all explorers in one pstack_task parallel call. Set role: "how-explorer" on every task. Fill each angle into references/explorer-prompt.md.
3. Synthesize
After all explorers return, spawn one explainer with role: "how-explainer". Use references/explainer-prompt.md and include every explorer finding.
4. Present
Present the explainer output. Light edits for clarity are acceptable. Do not substantially rewrite it.
Output format
Use the applicable sections from references/explainer-prompt.md: Overview, Key Concepts, How It Works, Where Things Live, and Gotchas.
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.

