layers: presentation, business logic, data access, infrastructure
Generate
a hierarchical JSON catalogue with:
Onboarding
Principal-Level Guide, Zero to Hero Guide
Getting Started
overview, setup, usage, quick reference
Deep Dive
architecture → subsystems → components → methods
Cite
real files in every section prompt using
file_path:line_number
Onboarding Guide Architecture
The catalogue MUST include an Onboarding section (always first, uncollapsed) containing:
Principal-Level Guide
— For senior/principal ICs. Dense, opinionated. Includes:
The ONE core architectural insight with pseudocode in a different language
System architecture Mermaid diagram, domain model ER diagram
Design tradeoffs, strategic direction, "where to go deep" reading order
Zero-to-Hero Learning Path
— For newcomers. Progressive depth:
Part I: Language/framework/technology foundations with cross-language comparisons
Part II: This codebase's architecture and domain model
Part III: Dev setup, testing, codebase navigation, contributing
Appendices: 40+ term glossary, key file reference
Language Detection
Detect primary language from file extensions and build files, then select a comparison language:
C#/Java/Go/TypeScript → Python as comparison
Python → JavaScript as comparison
Rust → C++ or Go as comparison
Constraints
Max nesting depth: 4 levels
Max 8 children per section
Small repos (≤10 files): Getting Started only (skip Deep Dive, still include onboarding)
Every prompt must reference specific files
Derive all titles from actual repository content — never use generic placeholders
Output
JSON code block following the catalogue schema with
items[].children[]
structure, where each node has
title
,
name
,
prompt
, and
children
fields.
When to Use
This skill is applicable to execute the workflow or actions described in the overview.