how

Generates architectural explanations of codebases by orchestrating parallel read-only explorer and explainer subagents.

2|Updated Jun 27, 2026
One-click install
npx skills add https://github.com/imjasonh/playground --skill how-imjasonh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: how
Source: https://github.com/imjasonh/playground/tree/main/.cursor/skills/how
Command: npx skills add https://github.com/imjasonh/playground --skill how-imjasonh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Understanding how an unfamiliar subsystem works requires hours of manual code reading. This Skill answers "how does X work" questions by exploring the codebase and producing a senior-engineer-level architectural explanation with a working mental model. ## Core Features & Use Cases - Complexity Assessment: Routes simple questions to a single-pass explainer and complex subsystem questions to parallel explorers plus a synthesizer. - Parallel Exploration: Decomposes broad questions into 2-4 exploration angles, each investigated by a read-only subagent that traces entry points, call chains, abstractions, and boundaries. - Structured Explanations: Synthesizes findings into sections covering Overview, Key Concepts, How It Works, Where Things Live, and Gotchas, with mermaid or ASCII diagrams where useful. - Use Case: Before modifying a payment processing flow spanning multiple services, ask how it works and receive a walkthrough of the trigger, step-by-step data flow, key files, and non-obvious pitfalls. ## Quick Start Ask how the authentication flow in this repository works and receive an architectural explanation of the subsystem.

Frequently Asked Questions about how

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I understand how an unfamiliar codebase subsystem works?▼

Ask a how-does-X-work question and the Skill explores the code, tracing entry points, call chains, and key abstractions. It returns a structured explanation with an overview, flow walkthrough, file map, and gotchas.

How does the Skill handle simple versus complex architecture questions?▼

Simple questions about a single module or function go to one explainer subagent in a single pass. Complex questions spanning multiple files or services are decomposed into 2-4 angles explored by parallel subagents, then synthesized.

Can the explorer agents modify my code while investigating?▼

No. All explorer and explainer subagents run with read-only access, using Read, Grep, and Glob to inspect the codebase. They gather facts and write explanations without changing any files.

What sections does the generated architectural explanation include?▼

Explanations use sections for Overview, Key Concepts, How It Works, Where Things Live, and Gotchas, dropping any that do not apply. Diagrams in mermaid or ASCII are included when they clarify multi-component flows.

When should I use this instead of reading the source code directly?▼

Use it when you need a working mental model of a subsystem before changing code, or when deciding where new logic should live. It is not a substitute for reading exact implementations when making precise edits.