Before you start coding on an unfamiliar repo, this walks you through the essentials in a specific order: architecture docs first, then drilling into the right layer (server, client, or MCP), then picking minimal files to read, and finally confirming test commands before touching anything. It's opinionated about structure, assuming a particular stack with separate backend/frontend/MCP directories and specific npm scripts. The real value is enforcing that verification step upfront so you're not guessing how to validate your changes later. If your repo follows different conventions, you'll need to adapt the directory assumptions, but the discovery-before-implementation pattern holds up.
npx -y skills add hoangsonww/claude-code-agent-monitor --skill repo-onboarding --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
sickn33/antigravity-awesome-skills
kubesphere/kubesphere
supercent-io/skills-template