This curated list showcases the rapidly growing ecosystem of open-source tools, applications, and resources that enhance and extend Claude's capabilities across development workflows, user interfaces, and integrations.
By submitting this pull request I confirm I've read and complied with the below requirements 🖖
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
Requirements for your pull request
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. Instead use #2242 for incubation visibility.
Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
You have to review at least 2 other open pull requests.
Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. Just commenting "looks good" or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions. Comments pointing out lint violation are allowed, but does not count as a review.
This pull request has a title in the format Add Name of List. It should not contain the word Awesome.
✅ PR Title: Add Claude
Your entry here should include a short description of the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb. It should not contain the name of the list.
✅- [Claude](https://github.com/alvinunreal/awesome-claude#readme) - Advanced AI assistant known for thoughtful responses and strong capabilities in reasoning, analysis, and coding.
Your entry should be added at the bottom of the appropriate category.
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 August 30, 2024 (46+ days old).
Run awesome-lint on your list and fix the reported issues. Passing with automated CI/CD workflow.
Includes a succinct description of the project/theme at the top of the readme.
✅ "Claude is Anthropic's advanced AI assistant, known for its thoughtful, nuanced responses and strong capabilities in reasoning, analysis, and coding. This list focuses on actively maintained, open-source projects that enhance and extend Claude's capabilities."
It's the result of hard work and the best I could possibly produce. Curated 100+ high-quality projects across 8 major categories with detailed descriptions and active maintenance verification.
The repo name of your list should be in lowercase slug format: awesome-name-of-list.
✅awesome-claude
The heading title of your list should be in title case format: # Awesome Name of List.
✅# Awesome Claude
Non-generated Markdown file in a GitHub repo.
The repo should have awesome-list & awesome as GitHub topics. (Need to add these topics on GitHub)
Not a duplicate. First comprehensive awesome list dedicated to Claude AI ecosystem.
Only has awesome items. Curated selection of actively maintained, high-quality projects with meaningful functionality.
Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs.
Includes a project logo/illustration whenever possible.
✅ High-DPI SVG logo centered at top, linking to Claude.ai
Entries have a description, unless the title is descriptive enough by itself.
Well-Organized Structure: Clear categorization from official resources to community tools
Regular Updates: Maintained list with recent additions and verified project status
Go to the top and read it again.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/sindresorhus/awesome/pull/3643
**Author:** [@alvinunreal](https://github.com/alvinunreal)
**Created:** 9/14/2025
**Status:** ❌ Closed
**Base:** `main` ← **Head:** `main`
---
### 📝 Commits (1)
- [`bf33456`](https://github.com/sindresorhus/awesome/commit/bf3345651968ff9e53ad4eb515b42eb3ffcec1bb) Add awesome-claude
### 📊 Changes
**1 file changed** (+1 additions, -0 deletions)
<details>
<summary>View changed files</summary>
📝 `readme.md` (+1 -0)
</details>
### 📄 Description
<!-- Congrats on creating an Awesome list! 🎉 -->
<!-- Please fill in the below placeholders -->
**https://github.com/alvinunreal/awesome-claude#readme**
**This curated list showcases the rapidly growing ecosystem of open-source tools, applications, and resources that enhance and extend Claude's capabilities across development workflows, user interfaces, and integrations.**
### By submitting this pull request I confirm I've read and complied with the below requirements 🖖
**Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.**
## Requirements for your pull request
- [x] 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. **Instead use [#2242](https://github.com/sindresorhus/awesome/issues/2242) for incubation visibility**.
- [x] **Don't waste my time.** Do a good job, adhere to all the guidelines, and be responsive.
- [x] **You have to review at least 2 other [open pull requests](https://github.com/sindresorhus/awesome/pulls?q=is%3Apr+is%3Aopen).**
Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. **Just commenting "looks good" or simply marking the pull request as approved does not count!** You have to actually point out mistakes or improvement suggestions. Comments pointing out lint violation are allowed, but does **not** count as a review.
**I have reviewed the following PRs:**
- [x] PR #3621 - Contribution guideline best practice
- [x] PR #3551 - URL slug consistency
- [x] You have read and understood the [instructions for creating a list](https://github.com/sindresorhus/awesome/blob/main/create-list.md).
- [x] This pull request has a title in the format `Add Name of List`. It should not contain the word `Awesome`.
- ✅ PR Title: `Add Claude`
- [x] Your entry here should include a short description of the project/theme of the list. **It should not describe the list itself.** The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb. It should not contain the name of the list.
- ✅ `- [Claude](https://github.com/alvinunreal/awesome-claude#readme) - Advanced AI assistant known for thoughtful responses and strong capabilities in reasoning, analysis, and coding.`
- [x] Your entry should be added at the bottom of the appropriate category.
- [x] The title of your entry should be title-cased and the URL to your list should end in `#readme`.
- [x] No blockchain-related lists.
- [x] The suggested Awesome list complies with the below requirements.
## Requirements for your Awesome list
- [x] **Has been around for at least 30 days.**<br>Repository created August 30, 2024 (46+ days old).
- [x] Run [`awesome-lint`](https://github.com/sindresorhus/awesome-lint) on your list and fix the reported issues. Passing with automated CI/CD workflow.
- [x] The default branch should be named [`main`, not `master`](https://www.zdnet.com/article/github-to-replace-master-with-alternative-term-to-avoid-slavery-references/).
- [x] **Includes a succinct description of the project/theme at the top of the readme.**
- ✅ "Claude is Anthropic's advanced AI assistant, known for its thoughtful, nuanced responses and strong capabilities in reasoning, analysis, and coding. This list focuses on actively maintained, open-source projects that enhance and extend Claude's capabilities."
- [x] It's the result of hard work and the best I could possibly produce. **Curated 100+ high-quality projects across 8 major categories with detailed descriptions and active maintenance verification.**
- [x] The repo name of your list should be in lowercase slug format: `awesome-name-of-list`.
- ✅ `awesome-claude`
- [x] The heading title of your list should be in [title case](https://capitalizemytitle.com/) format: `# Awesome Name of List`.
- ✅ `# Awesome Claude`
- [x] Non-generated Markdown file in a GitHub repo.
- [x] The repo should have `awesome-list` & `awesome` as [GitHub topics](https://help.github.com/articles/about-topics). *(Need to add these topics on GitHub)*
- [x] Not a duplicate. First comprehensive awesome list dedicated to Claude AI ecosystem.
- [x] Only has awesome items. Curated selection of actively maintained, high-quality projects with meaningful functionality.
- [x] Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs.
- [x] Includes a project logo/illustration whenever possible.
- ✅ High-DPI SVG logo centered at top, linking to Claude.ai
- [x] Entries have a description, unless the title is descriptive enough by itself.
- [x] Includes the [Awesome badge](https://github.com/sindresorhus/awesome/blob/main/awesome.md#awesome-badge).
- ✅ Badge placed next to main heading, links back to awesome list
- [x] Has a Table of Contents section.
- ✅ Named "Contents", first section, one level of nesting
- [x] Has an appropriate license.
- ✅ CC0 1.0 Universal license in LICENSE file
- [x] Has [contribution guidelines](https://github.com/sindresorhus/awesome/blob/main/awesome.md#include-contribution-guidelines).
- ✅ `contributing.md` file with comprehensive guidelines
- [x] All non-important but necessary content grouped in appropriate sections.
- [x] Has consistent formatting and proper spelling/grammar.
- ✅ Automated awesome-lint validation ensures consistency
- [x] Does not use [hard-wrapping](https://stackoverflow.com/questions/319925/difference-between-hard-wrap-and-soft-wrap).
- [x] Does not include a CI badge in readme (CI exists but badge not displayed).
- [x] Does not include an `Inspired by awesome-foo` link.
### Additional Quality Indicators
- **Comprehensive Coverage**: 8 major categories covering the entire Claude ecosystem
- **Active Community**: Features projects with strong community engagement and regular updates
- **Automated Quality Assurance**: GitHub Actions workflow ensures continuous compliance
- **Well-Organized Structure**: Clear categorization from official resources to community tools
- **Regular Updates**: Maintained list with recent additions and verified project status
**Go to the top and read it again.**
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/sindresorhus/awesome/pull/3643
Author: @alvinunreal
Created: 9/14/2025
Status: ❌ Closed
Base:
main← Head:main📝 Commits (1)
bf33456Add awesome-claude📊 Changes
1 file changed (+1 additions, -0 deletions)
View changed files
📝
readme.md(+1 -0)📄 Description
https://github.com/alvinunreal/awesome-claude#readme
This curated list showcases the rapidly growing ecosystem of open-source tools, applications, and resources that enhance and extend Claude's capabilities across development workflows, user interfaces, and integrations.
By submitting this pull request I confirm I've read and complied with the below requirements 🖖
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
Requirements for your pull request
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. Instead use #2242 for incubation visibility.
Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
You have to review at least 2 other open pull requests.
Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. Just commenting "looks good" or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions. Comments pointing out lint violation are allowed, but does not count as a review.
I have reviewed the following PRs:
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 wordAwesome.Add ClaudeYour entry here should include a short description of the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb. It should not contain the name of the list.
- [Claude](https://github.com/alvinunreal/awesome-claude#readme) - Advanced AI assistant known for thoughtful responses and strong capabilities in reasoning, analysis, and coding.Your entry should be added at the bottom of the appropriate category.
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
Repository created August 30, 2024 (46+ days old).
awesome-linton your list and fix the reported issues. Passing with automated CI/CD workflow.main, notmaster.awesome-name-of-list.awesome-claude# Awesome Name of List.# Awesome Claudeawesome-list&awesomeas GitHub topics. (Need to add these topics on GitHub)contributing.mdfile with comprehensive guidelinesInspired by awesome-foolink.Additional Quality Indicators
Go to the top and read it again.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.