.skaro/ directory that lives next to your code and is version-controlled with Git.
Philosophy
Developer is the architect. LLM is the amplifier. You make the decisions. The LLM helps you explore options, generate code, review for blind spots, and maintain consistency. Skaro provides the structure to make this collaboration repeatable and reliable.What Skaro Does
Skaro wraps your development workflow in a phase-based process where each phase produces a concrete artifact:- Constitution — your project’s immutable principles: stack, standards, constraints, security rules
- Architecture — component map, invariants, and Architecture Decision Records (ADRs)
- Clarify — LLM-driven Q&A to find gaps in your specification before you start coding
- Plan — decomposition into stages with dependencies and Definition of Done
- Implement — stage-by-stage code generation with AI notes for each stage
- Tests — verification commands and LLM-assisted test generation
- Project Review — cross-validation of spec vs code vs architecture (project-wide)
.skaro/. Every LLM call receives the relevant files as context. You can switch LLM providers, start a new chat, or hand off to a teammate — the context is always in the repository.
Key Features
CLI + Web Dashboard
Bootstrap projects with
skaro init, then run phases through a web dashboard at localhost:4700.Multi-Provider LLM
Anthropic, OpenAI, Groq, or Ollama. Use different models for different roles (architect, coder, reviewer).
12 Constitution Presets
Ready-made templates for React, Next.js, FastAPI, Django, Flutter, and more.
Existing Project Import
Run
skaro init on an existing codebase — the LLM analyzes it and generates initial artifacts automatically.How It Fits Your Workflow
Skaro is not a code editor, IDE plugin, or CI system. It is a specification layer that sits between you and your LLM:- You describe what to build (in specs and constitution)
- Skaro feeds the right context to the LLM at each phase
- The LLM produces artifacts and code
- You review, approve, and commit