AI-powered product management platform that transforms raw startup ideas into execution-ready documentation and GitHub backlogs.
Features • Quick Start • Documentation • Contributing • Community
Building a startup is hard. You have a brilliant idea, but turning it into a structured plan with clear requirements, technical designs, and actionable tasks is time-consuming and requires expertise.
No Vibe No Code bridges the gap between ideation and execution:
- 🚀 Validate Fast: Get AI-powered analysis of your startup idea in minutes, not days
- 📝 Document Automatically: Generate professional PRDs, technical designs, and architecture docs
- 🎯 Execute Confidently: Transform analysis into GitHub issues and project boards (coming soon)
- 🏗️ Built Right: Hexagonal architecture ensures maintainability and extensibility
- 🧪 Quality First: Property-based testing guarantees system correctness
Perfect for indie hackers, product managers, hackathon teams, and innovation labs who want to move from idea to execution quickly.
- Idea Analysis: AI-powered startup idea evaluation with detailed scoring and feedback
- Hackathon Analyzer: Specialized evaluation for hackathon projects (Kiroween theme)
- Doctor Frankenstein: AI-powered mashup idea generator combining tech company or AWS service technologies
- Idea Panel: Dedicated workspace for managing ideas with status tracking, notes, tags, and multiple analyses
- Document Generation: AI-generated PRDs, Technical Designs, Architecture Documents, and Roadmaps
- Multi-language Support: Full English and Spanish localization
- Credit System: Usage-based credit system with tier-based limits
- Node.js 18+ and npm
- Google Gemini API Key (Get one free)
- Supabase Account (Sign up free) - or use local storage mode (coming soon)
- Clone the repository
git clone https://github.com/amllamojha/no-vibe-no-code-kiroween.git
cd no-vibe-no-code- Install dependencies
npm install-
Set up Supabase
a. Create a new project at supabase.com (free tier is fine)
b. Enable Email Authentication:
- Go to Authentication > Providers
- Enable "Email" provider
- (Optional) Configure email templates
c. Run the database schema:
- Go to SQL Editor in your Supabase dashboard
- Click "New Query"
- Copy the entire contents of
supabase_seed.sqlfrom this repo - Paste and click "Run"
- You should see "Success. No rows returned"
d. Get your API credentials:
- Go to Project Settings > API
- Copy your "Project URL" (looks like
https://xxxxx.supabase.co) - Copy your "anon public" key (starts with
eyJ...)
-
Get a Google Gemini API Key
- Visit Google AI Studio
- Click "Get API Key"
- Create a new API key (free tier available)
- Copy the key
-
Configure environment variables
# Copy the example file
cp .env.example .env.localEdit .env.local with your actual values:
# Required: Google Gemini AI
GEMINI_API_KEY=your_actual_gemini_api_key_here
# Required: Supabase
NEXT_PUBLIC_SUPABASE_URL=https://your-project-id.supabase.co
NEXT_PUBLIC_SUPABASE_ANON_KEY=%YOUR_KEY_HERE%
# Optional: Analytics (leave blank to disable - app works fine without it)
NEXT_PUBLIC_POSTHOG_KEY=
NEXT_PUBLIC_POSTHOG_HOST=
# Optional: Mock mode (for testing without API costs)
FF_USE_MOCK_API=false- Run the development server
npm run dev- Open your browser
Navigate to http://localhost:3000
-
Create an account
- Click "Sign Up"
- Use any email/password (Supabase will create the account)
- You'll start with 3 free credits
"Failed to fetch" or connection errors:
- Verify your Supabase URL and anon key are correct
- Check that you ran the
supabase_seed.sqlscript - Ensure email auth is enabled in Supabase
"Invalid API key" errors:
- Verify your Gemini API key is correct
- Check you have API quota remaining (free tier has limits)
"Insufficient credits" errors:
- Default users get 20 credits
- Each analysis costs 1 credit
- You can manually add credits in Supabase (profiles table)
Database errors:
- Make sure you ran the complete
supabase_seed.sqlfile - Check the Supabase logs in Dashboard > Logs
Still having issues?
- Check GitHub Issues
- Ask in Discussions
For a simpler setup without Supabase, enable local storage mode:
# .env.local
FF_LOCAL_STORAGE_MODE=true
LOCAL_AUTH_USERNAME=kiro
LOCAL_AUTH_PASSWORD=kiro
GEMINI_API_KEY=your_gemini_api_key_hereThis mode stores all data in browser localStorage - perfect for testing and personal use.
Check out Spooky Snippets Studio — a complete example project built using No Vibe No Code's document generation workflow.
This Halloween-themed WebGL gallery demonstrates:
-
Generated Documentation (
examples/spooky-snippets/docs/)- PRD — Product requirements and user stories
- Technical Design — Architecture and implementation planning
- Tech Architecture — System architecture details
- Roadmap — Milestones and feature prioritization
-
Kiro Setup (
examples/spooky-snippets/.kiro/)- Specs and steering files used during development
- Reusable patterns for your own projects
The project went from idea → analysis → documentation → working code using the No Vibe No Code workflow.
The application follows hexagonal architecture (Ports and Adapters pattern):
- Domain Layer (
src/domain/): Pure business logic with strongly-typed entities and value objects - Application Layer (
src/application/): Use cases and application services - Infrastructure Layer (
src/infrastructure/): External adapters (database, AI services, web) - Features (
features/): UI components and client-side logic
- Architecture Overview: Comprehensive architecture documentation
- Developer Guide: Step-by-step guide for adding new features
- API Documentation: Complete API reference
- Database Schema: Current database schema and query patterns
- Hexagonal Architecture Standards: Architecture standards and guidelines
- Document Generation Guide: Complete guide for AI-generated documentation
- Idea Panel User Guide: User guide for the Idea Panel feature
- Mock System Documentation: Mock system for development without API costs
Generate professional project documentation from your analyzed ideas:
| Document Type | Credit Cost | Purpose |
|---|---|---|
| PRD | 1 | Product requirements and user stories |
| Technical Design | 1 | Architecture and implementation planning |
| Architecture | 1 | System architecture and infrastructure |
| Roadmap | 1 | Milestones and feature prioritization |
Note: Initial analysis is also 1 credit. Default free tier includes 20 credits.
Recommended Workflow: Analysis → PRD → Technical Design → Architecture → Roadmap
# Unit tests
npm test # Run once
npm run test:watch # Watch mode
npm run test:coverage # With coverage
# Property tests
npm run test:properties # Run property tests
npm run test:properties:coverage # With coverage
# E2E tests
npm run test:e2e # Run E2E tests
npm run test:e2e:ui # Interactive UI mode
npm run test:e2e:headed # Headed browser modeEnable mock mode for development without consuming API credits:
# .env.local
FF_USE_MOCK_API=true
FF_MOCK_SCENARIO=success
FF_SIMULATE_LATENCY=trueControl features via environment variables:
| Flag | Description | Default |
|---|---|---|
NEXT_PUBLIC_FF_ENABLE_CLASSIC_ANALYZER |
Classic analyzer visibility | true |
NEXT_PUBLIC_FF_ENABLE_KIROWEEN_ANALYZER |
Hackathon analyzer visibility | true |
FF_USE_MOCK_API |
Enable mock mode | false |
ENABLE_DOCUMENT_GENERATION |
Document generation feature | true |
Automated quality checks on every pull request:
- ESLint: Code quality and linting
- Unit Tests: Vitest with coverage reporting
- E2E Tests: Playwright browser automation
- Lighthouse: Accessibility audits (90% minimum score)
- Property Tests: Property-based testing validation
// ✅ Correct: Fresh client per request
const supabase = SupabaseAdapter.getServerClient();
// ❌ Wrong: Cached client causes session leaks
const cachedClient = createClient(); // Don't do this# Required
GEMINI_API_KEY=your_gemini_api_key
NEXT_PUBLIC_SUPABASE_URL=your_supabase_url
NEXT_PUBLIC_SUPABASE_ANON_KEY=your_supabase_anon_key
NEXT_PUBLIC_SITE_URL=http://localhost:3000
# Optional - Analytics
NEXT_PUBLIC_POSTHOG_KEY=your_posthog_key
NEXT_PUBLIC_POSTHOG_HOST=your_posthog_host
POSTHOG_API_KEY=your_posthog_server_key
# Optional - Mock Mode
FF_USE_MOCK_API=true
FF_MOCK_SCENARIO=success
FF_SIMULATE_LATENCY=true
# Optional - Tuning
AI_TIMEOUT=30000
AI_MAX_RETRIES=3
LOG_LEVEL=info
LOCAL_DEV_CREDITS=20
NEXT_PUBLIC_FF_CLASSIC_ANALYZER=true
NEXT_PUBLIC_FF_HACKATHON_ANALYZER=true
NEXT_PUBLIC_FF_AUDIO_FEATURES=falsesrc/
├── domain/ # Business logic (entities, value objects, services)
├── application/ # Use cases and handlers
├── infrastructure/ # Database, AI, web adapters
└── shared/ # Common utilities
features/
├── analyzer/ # Startup idea analysis
├── kiroween-analyzer/# Hackathon analysis
├── doctor-frankenstein/ # Idea mashup generator
├── idea-panel/ # Idea management workspace
├── document-generator/ # AI document generation
├── dashboard/ # User dashboard
└── auth/ # Authentication
app/
├── api/v2/ # API endpoints
├── generate/ # Document generation pages
├── idea/ # Idea Panel pages
└── ... # Other pages
We welcome contributions! Whether it's bug fixes, new features, documentation improvements, or feedback, your help makes this project better.
-
Fork the repository and create a new branch
git checkout -b feature/your-feature-name
-
Follow our standards
- Adhere to hexagonal architecture
- Write tests for new functionality (unit + property tests)
- Follow TypeScript strict mode
- Use conventional commit messages
-
Test your changes
npm run lint # Check code quality npm test # Run unit tests npm run test:properties # Run property tests npm run test:e2e # Run E2E tests
-
Submit a Pull Request
- Provide a clear description of the changes
- Reference any related issues
- Ensure all CI checks pass
- Architecture: Follow hexagonal architecture - domain layer has no dependencies
- Testing: Write property-based tests for business rules and invariants
- Code Style: ESLint + Prettier (auto-formatted on save)
- Commits: Use conventional commits (
feat:,fix:,docs:, etc.) - Documentation: Update docs when adding features
- 🐛 Bug fixes and issue triage
- 📝 Documentation improvements
- 🌍 Translations (currently EN/ES, need more languages)
- ✨ New features (check open issues)
- 🧪 More property tests for system correctness
- 🎨 UI/UX improvements
Be respectful, inclusive, and constructive. We're all here to build something great together.
See CONTRIBUTING.md for detailed guidelines.
Completed ✅
- Core analysis engine (startup + hackathon)
- Document generation (PRD, Technical Design, Architecture, Roadmap)
- Idea Panel with status tracking and notes
- Multi-language support (EN/ES)
- Credit system with tier management
- Property-based testing framework
- Mock mode for development
In Progress 🚧
- Local storage mode (no Supabase required)
- Enhanced export capabilities
- E2E test coverage
Coming Soon 🔜
- GitHub integration (export to issues/projects)
- Collaborative editing
- Template system for custom documents
- API access for programmatic integration
- More AI model support (Claude, etc.)
See open issues for detailed roadmap and feature requests.
- 💬 Discussions: GitHub Discussions - Ask questions, share ideas
- 🐛 Bug Reports: GitHub Issues - Report bugs or request features
- 📧 Email: [email protected] - Direct support
- 🐦 Twitter: @novibenocode - Updates and announcements
- ⭐ Star this repo - Helps others discover the project
- 🐛 Report bugs - Help us improve quality
- 💡 Suggest features - Share your ideas
- 📝 Improve docs - Make it easier for others
- 🔀 Submit PRs - Contribute code
Built with amazing open source tools:
- Next.js - React framework
- Supabase - Backend and authentication
- Google Gemini - AI analysis
- Vitest - Testing framework
- Playwright - E2E testing
- Tailwind CSS - Styling
Special thanks to all contributors who help make this project better!
This project is licensed under the GNU Affero General Public License v3.0 or later (AGPL-3.0-or-later).
See the LICENSE file for the full license text.
- ✅ You can use, modify, and distribute this software
- ✅ You must share your modifications under the same license
- ✅ If you run a modified version on a server, you must provide the source code to users
- ✅ You must include copyright and license notices
For more information, visit: https://www.gnu.org/licenses/agpl-3.0.html
Built with ❤️ by the No Vibe No Code community
Website • Documentation • Contributing
Last updated: December 3, 2025