Clone or browse the repo. Read actual code — module structure, entry points, key abstractions. Don't rely solely on READMEs.
Search for official docs, blog posts, conference talks, design docs, ADRs, and community discussions that explain the why behind the architecture.
Cite what you find. If you're inferring rationale (no source), say so explicitly.
Research the architecture of a codebase or system. Reads source code, finds external context, explains design decisions, and produces ELK diagrams. Use when asked to understand, explain, or diagram how a repo/system is built. Source: tychohq/agent-skills.