You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Clone this repo, open Claude Code, and you have a full dev team in your terminal — architects, frontend/backend leads, framework specialists, QA engineers, and more.
What Is This?
This is not a web application. It's a configuration layer for Claude Code — a collection of markdown agent definitions, skill workflows, hooks, and docs that turn Claude Code into a structured web development environment.
When you open Claude Code in this directory, you get access to:
51 AI agents organized in a 3-tier studio hierarchy
54 slash commands (skills) covering the full development lifecycle
Automated hooks for commit validation and code quality checks
Or ask /help at any point to see where you are and what to do next.
Guided Workflow (Orchestration Layer)
The studio is designed to feel like a guided game — you're never left staring at a blank prompt wondering what to run next.
Handoff menus — every skill ends with a numbered "what's next?" block so you can pick the next step by number or stay and chat.
MVP anchor — /start and /brainstorm write a one-line MVP to .claude/session/mvp.md. It shows up in every skill's Status block so the north star is always visible.
Session breadcrumbs — each skill appends a timestamped line to .claude/session/active.md, giving you a running log of what's been done.
SessionStart hook — every time you open Claude Code in this directory, the hook surfaces your MVP, review mode, and the last 40 lines of breadcrumbs so context is never lost.
Review gates — pick a mode during /start:
solo — no gates, move fast
lean — directors review at phase boundaries (architecture, build, deploy)
full — directors review after every meaningful skill
At phase-boundary skills, the designated director (project-architect, tech-lead, or product-owner) is auto-spawned to review before the handoff. See .claude/docs/review-gates.md for the full trigger matrix.
MCP Integration (Optional)
The studio doesn't pre-wire any MCP servers — that would force Stripe / Supabase / Sentry accounts on everyone. Instead, install only what you use:
The full catalog with install commands and auth requirements lives in .claude/docs/mcp-servers.md. Most modern MCPs are hosted (OAuth) — zero secrets, just a URL. Once installed, relevant skills (/setup-payments, /setup-monitoring, /setup-analytics, etc.) automatically suggest using the MCP for live queries.
Vendor AI Rules
Many frameworks now publish AI-targeted resources — llms.txt files, official "AI rules" pages, or installable rule packs — that materially improve agent output. Specialists in this studio reference these when relevant:
Supabase — vendor-curated AI prompts for RLS, edge functions, SQL style
Stripe — building-with-llms guide + .md URL convention on docs
The full index lives in .claude/docs/ai-rules.md. Specialist agents (@supabase-specialist, @nextjs-specialist, @angular-developer, etc.) automatically fetch the relevant URL via WebFetch before generating non-trivial code.
Examples
Build a SaaS with Next.js + Stripe
/start my-saas
@project-architect Design architecture for a multi-tenant SaaS
/setup-auth # Auth with NextAuth.js
/setup-payments # Stripe subscriptions
/setup-email # Transactional emails with Resend
/setup-redis # Caching and rate limiting
Build a REST API with Go
/start my-api
@go-developer Set up a Gin API with clean architecture
/design-api # Define endpoints
/design-database # Design schema
/create-middleware auth # JWT auth middleware
/setup-redis # Response caching
Build a content site with Astro
/start my-blog
@astro-developer Set up Astro with content collections
/setup-seo # SEO optimization
/setup-i18n en,tr # Multilingual support
/setup-analytics # Privacy-friendly analytics
Project Structure
.claude/
├── agents/ # 51 AI agent definitions
│ ├── project-architect.md
│ ├── react-developer.md
│ ├── go-developer.md
│ ├── django-specialist.md
│ └── ...47 more
├── skills/ # 49 workflow skills
│ ├── start/SKILL.md
│ ├── brainstorm/SKILL.md
│ ├── setup-payments/SKILL.md
│ └── ...46 more
├── hooks/ # Validation + session hooks
│ ├── validate-commit.sh
│ ├── validate-web-assets.sh
│ └── session-start.sh # Surfaces MVP + breadcrumbs on load
├── docs/ # Studio documentation
│ ├── agent-roster.md
│ ├── quick-start.md
│ ├── handoff-template.md # Canonical end-of-skill format
│ ├── review-gates.md # Trigger matrix for director reviews
│ ├── mcp-servers.md # Official MCP server catalog
│ └── ai-rules.md # Vendor AI rules / llms.txt index
├── session/ # Runtime state (auto-managed)
│ ├── mvp.md # One-line MVP anchor
│ ├── active.md # Timestamped breadcrumbs
│ └── review-mode.txt # solo / lean / full
└── settings.json # Permissions and hook config
CLAUDE.md # Studio configuration
README.md # This file
How It Works
This project uses Claude Code's built-in features:
Agents (.claude/agents/*.md) — Each markdown file defines an AI agent with a specific role, expertise, model tier, and allowed tools. Claude Code loads these automatically.
Skills (.claude/skills/*/SKILL.md) — Each skill is a slash command that guides Claude through a structured workflow. Type /skill-name to run one.
Hooks (.claude/hooks/*.sh) — Bash scripts that run automatically on certain events (before commits, after file edits) to enforce quality standards.
Settings (.claude/settings.json) — Permissions, denied commands, and hook configuration.
No custom runtime, no API keys needed, no server to run. It's just configuration that makes Claude Code smarter about web development.
Contributing
Contributions are welcome:
Add new agents for frameworks or tools you use
Create new skills for workflows you need
Improve existing agent prompts with better expertise