From Vibe to Running App in One Day

This is the story of SolarScore, a solar proposal scoring platform built from zero to running application in a single day using StellarView.

Not a prototype. Not a demo. A PostgreSQL-backed, FastAPI-served, React-fronted application with 7 Alembic migrations, 30 API endpoints, 15 frontend pages, and 16 test files. 334 files total.

Here is exactly what happened, hour by hour.

10:00 AM: The Vibe

SolarScore started as a sentence: “Homeowners need a way to score solar installation proposals against pricing benchmarks and Florida regulatory requirements.”

That sentence went into the Vibe Creator. Stack selection: Express + React + PostgreSQL. The Creator agent generated the data model, routes, SQL schema, seed data. Twenty minutes.

-- What Vibe Creator generated (seed.sql excerpt)
INSERT INTO companies (name, state_code, letter_grade, overall_score)
VALUES 
 ('SunPower Solutions', 'FL', 'A', 92),
 ('Momentum Solar', 'FL', 'B', 78),
 ('Freedom Solar Power', 'TX', 'A', 88);

The app was running on port 3221 inside the Vibe panel. A real dashboard. Real API endpoints. Real database queries.

11:00 AM: The Hydrate

One click. Deploy tab → “Hydrate into Galaxy” → Galaxy name: SolarScore.

The Vibe project became a StellarView galaxy. Registered in the galaxy registry. Files copied. Space Lake ingested 45 documents. Ready for epics.

{
 "id": "SolarScore",
 "name": "SolarScore", 
 "source": "vibe-creator",
 "projectPath": "/Users/joe/Forks/solarscore"
}

12:00 PM: The Epic

Big Bang Epic Creator. Pasted the full specification, 11 phases covering:

1. Foundation Infrastructure and Data Model
2. Proposal Intelligence Engine
3. Company Data Ingestion and Discovery
4. Company Report Cards and Trust Scoring
5. RAG AI Advisor Mode
6. Consumer Advocate Layer
7. Subscription Monetization

Each phase decomposed into 8 work units with functional requirements, acceptance criteria, and architecture diagrams.

78 work units. 220 functional requirements. 166 open gaps identified by the AI. All visible, all editable, all addressable before a single line of code is written.

1:00 PM: The Unleash

Hit “Unleash.” Seven GitHub issues created on practicai-org/solarscore, each with the full work unit specification, architecture diagrams, and gap list. JIRA tickets mirrored in the SOLARSCORE project.

Then: Miracle Mode.

1:00 PM → 6:00 AM: The Miracle

Miracle ran autonomously overnight. Phase by phase:

1. Analyze the issue (3-phase Smart Prompt: requirements → architecture → implementation plan)
2. Execute the code (Claude Code in an isolated worktree)
3. Commit and push to a feature branch
4. Move to the next phase

Each phase built on the previous phase’s branch. Branch chaining ensured Phase 2 saw Phase 1’s code. Phase 3 saw both. The architecture accumulated coherently.

Cosmic emissions from the run:

Phase	Duration	Input Tokens	Output Tokens	Files Changed
1	14 min	45K	12K	89
2	15 min	52K	14K	34
3	18 min	48K	11K	28
4	29 min	61K	18K	42
5	26 min	55K	15K	31
6	19 min	49K	13K	38
7	20 min	53K	14K	72

8:00 AM Next Morning: The Result

Seven feature branches on GitHub. All merged cleanly into solarmiracle:

$ git log solarmiracle --oneline
e227385 feat: Resolve issue #8 - Phase 7: Subscription Monetization
36fa606 feat: Resolve issue #7 - Phase 6: Consumer Advocate Layer
06a75f1 feat: Resolve issue #6 - Phase 5: RAG AI Advisor Mode
954e3d6 feat: Resolve issue #5 - Phase 4: Company Report Cards
2f84119 feat: Resolve issue #4 - Phase 3: Company Data Ingestion
e00a1b8 feat: Resolve issue #3 - Phase 2: Proposal Intelligence
98a3104 feat: Resolve issue #2 - Phase 1: Foundation Infrastructure

334 files. Python/FastAPI backend with Alembic migrations. React/TypeScript frontend. Terraform infrastructure modules. Docker Compose. CI/CD workflows. README with working make setup instructions.

What This Means

A single practitioner designed, decomposed, and executed a complete platform in one day. Not by writing 334 files by hand. By holding the vision, directing the platform, and letting the discipline carry the execution.

This is what the Modern Principal does. This is what the practice looks like.

The repo is live: practicai-org/solarscore

What happened next: The Forge. Why Generated Code Must Boot