Awesome Vibe Coding

★ 5.1kAwesome Lists

#awesome#vibe-coding#references

Overview

One of the most well-known open-source lists in the vibe coding space (5.1k+ stars), collecting references, tools and discussions about coding with AI. It organizes the ecosystem into a dozen categories — browser tools, IDEs, plugins, CLI tools, task management, documentation and communities — making it the best entry point for a full picture of vibe coding.

Who it's for

Anyone who wants a systematic overview of the vibe coding ecosystem, or needs to pick a tool for a specific stage from prototyping to deployment.

What you'll learn

01What it collects: concepts, tools and media together
The 'About the concept' section opens with background material — Karpathy's original tweet defining vibe coding and the Wikipedia article — before the tool list. Rather than a pure tool ranking, it gathers concepts, tools, documentation, communities and news in one place, so you can look up definitions, pick tools and follow industry debate from a single source.
02A directory organized by usage stage
The table of contents is split by purpose: browser-based builders (Bolt.new, Lovable, v0, Replit), IDEs and editors (Cursor, Windsurf, Zed), mobile apps, plugins and extensions (Cline, Copilot, avante.nvim), local apps (Dyad, bolt.diy) and command-line tools (Claude Code, aider, OpenHands, Codex CLI, Gemini CLI). For fast prototypes check Browser-based Tools; for daily development, look at IDEs / Plugins / Command Line Tools.
03Sections worth a look: task management, docs and news
Beyond tools, 'Task Management for AI Coding' covers tools for orchestrating multiple coding agents like vibe-kanban and Claude Task Master; 'Documentation for AI Coding' covers agent-facing doc standards such as AGENTS.md, awesome-cursorrules, llms.txt and Context7; 'News and Social Media' lists, newest first, industry discussions including postmortems of vibe-coding-caused production outages and debates over whether vibe coding is killing open source.
04Community and contributing
The list ends with community and job-board entries like Vibehackers and Reddit subreddits, plus a CONTRIBUTING guide encouraging readers to add new tools and resources. It is a living document that keeps growing, not a one-time inventory.

Practice tips

Pick one tool from Browser-based Tools (e.g. v0 or Bolt.new) to validate an idea over a weekend and feel the describe-run-iterate vibe workflow firsthand.
Install a Cursor or Claude Code from the IDE and command-line sections into daily development, run it for a week, then return to the list and compare your choices.
Read 2-3 articles under News and Social Media about vibe coding risks (e.g. outage postmortems) to build judgment on the boundaries of AI-generated code.
Contribute a tool you find worth adding through CONTRIBUTING, and use that process to stress-test your understanding of the ecosystem.