Show Notes
Parker shares a fast, repeatable approach to planning and shipping a new Vibe with AI project from scratch, plus quick takes on current AI tooling and docs strategies you can apply today.
Planning a new build from scratch
- Start with jobs to be done (JTBD): what should users accomplish on the site? For this build, key JTBDs are:
- Copy and reuse prompts easily
- Learn about Vibe with AI
- Join the Vibe with AI community
- Breadboarding the UI: lay out routes and flows first
- Pages to map: Home, Copy Prompts, Learn About Vibe with AI, Join Community (plus an optional account page)
- Decide on external vs internal routes early (external link to the community vs a new page in the site)
- Sign-in and prompts flow
- Use anonymous sign-on as a frictionless entry, with a lightweight prompt save experience
- Prompt copy triggers a modal/dialog and saves prompts for later
- Reuse and remixpatterns
- Leverage prior work (Cursor directory projects, Kitchen Pal) to save time
- Look for common data models (users, prompts) and copy-paste-ready UI patterns
- Roadmap to live quickly
- Plan to host on ivibewai.com and announce via the main channel
- Build quickly, then iterate based on feedback
Tools, tips, and learning resources mentioned
- NIP (nip.js): declutter dead code and surface the useful parts of your repo
- Doc gro / doc rocker: turn any URL into a concise, one-page context for quick reference
- Quilipy: attempt to keep knowledge bases up to date; index docs frequently to avoid outdated LM data
- Up-to-date docs idea: combine MCP-style connectors with an enterprise-friendly A2A protocol to keep data fresh
- V0 (Vzero): fast UI prototyping tool built on Next.js and Shad CN; helps you debug Next.js issues with a primitive-based approach
- Shad CN + Next.js ecosystem: anticipate changes and rely on well-understood primitives
- Convex vs. Supabase
- Supabase (PostgreSQL-based) is more feature-rich and familiar; Convex is lighter and more “training wheels”-like
- Preference: favor feature-rich, well-established primitives when you’re building something production-like
- LM-oriented docs tricks
- LM’s text (llmtxt): turn any website into LM-friendly text for better docs and onboarding
- Code GBT knowledge graph approach: uses a graph of code relationships to generate robust docs
- Real-world examples and anchors
- Taskmaster: founder is in the community; great for onboarding and Q&A
- Kitchen Pal: a past project you can mine for patterns (auth flows, prompts, data models)
AI tooling news highlights
- Agent-to-agent (A2A) protocol from Google: aims to standardize how agents talk to each other across vendors and clouds; complements MCP rather than replacing it
- Enables real-time collaboration, memory-enabled and multimodal agent workflows
- Enterprise impact: easier interoperation between Salesforce, Atlassian, SAP, and other big platforms
- The enterprise shift
- Emphasizes agentic workflows (teams of agents with specialized tasks) over single, monolithic agents
- Start small with agentic tasks, scale to cross-company collaboration as confidence grows
- Knowledge/documentation tooling trends
- Up-to-date docs is a recurring pain point; solutions include targeted doc gro workflows and LM-friendly docs pipelines
- Several repositories and tooling (LMX-style resources, llmtxt, etc.) show a pattern: convert docs and web content into LM-friendly, refreshable formats
- Practical take: rely on proven primitives and open-source patterns
- Build on known stacks (Postgres-based backends, Next.js frontends)
- Reuse and remix existing projects to move faster
Strategy for the Vibe with AI site (planning and execution)
- Define the site’s core jobs to be done and translate them into routes
- Breadboard the user flow first, then wire up UI elements
- Homepage → Copy Prompts → Learn about Vibe with AI → Join Community
- Consider an account page later for saved prompts
- UX decisions to simplify user onboarding
- Lightweight anonymous sign-on with a frictionless path to a saved prompts repository
- Clear external link versus internal route distinction
- Build on existing assets
- Start from Cursor directory project and Kitchen Pal for patterns (auth, prompts, data models)
- Use these as a blueprint, then remix to match the Vibe with AI brand
- Next steps Parker plans
- Implement the breadboard on ivibewai.com
- Create content and routing in the main channel video
- If you want Kitchen Pal links, drop “kitchen pal” in the comments and Parker will share assets
- Community and cadence
- Leverage the daily channel for quick iterations and feedback
- Keep the site tightly aligned with the “learn, copy, join” JTBDs
Actionable takeaways
- Start every project with a jobs-to-be-done list and a breadboard of routes
- Reuse successful patterns from your own repo history to save time
- When docs are outdated, use things like Quilipy and llmtxt to keep knowledge fresh
- Explore agent-to-agent protocols for enterprise-scale workflows to future-proof integrations
- Build with an MVP in mind (three core pages) and add features (account page, saved prompts) only after validating the core flows
- If you’re prototyping, try V0 for rapid UI iteration and Next.js-friendly tooling
Links
- Task Master (founder in the Discord) and related community resources
- V0 (UI prototyping on Next.js + shadcn/ui)
- shadcn/ui
- Next.js
- Supabase (PostgreSQL-based backend)
- Convex
- Google A2A protocol (Agent-to-Agent)
- MCP (Model Context Protocol)
- llms.txt (LM-friendly website text generator)