Night Shift

>_ how this was built

One owner, one agent,
one build week.

Night Shift was built for Vibeathon 02 from an empty Next.js project. The owner directed it in plain language; Claude Code wrote, tested and shipped the code. This page says who did what.

>_ tools

The AI tools

Claude Code (Claude Opus 5.5, with Sonnet 5.5 for a few late tasks)

The builder. Run in the Claude desktop app, it planned each feature, wrote the code, ran it locally, tested it and shipped it through GitHub to Vercel. For the final push, two Claude sessions worked in parallel: one on app features, one on these docs.

A small model in the product (Groq free tier, or Claude Haiku)

The overnight analyst (summary, tags, strengths, risks, launch readiness) and the Morning Report's headline and picks. JSON validated with zod; if it fails, the analyst shows site checks only and the report uses the scouts' own notes.

>_ workflow

The agent loop

  1. 01 · Direct

    The owner set the goal or reacted to the last build in plain words.

  2. 02 · Plan

    Claude read the code, proposed the change and the trade-offs, and waited for a go-ahead.

  3. 03 · Build

    Claude wrote the code, the schema changes and the copy.

  4. 04 · Test

    Claude ran the app locally, including scripted end-to-end checks that signed flares and claims with throwaway wallets, and ran the production build (type check and lint).

  5. 05 · Ship

    Commits pushed to GitHub on the owner's go-ahead, deployed by Vercel, then checked on the live site.

>_ prompts

Real prompts from the build

Quoted as typed, typos included.

“A community-powered discovery network where anyone can surface promising projects, supporters help them gain traction, and founders decide what happens next.”

The opening brief. Scouts, flares and founder decisions all grew from this sentence.

“judge its against the past vibeathon edition and check which one wins”

Claude compared it with Vibeathon 01's winners and found it weakest on launch potential. That led to wallet-signed flares on Base and positioning Night Shift as a pipeline into raising on Vibestarter.

“i feel like this cant win its just look like something anyone can build or look over”

The turning point on identity: it led to the flares-left counter, the how-it-works strip, and the night skyline where every flare lights a window.

“start the founder claims”

A one-line go-ahead. Claude then built the meta-tag verification and the three founder decisions.

“Never show seeded or demo data as real activity.”

One rule from the owner's four-track brief for the final push. It is why demo rows are flagged, badged and kept out of every real count.

“Im suggesting if the app tagline be backers instaed of scouters”

Claude kept “scouts” as the name (on Vibestarter, “backers” means people who fund raises) but took the verb: the tagline became “Scouts back indie apps overnight.”

>_ split

Directed versus generated

The owner directed

  • The idea and the audience: a discovery network for vibecoded apps, run by the community
  • Every go / no-go: each feature was proposed, then approved before it was built, and every push to the live site
  • The bar: comparing against the last Vibeathon and asking for something less generic
  • The four-track brief for the final push, and its honesty rule for demo data
  • Product calls: the “back” in the tagline, a free AI provider (Groq) over paid credits, and seeding the demo with the owner's own apps
  • Accounts and secrets: Supabase, Groq, Vercel and the environment variables, set up by the owner

Claude generated

  • Turning the brief into concrete mechanics (flares, the dawn lock, hit rates), proposed for approval
  • All application code, the database schema and the UI copy
  • Security work: signature checks on Base, SSRF guards on URL fetching, prompt-injection framing for page text
  • Local testing with throwaway wallets and an end-to-end smoke test, and fixes for what broke
  • The cover image, drawn in code from the same skyline as the site
  • Commits, pushes and deploys

No application code was written by hand. The owner edited configuration and data only: environment variables and the demo seed list. Where the owner overruled a suggestion, it is listed above as a product call.

>_ timeline

Commit by commit

  1. 4 NovFirst commit: wallet sign-in on Base, signed flares and tonight's board
  2. 6 NovScouting end to end against Supabase · first live deploy · Next.js security upgrade · dawn lock and Morning Report · flares-left counter and how-it-works strip
  3. 7 NovFounder claims and decisions · scout records with verifiable signatures · the night skyline · demo edition, scout notes, AI analyst and signed-message nonces · README, this page and the pitch · share images
  4. 8 NovIn-app AI moved to Groq's free tier · smoke test extended to check the AI

Full history: github.com/lightokey839-rgb/night-shift

Built by LIGHT, a Web3 developer and builder. Portfolio

Why it exists and where it goes next: read the pitch →