Tooling
Tooling
Not a logo wall. This is the vibe-coding system: how I scope, build, ship, and make brands visible to AI answer engines.
The system
- 01
Scope in plain language
Fixed packages, real timelines. No discovery theater. Systems mapped before code.
- 02
Build with AI, review with craft
Cursor + Claude/OpenRouter for speed. Architecture, tests, and integrations checked by hand.
- 03
Ship production-grade
Next.js on Vercel, Supabase for data, Resend for comms. Monitoring and governance included.
- 04
Make it citable
GEO/AEO: structured data, llms.txt, answer-first content. The site proves the method.
Stack
| Tool | Category | Role in the system |
|---|---|---|
| Next.js | Framework | Primary web framework for client and own products |
| Vercel | Hosting | Default hosting and CI/CD |
| Supabase | Data | Backend for apps that need persistent data |
| Cursor | Editor | Daily driver for vibe-coding workflows |
| Claude / OpenRouter | LLM | Architecture decisions, code generation, review |
| Resend | Comms | Contact forms, notifications |
| Tailwind CSS | Styling | Design tokens and rapid UI |
| MCP | Integrations | Connect AI tools to external systems |