Loading...
Loading...
Found 18 Skills
Codebase Onboarding
Analyze an unfamiliar codebase and generate a structured onboarding guide with architecture map, key entry points, conventions, and a starter CLAUDE.md. Use when joining a new project or setting up Claude Code for the first time in a repo.
Launch multiple explore subagents in parallel to investigate architecture, data models, auth, APIs, and deployment. Synthesize into an onboarding document.
Analyze an unfamiliar repository and explain what it does, how it runs, what architectural choices define it, where the important code lives, and what deserves deeper inspection next. Use this whenever a user has just cloned a repo, wants onboarding help, asks for a repo walkthrough, or needs a reliable first-pass architecture analysis.
Generate a SYSTEM_OVERVIEW.md that orients a senior engineer new to an unfamiliar codebase, with a Mermaid architecture diagram, a sequence diagram for data flow, and a legacy-pattern assessment. Use when user says 'give me a system overview', 'onboard me on this repo', 'walk me into this legacy codebase', 'document the high-level architecture', or 'create a SYSTEM_OVERVIEW.md'. Do NOT use for code walkthroughs (use explain), persistent architecture chapters (use arc42), or ADRs (use document-decision).
Use this before touching code when you have a requirement for a specification or multi-step task
Guide existing codebase onboarding through mapping, doc ingest, and planning setup
Gamified codebase onboarding through the Spaghetti Code Monster. Use when a developer wants to learn a new codebase through investigation, deep-dive challenges, and the Monster's guidance.
Write effective AGENTS.md files that give coding agents the context they need to work in a repository. Use when creating a new AGENTS.md, improving an existing one, setting up a repo for AI coding agents, or onboarding agents to a codebase. Triggers on: "write AGENTS.md", "create AGENTS.md", "agent instructions", "set up repo for agents", "configure coding agent", "onboard agent to codebase", "agent context file".
Use this when you have specifications or requirements for multi-step tasks, before starting to write code
Explain a piece of code, a subsystem, or an architectural concept in the codebase, grounded in real files. Use when user says 'explain this', 'walk me through X', 'how does Y work', 'what does this module do', 'help me understand the Z flow', or 'onboard me on this component'. Do NOT use for writing permanent docs (use write-doc or arc42) or for code review (use review-diff).
Teaches beginners and vibe coders how their own project works in plain, simple English. Explains the architecture, what each file and folder does, how the frontend, backend, database and API connect, how a click becomes a request, and what the runtime is (for example Node.js). Gives a transparent code quality score out of 100, security red flags, a prioritized fix list with ready-to-paste prompts, big-tech best practices, and feature ideas, all as structured cards and tables. Use when the user asks to explain, understand, tour, map, review, score, rate or improve their codebase, asks what a file does or what happens when a button is clicked, asks if their app is safe, or mentions vibe teacher.