Project Analysis Skill
When analyzing a project, systematically gather and present information in this order:
1. Quick Overview (30 seconds)
# Check for common project markers
ls -la
cat README.md 2>/dev/null | head -50
2. Tech Stack Detection
Package Managers & Dependencies
package.json → Node.js/JavaScript/TypeScript
requirements.txt / pyproject.toml / setup.py → Python
go.mod → Go
Cargo.toml → Rust
pom.xml / build.gradle → Java
Gemfile → Ruby
Frameworks (from dependencies)
- React, Vue, Angular, Next.js, Nuxt
- Express, FastAPI, Django, Flask, Rails
- Spring Boot, Gin, Echo
Infrastructure
Dockerfile, docker-compose.yml → Containerized
kubernetes/, k8s/ → Kubernetes
terraform/, .tf files → IaC
serverless.yml → Serverless Framework
.github/workflows/ → GitHub Actions
3. Project Structure Analysis
Present 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
4. Key Patterns Identification
Look for and report:
- Architecture: Monolith, Microservices, Serverless, Monorepo
- API Style: REST, GraphQL, gRPC, tRPC
- State Management: Redux, Zustand, MobX, Context
- Database: SQL, NoSQL, ORM used
- Authentication: JWT, OAuth, Sessions
- Testing: Jest, Pytest, Go test, etc.
5. Development Workflow
Check for:
.eslintrc, .prettierrc → Linting/Formatting
.husky/ → Git hooks
Makefile → Build commands
scripts/ in package.json → NPM scripts
6. Output Format
# 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` |
1---2name: project-analysis3description: 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?"4---56# Project Analysis Skill78When analyzing a project, systematically gather and present information in this order:910## 1. Quick Overview (30 seconds)11```bash12# Check for common project markers13ls -la14cat README.md 2>/dev/null | head -5015```1617## 2. Tech Stack Detection1819### Package Managers & Dependencies20- `package.json` → Node.js/JavaScript/TypeScript21- `requirements.txt` / `pyproject.toml` / `setup.py` → Python22- `go.mod` → Go23- `Cargo.toml` → Rust24- `pom.xml` / `build.gradle` → Java25- `Gemfile` → Ruby2627### Frameworks (from dependencies)28- React, Vue, Angular, Next.js, Nuxt29- Express, FastAPI, Django, Flask, Rails30- Spring Boot, Gin, Echo3132### Infrastructure33- `Dockerfile`, `docker-compose.yml` → Containerized34- `kubernetes/`, `k8s/` → Kubernetes35- `terraform/`, `.tf` files → IaC36- `serverless.yml` → Serverless Framework37- `.github/workflows/` → GitHub Actions3839## 3. Project Structure Analysis4041Present as a tree with annotations:42```43project/44├── src/ # Source code45│ ├── components/ # UI components (React/Vue)46│ ├── services/ # Business logic47│ ├── models/ # Data models48│ └── utils/ # Shared utilities49├── tests/ # Test files50├── docs/ # Documentation51└── config/ # Configuration52```5354## 4. Key Patterns Identification5556Look for and report:57- **Architecture**: Monolith, Microservices, Serverless, Monorepo58- **API Style**: REST, GraphQL, gRPC, tRPC59- **State Management**: Redux, Zustand, MobX, Context60- **Database**: SQL, NoSQL, ORM used61- **Authentication**: JWT, OAuth, Sessions62- **Testing**: Jest, Pytest, Go test, etc.6364## 5. Development Workflow6566Check for:67- `.eslintrc`, `.prettierrc` → Linting/Formatting68- `.husky/` → Git hooks69- `Makefile` → Build commands70- `scripts/` in package.json → NPM scripts7172## 6. Output Format7374```markdown75# Project: [Name]7677## Overview78[1-2 sentence description]7980## Tech Stack81| Category | Technology |82|----------|------------|83| Language | TypeScript |84| Framework | Next.js 14 |85| Database | PostgreSQL |86| ... | ... |8788## Architecture89[Description with simple ASCII diagram if helpful]9091## Key Directories92- `src/` - [purpose]93- `lib/` - [purpose]9495## Entry Points96- Main: `src/index.ts`97- API: `src/api/`98- Tests: `npm test`99100## Conventions101- [Naming conventions]102- [File organization patterns]103- [Code style preferences]104105## Quick Commands106| Action | Command |107|--------|---------|108| Install | `npm install` |109| Dev | `npm run dev` |110| Test | `npm test` |111| Build | `npm run build` |112```