Open source · MIT
Frontend spec-driven
development, done right
Kiro-style specs for Flutter, Next.js, and React Native — from requirements and gap analysis to UI design and implementation tasks.
Flutter
Next.js
React Native
Cursor MCP
Claude Desktop
Why SpecDrive
Structure for frontend teams
Backend has OpenAPI and Spec Kit. Frontend needs specs focused on screens, components, navigation, and accessibility.
Kiro-style gates
Approve requirements, gap-analysis, design, and tasks before writing code.
Gap analysis
Compare requirements against your codebase — know what's missing before design.
design.md drives UI
Screens, components, flows, state, and a11y in one UI blueprint.
AI-agnostic
Free LLM in CLI, or MCP in Cursor/Claude using your host AI keys.
Workflow
Four docs, one pipeline
requirements.md ✓
→
gap-analysis.md ✓
→
design.md ✓
→
tasks.md ✓
→
Implement
Quick start
Install in seconds
terminal
npm install -g @specdrive/cli
spec init --stack flutter
spec create "Product Review Screen"
export GEMINI_API_KEY="your-key"
spec gap-analysis --spec product-review-screen
Modes
CLI vs MCP
| Mode | Generates docs | API keys |
|---|---|---|
| CLI / npm | SpecDrive free LLM chain | GEMINI_API_KEY, Groq, or Ollama |
| MCP | Host AI (Cursor / Claude) | Your editor's key — SpecDrive never calls LLM |
Explore