Skeleton Projects Workflow
Use existing, battle-tested repositories as scaffolding for new projects instead of starting from scratch.
When to Use
- Starting a new project with known technology stack
- Standardizing team patterns across multiple services
- Rapid prototyping where architecture decisions are already made
- Onboarding new team members via a working reference
Don't use when: Exploring unknown tech (use Vibe Coding instead), or when requirements are too unique for existing templates.
Prerequisites
- Claude Code installed and configured
- Git access to reference repositories
- Clear understanding of target project requirements
Step-by-Step Guide
Phase 1: Find and Evaluate a Skeleton
Don't build from zero. Find an existing repo that matches your target architecture.
Step 1: Search for candidates
bash
# Ask Claude to help find reference repos
claude -p "I need a skeleton for a Next.js 15 app with:
- App Router
- Prisma ORM with PostgreSQL
- tRPC for type-safe API
- Tailwind CSS
- Jest + Playwright testing
Search GitHub for well-maintained starter templates.
Evaluate the top 3 by: last commit date, stars, dependency freshness, test coverage."Step 2: Clone and audit
bash