Skip to content

byeadro/awesome-vibe-coding

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

10 Commits
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

🎯 Awesome Vibe Coding

A curated, opinionated list of tools, prompts, patterns, and resources for non-technical founders building real software with AI.

Awesome Stars Contributors PRs Welcome Made Without Instructions


What this is

This is not another "AI coding tools" list.

This is a playbook for non-technical founders shipping real software with AI β€” written by one. Curated by someone who has actually shipped products under these constraints, not someone watching from the outside.

Every entry on this list earns its spot one of two ways:

  1. I've used it personally to ship something that exists in the world.
  2. A non-technical founder I trust has shipped with it and vouches for it.

If a tool is trendy on X but doesn't actually help a solo non-technical builder ship a working product β€” it's not on this list. If a resource is technically impressive but assumes you already know what a useEffect is β€” it's not on this list.

The bar is: would this help someone with no formal CS background ship a real product they could put in front of customers? That's it.

Some links are affiliate links. They cost you nothing extra and help keep this list maintained.


What "vibe coding" means

Vibe coding is shipping software by collaborating with AI as your co-developer β€” not by memorizing syntax, not by going to bootcamp, not by waiting for someone else to build it for you. You bring product instinct, taste, and persistence. The AI brings the syntax, the patterns, and the speed. Together you ship.

Vibe coding is not lazy. It's not "no-code." It's a real skill β€” and the people doing it well are shipping startups, products, and tools that compete with traditional dev teams.

This list is for them.


πŸ“– Table of Contents


⚑ The Vibe Coder's Loop

Most lists give you tools. Almost none tell you the actual workflow that ties them together. Here's the one I've shipped most of my work with β€” it's the same loop whether I'm building a prototype, a production feature, or a skill library.

1. CLAUDE CHAT  β†’  shape the idea, refine the concept, get it sharp
2. CLAUDE CHAT  β†’  generate a clean, structured prompt for what to build
3. COWORK       β†’  scaffold the project, create files, set up GitHub + Vercel
4. COWORK       β†’  generate the next set of build prompts for Claude Code
5. CLAUDE CODE  β†’  do the actual building, multi-file changes, run tests
6. COWORK       β†’  double-check what Code did, catch what got missed
7. β†’ loop ←     β†’  next feature, same rhythm

The unlock isn't any single tool β€” it's that each tool plays a role it's actually good at, and you stop trying to make one tool do everything. Chat is for thinking. Cowork is for orchestration and verification. Code is for building.

You don't need a CS degree to run this loop. You need to know which tool to grab, in what order, for what step.


πŸ› οΈ Editors & Coding Agents

The actual surface where you write (or, more accurately, generate) code. This is the most important section of the list β€” get this wrong and nothing else matters.

  • Claude Code β€” Terminal-based agentic coding tool from Anthropic. Reads your codebase, makes multi-file changes, runs tests, opens PRs. This is my primary. I've shipped CEE, wunanddone, FounderOS, and most of Embra with it. If you're serious about building real software with AI, start here.
  • Claude (Chat) β€” Where I think and plan before I build. Concept refinement, prompt construction, architecture conversations. I never start in Code; I always start in Chat.
  • Cowork β€” Anthropic's desktop tool for non-developers. The orchestration layer that ties Chat and Code together β€” scaffolds projects, sets up GitHub and Vercel through connectors, and double-checks what Code built. This is the missing piece in most "AI coding" workflows.
  • Codex β€” OpenAI's coding agent. I use this for smaller tasks or when I'm trying to conserve Claude usage. Solid for quick fixes, weaker than Claude Code for serious multi-file work.
  • v0 by Vercel β€” Generates UI components and full pages from prompts. Best in class for getting a beautiful frontend fast β€” drop the output straight into Cursor or Claude Code from there.
  • Cursor β€” VS Code fork with deeply integrated AI. I used this before Claude Code. Still excellent if you prefer working in an editor surface vs. a terminal.
  • Bolt.new β€” Browser-based AI builder. Type a prompt, get a working full-stack app, deploy in one click. Good for prototypes; you'll outgrow it fast for anything serious.
  • Lovable β€” Browser-based, opinionated stack. Solid for landing pages and small apps. Same ceiling as Bolt.
  • Replit Agent β€” Cloud-based AI builder + hosting in one. Approachable starting point if you don't want to install anything locally.
  • Windsurf β€” Another AI-native editor with strong agentic capabilities. Worth a look if Cursor isn't clicking for you.

πŸ’‘ Honest take: Once Claude Code and Cowork came out, I stopped using almost everything else. Pick a primary editor, get fluent, and stop tool-hopping. The compounding comes from depth, not breadth.


🎨 UI & Design Tools

