how

Generates architectural explanations of how codebases work using parallel explorer subagents.

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

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, and ad-hoc explanations often miss key flows, boundaries, or gotchas that a senior engineer would need before making changes. ## Core Features & Use Cases - Adaptive Exploration Depth: Routes simple questions to a single-pass explainer and complex subsystem questions to 2-4 parallel read-only explorer agents followed by a synthesis pass. - Structured Explanations: Produces senior-engineer-level walkthroughs with Overview, Key Concepts, How It Works, Where Things Live, and Gotchas sections, including mermaid or ASCII diagrams when flows involve multiple components. - Use Case: Before modifying a payment pipeline, ask how refund processing works and receive a traced explanation covering entry points, call chains, file locations, and non-obvious pitfalls. ## Quick Start Ask how the authentication flow works in this repository to receive a structured architectural explanation.

Frequently Asked Questions about how

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

FAQPage Schema
How do I get an explanation of how a codebase subsystem works?▼

Ask a 'how does X work' question and the skill explores the codebase, tracing entry points, call chains, and key abstractions. Complex questions spawn parallel explorer agents whose findings are synthesized into one structured explanation.

How does the skill decide between simple and complex exploration?▼

Simple questions about a single module or narrow function go to one explainer agent in a single pass. Complex questions spanning multiple files or services trigger 2 to 4 parallel explorers, then a synthesis step that reconciles their findings.

What sections does the architectural explanation include?▼

Explanations use Overview, Key Concepts, How It Works, Where Things Live, and Gotchas sections, dropping any that do not apply. Diagrams in mermaid or ASCII are included when flows involve multiple interacting components.

Can the exploration agents modify my code?▼

No. All explorer and explainer subagents run in read-only mode using Read, Grep, and Glob. They gather facts and write explanations without changing any files.

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

Use it when onboarding onto an unfamiliar subsystem, before changing code you do not own, or when deciding where new logic should live. It is less useful for single-line questions answerable by reading one function directly.