SPARK_ACCELERATOR
STEPS:0/5
DAY 1// FOUNDATION & REALITY INSTALL

Foundation & Reality Install

"I am an operator, not a learner."

LED BY

Damien Rufus

$spark ini_
Hard Win

App running and under your complete control.

$spark stack --list

Production-Grade Infrastructure

Built on the same stack that powers real businesses. No toy frameworks, no rented platforms. You own every layer.

N
Next.js 16
Framework
R
React 19
UI Library
TS
TypeScript
Language
SB
Supabase
Backend
PG
PostgreSQL
Database
S
Stripe
Payments
TW
Tailwind 4
Styling
V
Vercel
Hosting
build sequence
$spark build --steps

The Build Sequence

Check off each step as you complete it. Your progress is saved automatically.

[01]

Start with a proven template

No building from scratch. You begin with production-grade infrastructure that's already been battle-tested.

[02]

Connect your infrastructure

Database, hosting, security — all connected and configured. You own every piece.

[03]

Set up authentication

Users can sign up and log in. Professional-grade security with server-side session handling.

[04]

See your app running live

Real URL, real users. Your app is deployed and running on the internet.

[05]

Learn how to recover if something breaks

Things will break. That's normal. Knowing how to recover is what separates operators from learners.

$spark infra --diagram

Your Infrastructure

Every piece of infrastructure you connect today is something you own. No platform dependency. No rent extraction. No hidden costs.

Database// PostgreSQL via Supabase
connected
Auth// Supabase Auth + SSR
configured
Hosting// Vercel Edge Network
ready
Security// RLS + Server-side checks
active
coding document
$spark doc --template

One-Shot App Builder Document

This is the coding document you paste into Claude Code. All dependencies have been verified and updated to their latest versions as of February 27, 2026.

AppTemplate.md// one-shot builder doc

// Updated Install Commands (Feb 27, 2026)

dependency audit
$spark deps --audit

Dependency Audit

Every package verified against npm registry. Green means the doc version range covers the latest release. Orange means the doc should be updated to reflect the latest.

// Core

packagedoc_verlateststatus
next16+16.1.6
react19.2+19.2.4
react-dom19.2+19.2.4
typescript5.7+5.9.3

// Backend

packagedoc_verlateststatus
@supabase/supabase-jslatest2.98.0
@supabase/ssrlatest0.8.0

// UI

packagedoc_verlateststatus
tailwindcss4.1+4.2.1
@radix-ui/react-slotlatest1.2.4
class-variance-authoritylatest0.7.1
clsxlatest2.1.1
tailwind-mergelatest3.5.0
lucide-reactlatest0.575.0
sonnerlatest2.0.7

// State

packagedoc_verlateststatus
zustand5+5.0.11
@tanstack/react-query5+5.90.21

// Forms

packagedoc_verlateststatus
react-hook-form7.71+7.71.2
@hookform/resolverslatest5.2.2

// Validation

packagedoc_verlateststatus
zod4+4.3.6

// DnD

packagedoc_verlateststatus
@dnd-kit/corelatest6.3.1
@dnd-kit/sortablelatest10.0.0

// AI

packagedoc_verlateststatus
ai6+6.0.103
@ai-sdk/openailatest3.0.36
@ai-sdk/anthropiclatest3.0.48
@ai-sdk/googlelatest3.0.33
$spark recovery --playbook

When Things Break

Operators don't panic when things break. They follow the playbook.

recovery-playbook.sh
# The Recovery Playbook
# =====================

# 1. IDENTIFY — What broke?
git diff HEAD~1        # See what changed
vercel logs            # Check deployment logs

# 2. ISOLATE — Stop the bleeding
vercel rollback        # Restore last working version

# 3. FIX — Address the root cause
git stash              # Save current changes
git checkout main      # Start from clean state

# 4. VERIFY — Confirm the fix
pnpm dev               # Test locally first
vercel --prod          # Deploy when confident

# 5. DOCUMENT — Learn from it
# → Add to your team's runbook

Day 1 Complete

Tomorrow you deploy to the internet, connect Stripe for real payments, and install marketing infrastructure. By the end of Day 2, your app will be accepting money.

Day 1

Foundation

in progress
Day 2

Deploy & Monetize

Day 3

Ship & Scale