You can vibe-code logic all day, but bad UI kills products. These help.

  • v0 by Vercel β€” Worth listing twice. The fastest way to a beautiful frontend, period.
  • shadcn/ui β€” Copy-paste component library that's become the default for serious AI-built apps. Beautiful, accessible, owned by you.
  • Tailwind CSS β€” The styling framework AI tools generate best for. Learn enough to read it.
  • Figma β€” When you need to design before you build. Free tier is enough.
  • tweakcn β€” Theme editor for shadcn/ui. Get a polished look in 2 minutes instead of 2 days.
  • Aceternity UI β€” Animated, modern components. Great for landing pages.
  • Magic UI β€” Free animated UI components. Drop into shadcn projects.
  • Lucide Icons β€” Default icon library for most modern stacks. AI tools know it well.
  • Radix UI β€” Accessible primitives that shadcn is built on top of.

πŸš€ Deployment & Hosting

Where your stuff actually lives on the internet.

  • Vercel β€” The default for Next.js. Push to GitHub, it deploys. I deploy everything here. The free tier carries you a long way.
  • Hostinger KVM VPS β€” When you need a real Linux server (self-hosted Ollama, n8n, Open WebUI). I run a hybrid stack on this β€” local models for high-volume tasks, Claude API for strategic work. Not a typical pick for vibe coders, but if you want to control your costs and own your infra, it earns its spot.
  • Netlify β€” Vercel's biggest competitor. Slightly different feature set, equally solid.
  • Railway β€” Backends, databases, cron jobs, all one-click. Closest thing to "Vercel for backends."
  • Fly.io β€” When you need full control of a server. More technical but powerful.
  • Cloudflare Pages β€” Static sites, edge functions, generous free tier. Fast.

πŸ—„οΈ Backends & Databases

The thing your app talks to to remember stuff.

  • Supabase β€” Postgres + auth + storage + realtime + edge functions. The backend default for vibe coders. I use this for almost every Embra product.
  • Firebase β€” Google's BaaS. I've shipped with this β€” Devlog (Chrome extension) runs on Firebase. Great for mobile-first or realtime apps.
  • SpacetimeDB β€” Realtime database with multiplayer-game-engine roots. Unusual pick, but I built JARVIS (my personal AI OS) on top of this. If you're building anything realtime β€” collaborative tools, games, live dashboards β€” it's worth knowing about.
  • Convex β€” Realtime backend with TypeScript-first DX. Newer, well-loved.
  • Neon β€” Serverless Postgres. Great for projects that scale to zero.
  • Turso β€” Edge SQLite. Fast, cheap, simple.
  • Upstash β€” Serverless Redis & Kafka. Good for caching and queues.

🧱 Self-Hosted AI Infrastructure

Most non-technical founders never explore this. They should.

If you're going to build with AI as your primary tool, eventually you'll want to control your costs, run high-volume tasks locally, and stop bleeding API budget on jobs that don't need a frontier model. This is the stack that makes that possible.

  • Ollama β€” Run open-source LLMs locally with one command. I route high-volume tasks (content scraping, classification, simple completions) here. Saves real money.
  • Open WebUI β€” Self-hosted ChatGPT-like interface. Plug it into Ollama and you have your own private chat tool with no per-message cost.
  • LiteLLM β€” Universal API proxy. Lets you swap between Claude, GPT, Gemini, and local models with one interface. Critical for hybrid routing.
  • n8n (self-hosted) β€” Run automation workflows on your own server. Full control, no per-task fees, integrates with everything.
  • Hostinger KVM VPS β€” Where I host all of the above. Cheap, simple, enough horsepower for a hybrid local/cloud stack.

πŸ’‘ Honest take: You don't need this on day one. But if you're spending $200+/month on AI APIs and most of those calls are repetitive, low-stakes tasks, this stack pays for itself in a month.


⚑ Boilerplates & Starters

Don't start from npx create-next-app if you can avoid it.

  • T3 Stack β€” Next.js + TypeScript + Tailwind + tRPC + Prisma. Opinionated and excellent.
  • Saas-Starter (Next.js) β€” Next.js + Stripe + Auth, by Vercel's Lee Rob.
  • Supabase Starter β€” Vercel's official Next.js + Supabase template.
  • create-llama β€” Scaffold an AI app fast.
  • Nextra β€” Documentation site starter. Great for launching landing pages or docs fast.

🧠 Prompt Patterns & Skills

How you talk to the AI matters as much as the AI itself.

  • Anthropic's Prompt Engineering Guide β€” Read this. All of it.
  • Claude Code Skills β€” Reusable workflow definitions. The single biggest unlock for serious vibe coding. Write a skill once, reuse it across every project. I have skills for content generation, investor outreach, build logs, and a dozen other things β€” they save hours every week.
  • OpenAI Cookbook β€” Practical prompt examples and patterns.
  • Awesome ChatGPT Prompts β€” Massive prompt library. Inspiration source.
  • Made Without Instructions β€” My ongoing essays on the craft of building with AI as a non-technical founder. Bias warning: this is mine.

Patterns I use constantly

  • Bible-first development β€” Define every architectural rule in a bible/ folder before writing code. Each task references the bible section it implements. Codebase implements the bible; the bible doesn't describe the codebase. Used this on CEE β€” 1,531 tests later, no architectural drift.
  • Halt-and-resolve β€” Before writing code, surface every halt (every unclear decision, every assumption). Resolve each halt against a bible-grounded rationale. Then implement. Forces you to think before you generate.
  • Three-tool loop β€” Chat for thinking, Cowork for orchestration, Code for building. Each tool plays its role; you stop trying to force one tool to do everything.

