From project-starter
Analyzes any project to understand its structure, tech stack, patterns, and conventions. Use when starting work on a new codebase, onboarding, or when asked "how does this project work?" or "what's the architecture?"
How this skill is triggered — by the user, by Claude, or both
Slash command
/project-starter:project-analysisThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
When analyzing a project, systematically gather and present information in this order:
When analyzing a project, systematically gather and present information in this order:
# Check for common project markers
ls -la
cat README.md 2>/dev/null | head -50
package.json → Node.js/JavaScript/TypeScriptrequirements.txt / pyproject.toml / setup.py → Pythongo.mod → GoCargo.toml → Rustpom.xml / build.gradle → JavaGemfile → RubyDockerfile, docker-compose.yml → Containerizedkubernetes/, k8s/ → Kubernetesterraform/, .tf files → IaCserverless.yml → Serverless Framework.github/workflows/ → GitHub ActionsPresent as a tree with annotations:
project/
├── src/ # Source code
│ ├── components/ # UI components (React/Vue)
│ ├── services/ # Business logic
│ ├── models/ # Data models
│ └── utils/ # Shared utilities
├── tests/ # Test files
├── docs/ # Documentation
└── config/ # Configuration
Look for and report:
Check for:
.eslintrc, .prettierrc → Linting/Formatting.husky/ → Git hooksMakefile → Build commandsscripts/ in package.json → NPM scripts# Project: [Name]
## Overview
[1-2 sentence description]
## Tech Stack
| Category | Technology |
|----------|------------|
| Language | TypeScript |
| Framework | Next.js 14 |
| Database | PostgreSQL |
| ... | ... |
## Architecture
[Description with simple ASCII diagram if helpful]
## Key Directories
- `src/` - [purpose]
- `lib/` - [purpose]
## Entry Points
- Main: `src/index.ts`
- API: `src/api/`
- Tests: `npm test`
## Conventions
- [Naming conventions]
- [File organization patterns]
- [Code style preferences]
## Quick Commands
| Action | Command |
|--------|---------|
| Install | `npm install` |
| Dev | `npm run dev` |
| Test | `npm test` |
| Build | `npm run build` |
npx claudepluginhub skalingclouds/claude-workflow3plugins reuse this skill
First indexed Jul 10, 2026
Analyzes codebases to reveal structure, tech stack, patterns, and conventions. Useful for onboarding to new projects or exploring unfamiliar code.
Extracts tech stack, project structure, key patterns, and conventions from codebases via package.json scans, find, grep for JS/TS, Python, Go, Rust projects. Use before PRDs or planning.
Analyzes project tech stack via sync-ctl CLI: detects languages, frameworks, runtimes, package managers, dependencies, Docker/K8s, monorepo structure. Use before scans or to understand codebases.