Shuashuaa

Codebase Onboarding — Data skill for Claude Code

Data community

A Claude skill that turns any codebase into an interactive onboarding map: services, auth, request flows, data, APIs and setup, in one offline HTML page.

How to install Codebase Onboarding

This entry records only its repository, not the path inside it, so there is no exact command to give. Open Shuashuaa/codebase-onboarding and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Codebase Onboarding does

A Claude skill that turns any codebase into an interactive onboarding map: services, auth, request flows, data, APIs and setup, in one offline HTML page.

Alternatives in Data

  • Financial Services — Reference agents, skills, and data connectors for the financial-services workflows we see most — investment ba 34.5k ★
  • 12 Services Layer — Prompt 12: Wire Up Services Layer (Analytics, Policy, Settings, Sessions) 2.3k ★
  • Claude Code Memory Setup — Up to 71.5x fewer tokens per session on Claude Code with Obsidian + Graphify 947 ★

README

codebase-onboarding

A Claude skill that turns any codebase into an interactive onboarding map: services, auth, request flows, data, APIs and setup, in one offline HTML page.

New to a project? Ask Claude *"I'm new to this repo. Map how it fits together."* and get `docs/onboarding/atlas.html`: a page you can open in any browser, commit, and share with the next new teammate.

![codebase-onboarding demo: overview, service map, flows and API catalog](docs/demo.gif)

**Disclaimer:** The demo and screenshots show an atlas generated from [aws-samples/aws-sam-nested-stack-sample](https://github.com/aws-samples/aws-sam-nested-stack-sample), a public AWS sample repository (Apache-2.0). It is used only to demonstrate what this skill produces on a real codebase. This project is not affiliated with or endorsed by Amazon Web Services, and no code from that repository is included here.

What you get

Tab Answers
Overview What is this system? Where do I start? (guided tour, open questions)
Service map How do frontend → auth → gateway → compute → queues → data connect?
Flows What happens, step by step, when a user logs in or places an order?
APIs Which endpoints exist, who handles them, what auth they need
Auth Identity provider, tokens, where they're verified, roles
Data Entities, keys, access patterns, owning service
Code Entry points and modules
Run & ship Local setup, environments, config keys (names only), CI/CD
Operate Logs, alarms, symptom → check → fix runbooks
Context Glossary, owners, decisions, hotspots

Every component and connection is marked **declared** (found in config or code) or **inferred** (Claude's reasoned guess, drawn dashed). Anything the repo can't answer becomes an open question instead of a made-up fact.

![Service map of the aws-sam-nested-stack-sample repo](docs/preview-map.png)

Works with

AWS (Serverless Framework, SAM, CloudF