How

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.

107 stars 21 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add Dimon94/skills --skill how
Manual install
git clone --depth 1 https://github.com/Dimon94/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/how ~/.claude/skills/how

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# 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, enough to build a working mental model, not so much that it reads like annotated source code.

Spawn subagents in the current runtime's native way. When the runtime accepts an explicit model per spawn, set it by role tier; a model the user explicitly chose always wins over this table. If the runtime cannot resolve a tier to a concrete model, leave model unset and continue — never block on it.

- explorers: fast tier. The cheapest adequate general model in the current runtime.
- explainer / synthesizer: strong tier. The strongest reasoning model available.

## 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. One explainer 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 hand off to the explainer. 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 read-only explorer subagents in a single message, one per angle.
Read the full skill on GitHub

Details

Skill name
how
Repository
Dimon94/skills
Path
skills/how/SKILL.md
Repo updated
18 November 2026
Copies
Found in 3 GitHub repos

FAQ

What does the How skill do?

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.

How do I install the How skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add Dimon94/skills --skill how. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is How popular?

It lives in Dimon94/skills, which has 107 GitHub stars and 21 forks, and is included in 2 curated skill lists.

Related skills

Maintain Verification Skill

107

Dimon94/skills

Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for /maintain-verification-skill or "audit the verify skill".

Git & Code ReviewIn 2 lists21

Create Verification Skill

107

Dimon94/skills

Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, "make a control skill for this repo", or when a project has no scripted way to prove UI/CLI/service behavior.

Software DevelopmentIn 2 lists21

Principle Boundary Discipline

107

Dimon94/skills

Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure functions.

Software DevelopmentIn 2 lists21

Principle Laziness Protocol

107

Dimon94/skills

Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.

Software DevelopmentIn 2 lists21

Zig Debugging

293

mohitmishra786/low-level-dev-skills

Zig debugging skill. Use when debugging Zig programs with GDB or LLDB, interpreting Zig runtime panics, using std.debug.print for tracing, configuring debug builds, or debugging Zig programs in VS Code. Activates on queries about debugging Zig, Zig panics, zig gdb, zig lldb, std.debug.print, Zig stack traces, or Zig error return traces.

Software Development36

Principle Migrate Callers Then Delete Legacy Apis

107

Dimon94/skills

Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving compatibility layers.

Software DevelopmentIn 2 lists21

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.