Results for “codebase-onboarding”

Maps, documents, and onboards into an existing codebase by generating seven structured documents covering stack, structure, architecture, conventions, integrations, testing, and concerns.

Practical codebase onboarding for Nick's workflow. Use when opening a stale project, picking up a new repo, rebuilding context after time away, or generating fast markdown docs that explain how to start working on a codebase right now. Focus on setup, key files, flows, commands, risks, and what to touch first.

Generates a codebase architecture document and CLAUDE.md scaffold by exploring source code and asking targeted questions.

Systematically explore an unfamiliar codebase and build a reusable architecture summary with file:line evidence, starting from documentation and tracing data flow.

Create CodeTour `.tour` files with persona-targeted, step-by-step walkthroughs anchored to real files and line ranges for onboarding, architecture, PR review, and code explanation.

Deep codebase initialization with hierarchical AGENTS.md documentation

You are a documentation architect that produces structured wiki catalogues and onboarding guides from codebases.

Creates CodeTour `.tour` files with real file and line anchors for guided codebase walkthroughs, including onboarding, architecture, PR, and RCA tours.

Creates persona-targeted, step-by-step CodeTour walkthroughs that link to real files and line numbers for onboarding, architecture, PR review, and more.

Creates CodeTour .tour files — persona-targeted, step-by-step walkthroughs that link to real files and line numbers for any repository.

Audits and rewrites user-facing copy across web and mobile codebases, improving clarity, tone, and actionability of labels, errors, CTAs, and empty states.

Generates a structured developer-facing markdown document that teaches how a specific feature, module, or piece of functionality works in the codebase. Use this skill whenever the user runs `/teach`, asks "how does X work", "explain the auth flow", "document how payments work", "walk me through the webhook system", or any request to understand and document internal codebase functionality. Also trigger when the user wants to produce onboarding docs, feature walkthroughs, or "how it works" references for developers. Always use this skill even if the user only gives a vague description — use the provided context or file hints to locate the relevant code yourself and build the teaching doc from there. This skill writes for developers reading the codebase — for end-user/customer-facing help docs, use the eli5-features skill instead.

Generate user-friendly "Explain Like I'm 5" feature documentation for end users by reading the codebase. Use this skill whenever the user wants to document a feature for non-technical users, write help docs, create an explainer for a feature in their app, produce onboarding content, or asks "make a user doc for X". Trigger on phrasings like "ELI5 the closeout flow", "write user docs for the kanban view", "explain this feature to a customer", "make a help article for X", "document this for end users". Also known as "E-features-LI5". This skill produces plain-language docs written for someone with the app open trying to get something done — not internal developer docs (use the `teach` skill for those) and not feature announcements.