πŸ” Workflow Automation

For when "this should run while I sleep."

  • n8n β€” Self-hostable workflow automation. I run everything here β€” investor outreach (55+ personalized cold emails), content distribution, daily news digests. Self-hosted on my Hostinger VPS for full control. Genuinely the most leveraged tool in my stack after Claude Code.
  • Zapier β€” The OG. Easy, expensive at scale.
  • Make β€” Zapier alternative, more visual, more powerful for complex flows.
  • Pipedream β€” Code-friendly automation. Great if you want to drop in JavaScript when needed.
  • Trigger.dev β€” Background jobs and workflows in your code, not in a separate tool.

πŸ“‹ Knowledge OS & Second Brain

Most non-technical founders are drowning in their own ideas. Fix that here.

  • Notion β€” Where I plan, draft, and run my businesses. I have a Content Writing Dashboard, an Investor Intelligence DB tracking every conversation, a Claw Command Center for daily focus, and dedicated databases for every active project. The Notion stack is half my operating system.
  • Obsidian β€” My second brain β€” a vault called ~/SecondBrain with a 00–08 folder structure. Plain markdown files I own forever, regardless of what app I use to view them. Pairs perfectly with Claude Code (which can read your vault directly).
  • Heptabase β€” Visual whiteboard meets card-based note-taking. Great for thinking through complex problems.
  • Tana β€” Outliner with structured fields. Powerful but steeper curve.
  • Logseq β€” Open-source Obsidian alternative.

πŸ“± Mobile App Builders

Shipping native iOS/Android without becoming an iOS/Android dev.

  • Claude Code + Xcode β€” Yes, you can vibe-code native iOS apps in Swift. I shipped Embra Signal to the App Store this way. Don't let "I don't know Swift" stop you.
  • Expo β€” React Native made human. Most AI tools generate Expo-flavored RN well.
  • FlutterFlow β€” Visual builder for Flutter apps. Lower ceiling but very fast.

πŸ’Έ Payments & Auth

The two things every real product needs.

  • Stripe β€” The default. Excellent docs. AI tools generate Stripe code well.
  • Lemon Squeezy β€” Stripe alternative that handles tax/VAT for you. Worth it for indie hackers.
  • Clerk β€” Auth-as-a-service. The fastest way to a production-grade login system.
  • Auth.js (NextAuth) β€” Open-source auth for Next.js. Free, battle-tested.
  • Supabase Auth β€” If you're already on Supabase, you're already authed.

πŸ“Š Analytics & Monitoring

Knowing if anyone is using your thing and what's broken.

  • PostHog β€” Product analytics + session replay + feature flags. Generous free tier.
  • Plausible β€” Privacy-friendly Google Analytics replacement. Simple.
  • Vercel Analytics β€” Built into Vercel. Just turn it on.
  • Sentry β€” Error tracking. Catch bugs in production before users complain.
  • Logsnag β€” Slack-like notifications for product events. Great for early-stage.

πŸ“ Content & Build-in-Public

Shipping the story of what you built matters as much as the build itself.

  • Substack β€” Where the building-in-public crowd writes.
  • Medium β€” Older audience, still gets traffic.
  • Hashnode β€” Developer-focused blogging. Free custom domain.
  • Beehiiv β€” Newsletter platform. More creator-friendly than Substack on monetization.

πŸŽ“ Learning Resources

For when you need to actually learn the thing, not just generate it.


πŸ“š Books & Long-form Reads

When you want depth, not a 280-character take.


πŸŽ™οΈ Podcasts

For the commute, the gym, the long walk.


πŸ“Ί YouTube Channels


πŸ‘₯ Communities

Where the actual builders hang out.


πŸ’Ό Founder Resources

For the operator side of the equation.


βš–οΈ Legal & Compliance

Boring but the difference between "real company" and "guy who got sued."


🀝 Contributing

This list is alive. It only stays useful if real builders keep adding what's working for them.

To add an entry:

  1. Read CONTRIBUTING.md
  2. Open a PR
  3. Make sure your entry meets the bar: would this help a non-technical founder ship a real product?

We don't accept entries based on hype, sponsorship, or follower counts. We accept entries based on whether the thing actually works for the audience this list is for.


⭐ Star History

Star History Chart


✍️ About the Curator

Maintained by @byeadro β€” non-technical solo founder, vibe coder, and writer behind Made Without Instructions. I'm building Embra (B2B EdTech/LegalTech, NVIDIA Inception, SPARK Accelerator), CEE, and a bunch of other things β€” all with AI as my co-developer.

If this list is useful to you:

  • ⭐ Star the repo
  • πŸ” Share it with another non-technical founder
  • πŸ“¬ Subscribe to MWI
  • 🐦 Follow me on X

License

CC0-1.0 β€” Public domain. Take it, fork it, remix it.

Built without instructions.

About

A curated list of tools, prompts, and patterns for non-technical founders shipping real software with AI.

Topics

Resources

License

Contributing

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors