agentleFS
Sign inStart free
anhermonanhermon/pstack-claude/skills/how/SKILL.md

how

Skill0 starsChanged 38 days agoMITView on GitHub

Use for \"how does X work\", code walkthroughs before changing something, and placement / ownership / layering questions (\"where should this live\", \"which package owns this\", \"is this the right layer\"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.

90 other projects use a version of this, 61 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use ketchup-video, make-bot-ui and 5 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.
  • tristanphvnSkill

    ketchup-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

  • eryzerzSkill

    make-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

  • drafaelSkill

    in-your-own-words

    Restate the user's goals and the problem they are trying to solve to check understanding. Manual invocation only; use when the user explicitly invokes in-your-own-words or requests this understanding check. Do not solve the task or rewrite the assistant's last answer.

    Also in 26 projects that use this

  • TheOnlyFusionCubeSkill

    maintain-formal-verification-skill

    Bring a project's formal verification back in line with the code after the code changes: find the commits that touched verified code, update the model, harness, or properties to describe the code as it is now, rerun, and say whether each failure is drift in the verification or a bug in the code. Use for /maintain-formal-verification-skill, \"is the model still true to the code\", or after merges and refactors that touched verified code without rechecking it.

    Also in 20 projects that use this

  • TheOnlyFusionCubeSkill

    create-formal-verification-skill

    Generate a project-local skill that formally verifies the code where a bug costs the most and tests reach the least, in any language, with whichever verification tool fits. Use for /create-formal-verification-skill, \"model-check this race\", \"prove this invariant\", or when concurrency, retries, state machines, parsers, or unsafe code need more than tests.

    Also in 21 projects that use this

  • instructureSkill

    ketchup

    Rebuild context after /clear by analyzing uncommitted changes across Canvas LMS and all plugin repositories

    Also in 22 projects that use this

  • +1 more from TheOnlyFusionCube

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 89 edited versions we read keep these.

  • 2

    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
  1. Distinctive:

    If the scope is ambiguous, state your interpretation and explore.

    line 16
  2. Distinctive:

    When in doubt, take the simple path.

    line 21
  3. Very specific:

    read-only: enforced by pstack:read-only (no Edit/Write).

    line 30

“Common” is measured: kept by at least 6 in 10 of the 89 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

How

Claude Code: read Cursor terms in this skill through claude-code/runtime.md (tools, subagents, models, transcripts).

Explore the codebase to answer "how does X work?" questions. Produce architectural explanations at the level of a senior engineer onboarding onto a subsystem, enough to build a working mental model, not so much that it reads like annotated source code.

Resolve each seat's explicit model and effort from delegation-kit's live routing table when its Delegation routing (live section is in context; otherwise use pstack-models.md and the defaults below. Map auto, inherit-parent, and inherit to model: sonnet, effort: medium. Always pass both parameters to Agent, including retries and resumes. For fan-outs of 3+ use sonnet/haiku seats, never opus. The main session owns final synthesis; any separately prescribed synthesizer runs alone after the fan-out.

Step 1. Assess Complexity

If the scope is ambiguous, state your interpretation and explore. The user can redirect.

  • Simple (a single module, a small utility, a narrow question such as "how does function X work"): no explorers. The main session explores and explains in a single pass. Go to Step 2b.
  • Complex (a subsystem spanning multiple files or services, a cross-cutting feature, a full architectural overview): spawn parallel explorers first, then synthesize in the main session. Go to Step 2a.

When in doubt, take the simple path.

Step 2a. Explore (complex questions only)

Decompose the question into 2 to 4 exploration angles, each a distinct slice of the subsystem. Spawn all explorers in a single message:

  • subagent_type: pstack:read-only
  • model: the how explorer line, default sonnet
  • effort: explicitly pass the configured effort, default low
  • read-only: enforced by pstack:read-only (no Edit/Write); still say "do not modify files" in the prompt

Each explorer gets the prompt in references/explorer-prompt.md with its angle filled in. Then go to Step 3.

Step 2b. Direct Explain (simple questions)

The main session explores and explains directly; do not spawn an explainer. Follow references/explainer-prompt.md without the explorer-findings section. Go to Step 4.

Step 3. Synthesize (complex questions only)

Once all explorers have returned, the main session synthesizes their findings. Follow references/explainer-prompt.md with every explorer's findings filled in.

Step 4. Present

Present the main session's explanation to the user. Light edits for clarity or context from the conversation are fine. Do not substantially rewrite it.

Output Format

The explanation uses the sections defined in references/explainer-prompt.md, dropping any that do not apply: Overview, Key Concepts, How It Works, Where Things Live, Gotchas.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free