How Package Was Built
From repo to landing page in one prompt chain.
April 11, 2026
The problem
Vibe coders can build apps in a weekend. They can't communicate what they built. So nobody cares.
The gap isn't technical. It's positioning. Most developers skip the hardest part: explaining why someone should use what they made. The Build Once, Sell Twice course covers this in depth — Package is the tool that automates it.
Package connects to a GitHub repo, reads the codebase, and generates three positioning angles. Pick one. Get a landing page, README, tweets, Product Hunt listing, and a 30-second pitch.
The stack
Next.js 15. Claude API. GitHub API. Tailwind. PostgreSQL. The same stack that powers this entire site.
No fine-tuning. No RAG. No vector databases. Just structured prompts with the right context.
How it works
User connects a GitHub repo. Package reads the codebase and feeds it into a prompt that generates three positioning angles. Each angle is a different way to frame the same product. Pick one. Everything generates from that angle.