Individual skill

architecture-breakdown

Map an unfamiliar codebase or subsystem into modules, boundaries, data flow, entry points, and hot spots, and produce a breakdown other engineers can navigate by. Use before large changes, onboarding, or when asked how something is structured.

src/skills/builtin/architecture-breakdown/SKILL.md

Read pinned source

Source commit 79a26efbea50aa0e351c4b5fbdfc6502fef25b8e

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Instructions only
Last checked: Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 216
Repository last updated: Nov 5, 2026
License: Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agentic-ai Repository topic
ai Repository topic
code-cli Repository topic
code-generation Repository topic
llms Repository topic
ai-agents-cli Repository topic
autonomous-agents Repository topic
ai-coding-agent Repository topic
ai-coding-agents Repository topic
coding-agent Repository topic
engineering Derived category
data Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 1,873 bytes

Read excerpt


# Break the architecture down

Produce a map, not a summary. The reader should be able to open the right file
for any responsibility without searching.

## Survey

1. Entry points: binaries, `main`, CLI commands, HTTP routes, jobs, event
   handlers. Find them from the build config and manifests, then follow imports.
2. Layers and boundaries: what talks to what. Note the direction of
   dependencies and any cycles.
3. State: where data lives (stores, caches, files), who owns each piece, and
   how it moves between layers.
4. Cross-cutting concerns: config, auth, logging, errors, retries, feature