2026EXPERIMENTSHIPPED

Solaar

A multi-agent development agency built entirely with Claude Code. One orchestrator, eight specialized agents, and a persistent intelligence layer — the system knows your stack history, your production state, and which structural patterns in generated code are likely to fail before they reach users.

Visit Solaar

What it does

  • Accepts a project brief and runs eight specialized agents in sequence — strategist, UX designer, frontend, backend, security, PM, architect review, and production sentinel
  • Strategist selects one of six pipeline archetypes at Step 0 — landing page, SaaS web, API service, mobile Expo, mobile native Android, or content site — and skips steps that don't apply
  • UX agent produces a full design spec: color palette, typography scale, wireframes per route, responsive breakpoints, and an accessibility checklist
  • Frontend and backend agents run in parallel once the spec is approved — they write production-ready code, not scaffolds
  • Architect Review agent (Step 4.5) checks structural correctness before security: deployment target conformance, dual code path detection, API contract alignment, env var completeness, and Danger Map violations — findings classified as BLOCK, WARN, or INFO
  • Security agent audits output against OWASP Mobile/Web Top 10 before handoff; PM agent writes the release plan and task checklist
  • Production Sentinel fetches Vercel deployment status, Sentry error counts, and Lighthouse scores post-deploy; session open reads production health before any feature work starts
  • Client Knowledge Base tracks stack history, approved libraries, and accumulated lessons per client across all projects — Strategist reads it at Step 0 before any recommendation

Why it matters

  • Compresses time-to-first-deployable-repo from days to under 4 hours — strategy, design, frontend, backend, security, and PM done in one pipeline run
  • Blocking checkpoints prevent the most common AI coding failure mode: generating code before the design is validated
  • The system opens every session with production awareness — errors, performance regressions, and failed deploys surface before any new feature work begins
  • Ships to Vercel automatically via GitHub Actions — no manual deploy steps after the pipeline runs

Architecture

  • Claude Code as the runtime — each agent is a markdown instruction file read and executed in sequence
  • Six pipeline archetypes map to specific step sets — a landing page runs 7 steps; a full SaaS runs 14
  • Blocking checkpoints between agents require explicit user approval — strategy before design, design before code
  • Claude Design runs between the UX and Frontend agents to generate visual prototypes from the text spec before implementation
  • Project Danger Map captures the 3 landmines, 2 unconventional conventions, and 1 non-negotiable constraint from each session; every agent reads recent entries before starting
  • GitHub Actions CI/CD and Vercel Git Integration handle build, test, and deploy on every push to main

Philosophy

  • Describe the project once — the agents handle the rest, in the right order
  • Blocking checkpoints keep the user in control without being in the loop on every decision
  • Built to ship production code, not proof-of-concepts

Stack

  • CLAUDE CODE
  • AGENTS
  • MCP
  • GITHUB
  • CLAUDE DESIGN