π Hanoi Rainbow
Build Better Software with AI-Powered Specifications
Stop guessing. Start specifying.
Turn your ideas into production-ready applications through clear specifications, not trial-and-error coding.
π‘ What is Spec-Driven Development?
Traditional approach: Write code first, figure it out as you go.
Spec-Driven approach: Define what you want first, then let AI build it right.
For decades, we treated specifications as throwaway notesβjust a formality before the "real" coding began. Spec-Driven Development flips this around: your specification becomes the blueprint that directly generates working code, not just a suggestion.
Think of it like architecture: You wouldn't build a house without blueprints. Why build software without clear specifications?
π Getting Started
New to Hanoi Rainbow? Follow these guides:
| Guide | Description |
|---|---|
| π¦ Installation Guide | Set up Rainbow CLI and prerequisites |
| β‘ Quick Start Guide | Build your first project in minutes |
| π Upgrade Guide | Update to the latest version |
| π» Local Development | Contribute and develop locally |
Project Workflows
Choose your workflow based on project type:
| Workflow | Best For | Timeline |
|---|---|---|
| π± Greenfield | New applications from scratch | 2-4 weeks (MVP) |
| ποΈ Brownfield | Adding features to existing apps | 1-2 weeks/feature |
π― Available Commands
After installation, you'll have access to these slash commands in your AI assistant:
Core Workflow Commands
| Command | Purpose |
|---|---|
/rainbow.regulate |
Set project principles and ground rules |
/rainbow.specify |
Define requirements and user stories |
/rainbow.design |
Create technical implementation plans |
/rainbow.taskify |
Break down into actionable tasks |
/rainbow.implement |
Execute all tasks and build the feature |
Product-Level Commands
Run these once per product, not per feature:
| Command | Purpose |
|---|---|
/rainbow.architect |
Design system architecture with C4 diagrams |
/rainbow.standardize |
Create coding standards and conventions |
/rainbow.design-e2e-test |
Design end-to-end test specifications |
/rainbow.perform-e2e-test |
Execute end-to-end tests |
Quality & Enhancement Commands
| Command | Purpose |
|---|---|
/rainbow.clarify |
Clarify unclear requirements |
/rainbow.analyze |
Check consistency across specifications |
/rainbow.checklist |
Generate quality validation checklists |
/rainbow.taskstoissues |
Convert tasks to GitHub issues |
π― Core Philosophy
Spec-Driven Development is built on these principles:
| Principle | What It Means |
|---|---|
| Intent First | Define the "what" and "why" before the "how" |
| Rich Specifications | Create detailed specs with organizational principles |
| Step-by-Step | Improve through multiple steps, not one-shot generation |
| AI-Powered | Use advanced AI to interpret specs and generate code |
π When to Use This
| Scenario | What You Can Do |
|---|---|
| π New Projects |
|
| π¬ Exploration |
|
| π§ Existing Projects |
|
π¬ What We're Exploring
Our experiments focus on making Spec-Driven Development work for real teams:
- π§ Tech Independence - Build apps with any tech stack, proving this process works across languages and frameworks
- π’ Enterprise Ready - Support organizational constraints: cloud providers, compliance requirements, design systems
- π₯ User Focused - Build for different user needs and development styles (from exploratory coding to structured workflows)
- π Iterative & Creative - Enable parallel exploration of solutions and robust workflows for modernization
π€ Contributing
Want to help improve Hanoi Rainbow? Check our Contributing Guide to get started.
Ways to contribute:
- π Report bugs or issues
- π‘ Suggest new features
- π Improve documentation
- π§ Submit code improvements
π¬ Get Help
Need assistance?
- π Support Guide - Common questions and solutions
- π Open an Issue - Report bugs or request features
- π Discussions - Ask questions and share ideas