🌈 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
  • Start with high-level requirements
  • Generate complete specifications
  • Plan implementation steps
  • Build production-ready apps
πŸ”¬ Exploration
  • Try different solutions in parallel
  • Test multiple tech stacks
  • Experiment with UX patterns
πŸ”§ Existing Projects
  • Add new features systematically
  • Modernize legacy code
  • Adapt processes to your needs

πŸ”¬ 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?