>_ how this was built
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
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
01 · Direct
The owner set the goal or reacted to the last build in plain words.
02 · Plan
Claude read the code, proposed the change and the trade-offs, and waited for a go-ahead.
03 · Build
Claude wrote the code, the schema changes and the copy.
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).
05 · Ship
Commits pushed to GitHub on the owner's go-ahead, deployed by Vercel, then checked on the live site.
>_ prompts
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
The owner directed
Claude generated
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
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 →