how

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

4|1|Updated Dec 16, 2023
One-click install
npx skills add https://github.com/Shtian/AuthentiClash --skill how-shtian
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: how
Source: https://github.com/Shtian/AuthentiClash/tree/main/.claude/skills/how
Command: npx skills add https://github.com/Shtian/AuthentiClash --skill how-shtian

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Understanding how an unfamiliar subsystem works requires tracing code paths across many files, which is slow and error-prone when done manually. This Skill answers "how does X work" questions by exploring the codebase and producing a senior-engineer-level architectural explanation. ## Core Features & Use Cases - Complexity Assessment: Routes simple questions to a single-pass explainer and complex, multi-file questions to parallel explorer agents. - Parallel Exploration: Decomposes subsystem questions into 2-4 exploration angles, each investigated by a read-only subagent using structured prompt templates. - Synthesized Explanations: Merges explorer findings into a unified explanation with Overview, Key Concepts, How It Works, Where Things Live, and Gotchas sections, including mermaid diagrams where useful. - Use Case: Before modifying an authentication flow, ask how login sessions are validated and receive a walkthrough of the entry points, call chain, key abstractions, and pitfalls with exact file references. ## Quick Start Ask how the game scoring flow works in this repository to get an architectural walkthrough of the relevant 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 codebase, tracing entry points, call chains, and key abstractions. It returns a structured explanation with an overview, flow walkthrough, file map, and gotchas referencing exact files and functions.

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

Simple questions about a single module or function are explored and explained in one pass by a single subagent. Complex questions spanning multiple files are decomposed into 2-4 angles investigated by parallel explorer subagents, then synthesized into one explanation.

Can I use this to decide where new code should live?▼

Yes, the skill covers placement, ownership, and layering questions such as "where should this live" or "which package owns this". It explains subsystem architecture and boundaries so you can judge the right layer for new logic.

Does the exploration modify any files in the repository?▼

No, all explorer and explainer subagents are explicitly instructed not to modify files. They use read-only operations like Read, Grep, and Glob to trace code paths and gather findings.

What happens when explorers cannot fully trace part of the code?▼

Explorers report gaps explicitly in an Open Questions section rather than guessing. The explainer acknowledges these unresolved areas in the final explanation instead of hiding them.