how

Name: how
Availability: InStock
Author: Paul

Explore code paths and synthesize architectural mental models of subsystems.

Updated May 18, 2025

Search Tags:#system design #codebase exploration #dependency mapping #architecture explanation #call flow tracing #engineering onboarding #architectural critique

Ready to run

npx skills add https://github.com/nthpaul/dotfiles --skill how-nthpaul

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: how
Source: https://github.com/nthpaul/dotfiles/tree/main/cursor/.cursor/plugins/local/how/skills/how
Command: npx skills add https://github.com/nthpaul/dotfiles --skill how-nthpaul

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you learn how a specific part of a codebase works by tracing the real implementation and turning it into a senior-engineer-level mental model.

Core Features & Use Cases

Explain mode: Builds an architectural walkthrough by exploring the codebase, mapping key abstractions, and describing the end-to-end flow.
Critique mode: Produces the explanation first, then evaluates architectural issues using multiple specialized critics.
Right-sized exploration: Chooses between a direct one-pass explanation for simple questions and parallel exploration for complex subsystems.

Quick Start

Ask: "How does [feature/subsystem X] work in this repository?" and (optionally) "Critique the architecture for issues" if you want improvement-oriented feedback.

Frequently Asked Questions about how

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

FAQPage Schema

How do I understand how a specific subsystem works in an unfamiliar codebase?▼

To understand a subsystem, this Skill explores code paths, identifies abstractions, and synthesizes a clear architectural mental model. It traces triggers, call chains, and boundaries to provide an end-to-end walkthrough of the target feature.

What is the best way to trace call flows and map dependencies during engineering onboarding?▼

Tracing call flows during onboarding is handled by exploring the repository's reference prompts to map dependencies and identify cross-cutting flows. It produces a senior-engineer-level mental model without manual codebase digging.

Can I get an architectural critique of existing system design after generating an explanation?▼

Yes, you can request an architectural critique after the explanation. Critique mode evaluates architectural issues and highlights gotchas using specialized critics to provide improvement-oriented feedback on the subsystem.

Does this codebase exploration approach work for both simple and complex architectural questions?▼

Codebase exploration adapts to complexity by choosing a direct one-pass explanation for simple questions and parallel exploration for complex subsystems. This right-sized exploration ensures accurate architectural explanations regardless of scope.

How do I explain a runtime trace across cross-cutting flows in a large repository?▼

To explain a runtime trace, the Skill follows cross-cutting flows through the codebase to build an architectural walkthrough. It synthesizes the end-to-end execution path and component boundaries into a clear mental model.