Add Vibe Coding

[johnxie]

https://github.com/taskade/awesome-vibe-coding#readme

Building software through natural language prompts, using AI to generate, test, and deploy code.

Why it should be included: Vibe coding is a paradigm shift coined by Andrej Karpathy — it's the defining development workflow of 2026, recognized by MIT Technology Review as a Breakthrough Technology. This list is the most comprehensive curated resource (285+ tools, 1,300+ lines, tables with descriptions) covering AI app builders, code editors, agents, MCP tools, automation platforms, and learning resources. There's no comparable entry in the registry yet.

AI usage disclosure: Content was curated by humans. AI tools were used for research assistance (finding tools, verifying URLs), but all editorial decisions, descriptions, and structure are human-authored.

PRs I reviewed:

• Add awesome-agent-services #4002 — flagged license NOASSERTION, description describes list not theme, age borderline, emoji anchors
• Add Microsoft Agent Framework #4003 — flagged URL missing #readme, Contributing/Footnotes in TOC, badge variant
• Add Cesium #4077 — flagged wrong Awesome badge URL, extra social badges, nested TOC, description describes list not theme
• Add EU AI Act #4095 — flagged extra dynamic badges, author byline in description position, license NOASSERTION

unicorn

By submitting this pull request I confirm I've read and complied with the below requirements 🖖

Requirements for your pull request

• Fully AI-generated pull requests are not accepted.
• Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it.
• Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
• You have to review at least 4 other open pull requests. Reviewed PRs Add awesome-agent-services #4002, Add Microsoft Agent Framework #4003, Add Cesium #4077, Add EU AI Act #4095 with specific compliance feedback on each.
• You have read and understood the instructions for creating a list.
• This pull request has a title in the format Add Name of List. It should not contain the word Awesome.
• Your entry here should include a short description of the project/theme of the list. It should not describe the list itself. The description "Building software through natural language prompts, using AI to generate, test, and deploy code." describes the vibe coding concept/theme.
• Your entry should be added at the bottom of the appropriate category. Added at bottom of Platforms section.
• The title of your entry should be title-cased and the URL to your list should end in #readme.
• No blockchain-related lists.
• The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

• Has been around for at least 30 days. Repository created 2026-01-19 — 83 days ago.
• Is not AI-generated.
• Run awesome-lint on your list. CI workflow at .github/workflows/lint.yml runs npx awesome-lint on every push/PR.
• The default branch is named main.
• Includes a succinct description of the project/theme at the top of the readme. > Building software through natural language prompts — describe what you want, and AI generates, tests, and ships the code.
• It's the result of hard work and the best I could possibly produce.
• The repo name is in lowercase slug format: awesome-vibe-coding.
• The heading title is in title case: # Awesome Vibe Coding.
• Non-generated Markdown file in a GitHub repo.
• The repo has awesome-list & awesome as GitHub topics (plus 15 more relevant topics).
• Not a duplicate. No vibe coding list exists in the registry.
• Only has awesome items.
• Does not contain unmaintained/archived/deprecated items.
• Includes the Awesome badge linking to https://awesome.re.
• Has a Table of Contents section named Contents as the first section with one level of nesting.
• Has an appropriate license. CC-BY-4.0 in LICENSE file. No License section in readme.
• Has contribution guidelines in CONTRIBUTING.md.
• Has consistent formatting and proper spelling/grammar.
• Does not use hard-wrapping.
• Does not include a CI badge in the readme.
• Does not include an "Inspired by awesome-foo" link.

[sindresorhus]

Thanks for making an Awesome list! 🙌

It looks like you didn't read the guidelines closely enough. I noticed multiple things that are not followed. Try going through the list point for point to ensure you follow it. I spent a lot of time creating the guidelines so I wouldn't have to comment on common mistakes, and rather spend my time improving Awesome.

[JinyangWang27]

Nice list! The resources look genuinely useful for vibe coding workflows.

A few observations:

• Good coverage of tools across different aspects (IDEs, AI assistants, templates)
• Descriptions are concise and helpful
• Consider adding a brief 'Getting Started' section for newcomers

Overall solid contribution. Thanks for putting this together!

[JinyangWang27]

Excellent submission! The vibe coding list is comprehensive and timely.

Strengths:

• 285+ tools with detailed tables — genuinely useful curation
• Clear scope: natural language → AI-generated code is well-defined
• Good job on the compliance checklist (I see you reviewed 4 other PRs thoroughly)
• CC-BY-4.0 license and awesome-lint CI in place

One minor suggestion: Consider adding a 'Getting Started' or 'Workflow Examples' section showing how vibe coding works in practice — would help newcomers understand the paradigm shift beyond just the tool list.

The AI disclosure is appreciated and handled well. LGTM! 👍

[weilun88313]

Review of awesome-vibe-coding:

1. License detection shows NOASSERTION on GitHub. The LICENSE file contains CC-BY-4.0 text, but GitHub's API returns NOASSERTION for the license spdx_id, meaning the file likely doesn't follow the exact template GitHub uses for auto-detection. Consider re-adding the license using GitHub's template picker so GitHub properly detects it.

2. 9 awesome-lint disable directives at the top of the README. Disabling awesome-toc, awesome-list-item, awesome-spell-check, awesome-github, no-heading-punctuation, etc. suggests the list does not actually pass awesome-lint cleanly. The submission checklist says "Run awesome-lint on your list and fix the reported issues" — suppressing 9 rules rather than fixing the underlying violations seems contrary to that requirement.

3. Heavy Taskade self-promotion throughout the README. The "Workspace DNA: The Living Systems Architecture" section, Taskade Genesis Loop diagrams, multiple Taskade blog links, and the "Try Vibe Coding Now" CTA collectively read more like a marketing page than a community-curated awesome list. Consider reducing the Taskade-specific content to be proportional to other tools.

4. The "Distribution & Promotion" section near the bottom is unusual for an awesome list. It includes instructions for promoting the list on Hacker News and Reddit with "optimal posting times." This is not content that belongs in a curated resource list — consider moving it to an internal doc or wiki.

[brunobuddy]

Hey @johnxie this list is clearly not following the guidelines of an awesome list. Please check the contributing and run the linter

[monapdx]

Really comprehensive and varied awesome list here. Love seeing parts of my vibe coding workflow in different sections here.

Consider adding Streamlit (Python) to an appropriate category. Not sure if it would belong in Open Source Tools or Frameworks, or something similar.

I've built lots of great data exploration apps with AI using Streamlit.

[blenderandroid3fanmade]

fuck you