Contributing to Awesome Vibe Coding

July 19, 2026 · View on GitHub

Thanks for taking the time to contribute! This list only stays useful if it stays curated, so please read through these guidelines before opening a pull request.

Before you submit

  • Search first. Check the README and open pull requests/issues to make sure the tool, article, or resource isn't already listed.
  • Stay on topic. Entries should be directly relevant to AI-assisted / "vibe" coding — tools, editors, agents, CLIs, or writing that helps people build software by prompting, iterating, and collaborating with AI. General AI tools with no coding angle don't belong here.
  • Only submit things you'd actually recommend. The tool or resource should be functional, reasonably maintained, and not vaporware. Broken links, abandoned repos, or "coming soon" pages will be declined.
  • One resource per line, one topic per PR where possible. Small, focused PRs are easier to review than one PR that adds ten unrelated things.

How to add an entry

  1. Fork the repo and create a new branch.

  2. Add your entry to the most relevant section in readme.md, keeping entries alphabetically ordered within that section.

  3. Match the existing format:

    - [Tool Name](https://example.com) — Short, factual description of what it does.
    • Use an em dash (—) to separate the name from the description.
    • Keep descriptions to a single, concise sentence. Describe what the tool does, not why it's amazing — no marketing language, superlatives, or emoji.
    • Link directly to the tool's official site or repo, not to an affiliate/referral link.

  4. If your entry doesn't fit any existing section and you believe it warrants a new one, propose it in your PR description and update the Table of Contents accordingly. New sections should only be added if there are multiple entries to justify them.

  5. Run through the awesome-lint checks if you can — it catches most formatting issues automatically.

Adding your own project

You're welcome to submit a tool you built or maintain. Please:

  • Disclose in the PR description that it's your own project.
  • Make sure it meets the same bar as any other entry (functional, documented, actually useful for vibe coding).
  • Avoid adding multiple projects from the same author/org in a single PR — submit your strongest one first.

Note that this list also has a separate sponsorship option for teams who want dedicated placement rather than a standard entry — pull requests are for organic, editorially-relevant additions.

Removing or updating entries

If you notice a dead link, an abandoned project, or a description that's gone stale, please open a PR (preferred) or an issue. Corrections and removals are just as welcome as new additions.

Pull request review

  • Maintainers review PRs periodically, not necessarily instantly — please be patient.
  • We may edit your description for tone, length, or consistency before merging.
  • PRs that don't follow the format above may be asked for changes rather than merged as-is.

Code of conduct

Be respectful in issues and PRs. Disagreements about whether something fits are fine; personal attacks aren't.

Thanks again for helping keep this list useful for the vibe coding community!