Onboard

Skill viknesh20-20/claude-code-tool-kit/.claude/skills/onboard

Production-ready Claude Code configuration. 12 original agents, 200+ slash-command skills, 45+ MCP servers, 14 plugins, design + 3D + WebGPU + GSAP + RAG tooling. One-command Node.js installer for premium websites, SaaS apps, AI agents. Free, MIT, stack-agnostic.

Install

npx -y skills add viknesh20-20/claude-code-tool-kit --skill onboard

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Generates a comprehensive codebase onboarding guide by scanning the project structure, detecting the stack, mapping architecture, and identifying key entry points. Use when joining a new project or onboarding teammates.

SKILL.md

3.0 KB, as published. Nobody here has run it

Codebase Onboarding

Auto-Scan

!find . -type f -not -path "*/node_modules/*" -not -path "*/.git/*" -not -path "*/vendor/*" -not -path "*/__pycache__/*" -not -path "*/target/*" -not -path "*/dist/*" -not -path "*/build/*" -not -path "*/.next/*" 2>/dev/null | wc -l

Project Files

!ls package.json requirements.txt pyproject.toml go.mod Cargo.toml *.csproj *.sln Gemfile composer.json mix.exs Makefile Dockerfile docker-compose* 2>/dev/null

Directory Structure

!tree -L 2 -I "node_modules|.git|vendor|__pycache__|target|dist|build|.next" 2>/dev/null || find . -type d -maxdepth 2 -not -path "*/node_modules/*" -not -path "*/.git/*" 2>/dev/null

README

!cat README.md 2>/dev/null | head -50

Git Activity

!git log --oneline -20 2>/dev/null !git shortlog -sn --no-merges 2>/dev/null | head -10

Onboarding Guide Generation

Section 1: Project Overview

What this project does (from README + code analysis)
Who maintains it (from git history)
How active it is (recent commits, contributors)

Section 2: Tech Stack

Detect and document:

Language(s) and version(s)
Framework(s)
Database(s)
Package manager
Test framework
Build tools
CI/CD system

Section 3: Directory Map

Annotated directory tree:

src/
├── components/   # UI components
├── services/     # Business logic
├── utils/        # Shared utilities
├── types/        # Type definitions
└── config/       # Configuration

Section 4: Key Entry Points

Application entry point (main file, index, app)
API routes / endpoints
Database schema / models
Configuration files
Environment variables needed

Section 5: How to Run

Prerequisites (runtime versions, tools)
Installation steps
Development server command
Test command
Build command

Section 6: Architecture Patterns

Code organization pattern (MVC, hexagonal, feature-based, etc.)
State management approach
Data flow (request lifecycle)
Error handling strategy
Authentication/authorization approach

Section 7: Where to Start

Based on the codebase analysis:

"If you need to fix a bug, start here: ..."
"If you need to add a feature, start here: ..."
"If you need to understand the data model, look at: ..."

Section 8: Gotchas & Tribal Knowledge

Non-obvious conventions found in the code
Common pitfalls (from error handling patterns and comments)
Areas with tech debt (complex, undocumented, or heavily modified files)

Rules

Base everything on actual code — don't assume
Flag areas that lack documentation
Be honest about code quality and tech debt
Include exact file paths for every reference