# AI Coding Starter Kit > A Next.js template with an AI-powered development workflow using 6 specialized agents ## Vision Build web applications faster with AI agents handling Requirements, Architecture, Development, QA, and Deployment. Each agent has clear responsibilities and a human-in-the-loop workflow for quality control. --- ## Aktueller Status Template ready - Start by defining your first feature! --- ## Tech Stack ### Frontend - **Framework:** Next.js 16 (App Router) - **Sprache:** TypeScript - **Styling:** Tailwind CSS - **UI Library:** shadcn/ui (copy-paste components) ### Backend - **Database:** Supabase (PostgreSQL with Auth) - **State Management:** React useState / Context API - **Data Fetching:** React Server Components / fetch ### Deployment - **Hosting:** Vercel (oder Netlify) --- ## Features Roadmap ### Your Features Will Appear Here Start by defining your first feature using the Requirements Engineer agent: ``` Read .claude/agents/requirements-engineer.md and create a feature spec for [your feature idea] ``` Example roadmap structure: - [PROJ-1] Your First Feature β†’ πŸ”΅ Planned β†’ [Spec](/features/PROJ-1-feature-name.md) - [PROJ-2] Your Second Feature β†’ βšͺ Backlog --- ## Status-Legende - βšͺ Backlog (noch nicht gestartet) - πŸ”΅ Planned (Requirements geschrieben) - 🟑 In Review (User reviewt) - 🟒 In Development (Wird gebaut) - βœ… Done (Live + getestet) --- ## Development Workflow 1. **Requirements Engineer** erstellt Feature Spec β†’ User reviewt 2. **Solution Architect** designed Schema/Architecture β†’ User approved 3. **PROJECT_CONTEXT.md** Roadmap updaten (Status: πŸ”΅ Planned β†’ 🟒 In Development) 4. **Frontend + Backend Devs** implementieren β†’ User testet 5. **QA Engineer** fΓΌhrt Tests aus β†’ Bugs werden gemeldet 6. **DevOps** deployed β†’ Status: βœ… Done --- ## Environment Variables For projects using Supabase: ```bash NEXT_PUBLIC_SUPABASE_URL=your_supabase_url NEXT_PUBLIC_SUPABASE_ANON_KEY=your_anon_key ``` See `.env.local.example` for full list. --- ## Agent-Team Verantwortlichkeiten - **Requirements Engineer** (`.claude/agents/requirements-engineer.md`) - Feature Specs in `/features` erstellen - User Stories + Acceptance Criteria + Edge Cases - **Solution Architect** (`.claude/agents/solution-architect.md`) - Database Schema + Component Architecture designen - Tech-Entscheidungen treffen - **Frontend Developer** (`.claude/agents/frontend-dev.md`) - UI Components bauen (React + Tailwind + shadcn/ui) - Responsive Design + Accessibility - **Backend Developer** (`.claude/agents/backend-dev.md`) - Supabase Queries + Row Level Security Policies - API Routes + Server-Side Logic - **QA Engineer** (`.claude/agents/qa-engineer.md`) - Features gegen Acceptance Criteria testen - Bugs dokumentieren + priorisieren - **DevOps** (`.claude/agents/devops.md`) - Deployment zu Vercel - Environment Variables verwalten - Production-Ready Essentials (Error Tracking, Security Headers, Performance) --- ## Production-Ready Features This template includes production-readiness guides integrated into the agents: - **Error Tracking:** Sentry setup instructions (DevOps Agent) - **Security Headers:** XSS/Clickjacking protection (DevOps Agent) - **Performance:** Database indexing, query optimization (Backend Agent) - **Input Validation:** Zod schemas for API safety (Backend Agent) - **Caching:** Next.js caching strategies (Backend Agent) All guides are practical and include code examples ready to copy-paste. --- ## Design Decisions Document your architectural decisions here as your project evolves. **Template:** - **Why did we choose X over Y?** β†’ Reason 1 β†’ Reason 2 --- ## Folder Structure ``` ai-coding-starter-kit/ β”œβ”€β”€ .claude/ β”‚ └── agents/ ← 6 AI Agents (Requirements, Architect, Frontend, Backend, QA, DevOps) β”œβ”€β”€ features/ ← Feature Specs (Requirements Engineer creates these) β”‚ └── README.md ← Documentation on how to write feature specs β”œβ”€β”€ src/ β”‚ β”œβ”€β”€ app/ ← Pages (Next.js App Router) β”‚ β”œβ”€β”€ components/ ← React Components β”‚ β”‚ └── ui/ ← shadcn/ui components (add as needed) β”‚ └── lib/ ← Utility functions β”‚ β”œβ”€β”€ supabase.ts ← Supabase client (commented out by default) β”‚ └── utils.ts ← Helper functions β”œβ”€β”€ public/ ← Static files β”œβ”€β”€ PROJECT_CONTEXT.md ← This file - update as project grows └── package.json ``` --- ## Getting Started 1. **Install dependencies:** ```bash npm install ``` 2. **Setup Environment Variables (if using Supabase):** ```bash cp .env.local.example .env.local # Add your Supabase credentials ``` 3. **Start development server:** ```bash npm run dev ``` 4. **Start using the AI Agent workflow:** - Tell Claude to read `.claude/agents/requirements-engineer.md` and define your first feature - Follow the workflow: Requirements β†’ Architecture β†’ Development β†’ QA β†’ Deployment --- ## Next Steps 1. **Define your first feature idea** - Think about what you want to build 2. **Start with Requirements Engineer** - Tell Claude: "Read .claude/agents/requirements-engineer.md and create a feature spec for [your idea]" - The agent will ask clarifying questions and create a detailed spec 3. **Follow the AI Agent workflow** - Requirements β†’ Architecture β†’ Development β†’ QA β†’ Deployment - Each agent knows when to hand off to the next agent 4. **Track progress via Git** - Feature specs in `/features/PROJ-X.md` show status (Planned β†’ In Progress β†’ Deployed) - Git commits track all implementation details - Use `git log --grep="PROJ-X"` to see feature history --- **Built with AI Agent Team System + Claude Code**