Stack
- Framework: Next.js 14 (App Router)
- Language: TypeScript (strict mode)
- Styling: Tailwind CSS + shadcn/ui
- Database: PostgreSQL with Drizzle ORM
- Auth: Auth.js (NextAuth v5)
Commands
npm run dev— Start dev server (port 3000)npm run build— Production buildnpm run test— Run Vitest testsnpm run lint— Run Biome linter
Code Conventions
- Functional components only
- Server Components by default, Client Components with "use client"
- Use Zustand for client state, React Query for server state
- All API routes return { data, error } shape
- Database queries use Drizzle ORM (no raw SQL)
File Structure
- src/app/ — Pages and layouts (App Router)
- src/components/ — Shared UI components
- src/lib/ — Utilities, database, auth config
- src/server/ — Server-side logic
Do NOT
- Do not use Redux, Context API, or class components
- Do not create CSS modules or styled-components
- Do not add comments explaining obvious code
- Do not use any as a TypeScript type EOF
2. Configure essential MCP servers
cat > .mcp.json << 'MCPEOF' { "mcpServers": { "github": { "command": "npx", "args": ["-y", "@modelcontextprotocol/server-github"], "env": { "GITHUB_TOKEN": "${GITHUB_TOKEN}" } }, "postgres": { "command": "npx", "args": ["-y", "@modelcontextprotocol/server-postgres"], "env": { "POSTGRES_CONNECTION_STRING": "${DATABASE_URL}" } } } } MCPEOF
echo "Done! Open Claude Code and start building."
---
## What is Included
### 1. CLAUDE.md Templates
**Web App (Next.js):**
- Stack, commands, conventions, file structure
- Do/Don't rules for consistent AI output
- Database and auth patterns
**API Server (Hono/Express):**
- REST conventions, error handling patterns
- Middleware patterns, validation rules
- Testing and deployment commands
**Python Project (FastAPI):**
- Type hints everywhere, async patterns
- Pydantic models for I/O
- Testing and linting commands
### 2. MCP Configuration (.mcp.json)
Essential servers for every project:
```json
{
"mcpServers": {
"github": { "...": "PR management, issue tracking" },
"postgres": { "...": "Database queries and schema" },
"filesystem": { "...": "Access to shared config dirs" }
}
}Optional servers by use case:
| Use Case | MCP Server |
|---|---|
| Web scraping | Firecrawl MCP |
| Search | Tavily MCP |
| Monitoring | Sentry MCP |
| Payments | Stripe MCP |
| Team chat | Slack MCP |
| Diagrams | Excalidraw |
3. Recommended Skills
# Install from TokRepo
npx skills install react-best-practices
npx skills install api-security
npx skills install git-workflow4. Git Hooks (via Claude Code Hooks)
{
"hooks": {
"PostToolUse": [{
"matcher": "Write|Edit",
"command": "npx biome check --write $CLAUDE_FILE_PATH 2>/dev/null || true"
}]
}
}5. Environment Template
# .env.example
DATABASE_URL=postgresql://localhost:5432/myapp
GITHUB_TOKEN=ghp_xxx
ANTHROPIC_API_KEY=sk-ant-xxxProject Templates
Minimal (any project)
CLAUDE.md # Project conventions
.mcp.json # MCP servers
.env.example # Required env varsFull Stack (Next.js + Postgres)
CLAUDE.md
.mcp.json
.env.example
biome.json # Linter config
drizzle.config.ts # ORM configPython API
CLAUDE.md
.mcp.json
.env.example
pyproject.toml # UV/pip config
ruff.toml # Linter configKey Stats
- Templates for 3+ project types
- Essential MCP server configs
- Claude Code hooks for auto-formatting
- Environment variable templates
- 2-minute setup
FAQ
Q: What is the AI Project Starter Kit? A: A pre-configured bundle of CLAUDE.md, MCP servers, skills, and hooks that makes any new project instantly productive with Claude Code.
Q: Do I need all the MCP servers? A: No, start with GitHub and your database. Add others as needed.
Q: Can I customize the templates? A: Yes, the templates are starting points. Modify CLAUDE.md to match your project conventions.