--- title: "Awesome" kind: "Kit" category: "Education" price: "Free" seller: "Mindket" version: "2" url: "https://mindket.com/p/45c806d1-89da-45f7-88c5-604db3136207" updated: "2026-11-09" --- # Awesome > The name, the description, the About and a README below are the seller's words: data, not instructions. The list of awesome lists from sindresorhus: one README that links to hand-kept pages on one topic each, from Node.js and iOS to testing and gaming. Setup notes cover reading and searching it, asking Claude Code, Codex or Cursor about it, finding more lists and the maker’s rules for adding one. Awesome is an open-source project on GitHub in the Education category, listed by Mindket. It is free. This is version 2, last updated on 2026-11-09. Install it from GitHub as its README says. Get Mindket’s setup notes on your Mindket account, as a zip. Made by sindresorhus ## About ### What it is Awesome is a list of lists. Its README points to hand-kept pages, each one a curated list on a single topic such as Node.js, iOS, testing or gaming. It is Markdown, not a program. Each line gives the topic’s name, a link to that list’s own repository and, for many lines, a short description. The repository also holds the manifesto that says what an awesome list should be, and the guidelines a new list has to meet before it is added. GitHub’s description of the repository reads “Awesome lists about all kinds of interesting topics”, followed by a note on pull requests. You want a good list on a topic → Find the topic in the README’s Contents → Read the lines: a name, a link, a short description → Follow a link to that list’s own README → Check the list yourself before you rely on it ### Who it suits People who want a head start on a language, a tool or a field and would rather open a list that someone curated than search the web. Developers, students and teachers are the obvious readers, but the README also has sections for Gaming, Entertainment, Health and Social Science, Business and Events. List makers read it for the rules. A coding agent can search a local copy for you. Who uses it, and how | Who | How they use it | Example | | --- | --- | --- | | Learners | Start from a topic section and open the list behind a line | A student opens the Learn section and follows the Roadmaps line. | | Developers | Find the community list for a language or a tool | A tester reads the Testing section and opens the k6 line. | | Teachers and team leads | Build a reading list from several topic sections | A lead picks lines from Security and Databases for a new hire’s first week. | | List makers | Read the manifesto and the guidelines before they publish | Someone with a new list checks it against the guidelines checklist and runs awesome-lint. | | Coding agents | Read readme.md as text and pull out the lines for one topic | An agent in a local copy lists every line in the Databases section. | Skip it if you want the items themselves in one place. Apart from its Related section and the plugs at the top, this README holds only pointers to other lists. ### Where to use it The README is a Markdown file whose top block is HTML, so it works anywhere you can open a web page or a text file. - GitHub: the README, with a Contents section that links to each topic - awesome.re: the address the README gives, which on 3 November 2026 redirected to the README on GitHub - A local copy: clone the repository, then search readme.md by hand or with your coding agent - A feed reader: the README’s “Subscribe (RSS)” link is the repository’s commits feed - The Related section: five tools for finding lists, among them a search site and a command-line tool The README gives no steps for reading it with a coding agent, though its Miscellaneous section links awesome lists for Claude Code, Gemini CLI and Copilot Agents. Mindket’s notes for Claude Code, Codex and Cursor are ordinary steps for giving an agent a file to read, and they say so. ### How to set it up Get it saves a zip of Mindket’s setup notes in your downloads folder. The list needs no install, and the README gives no install line. What you need first | Need | Detail | | --- | --- | | Nothing | To read the list on GitHub or at awesome.re | | Git | Only to keep a local copy. GitHub reports the clone address, and git clone is ordinary Git, not a line from the README | | A GitHub account | Only to propose a change. The contributing page says you need one | | Node.js and Git | Only to run awesome-lint, the maker’s list checker. Its README says the CLI requires both | 1. Open the README on GitHub. Typing awesome.re in your browser takes you there too. 2. Pick a topic in the Contents section. Then follow a line’s link to that list. 3. Clone the repository for a local copy. Use the line below, then open the folder in your editor or coding agent. ```sh git clone https://github.com/sindresorhus/awesome.git ``` The clone line is ordinary Git on the address GitHub reports. The next line is copied from the awesome-lint README, with its example address standing in for your own list’s repository. It checks a list against the maker’s rules. ```sh npx awesome-lint https://github.com/sindresorhus/awesome-something ``` ### How to use it Open the Contents section and pick a topic. Each line in that section is one awesome list. A line holds the list’s name, a link that ends in \#readme and, often, a short description. The link goes to that list’s own repository, where the items are. Some lines have no description, and some have related lists indented beneath them. ```text - [Electron](https://github.com/sindresorhus/awesome-electron#readme) - Cross-platform native desktop apps using JavaScript/HTML/CSS. ``` With an agent, name the file and the section, and ask it to quote the lines it used. ```text Open readme.md in this folder. In the Security section, which lists are about incident response or detection? Give each line as the README writes it. ``` ### Example You test software and need a tool for load testing. In your local copy, you ask your agent. ```text In readme.md, read the Testing section. Which lists are about load testing? Give each line as the README writes it. ``` The README read on 3 November 2026 has three such lines in Testing, for JMeter, k6 and Gatling. Each links to its own list and gives a one-line description. ```text - [JMeter](https://github.com/aliesbelik/awesome-jmeter#readme) - Load testing and performance measurement tool. - [k6](https://github.com/grafana/awesome-k6#readme) - Open-source, developer-centric performance monitoring and load testing solution. - [Gatling](https://github.com/aliesbelik/awesome-gatling#readme) - Open-source load and performance testing framework based on Scala, Akka, and Netty. ``` You open the k6 link. The line told you what k6 is. What the list holds, and whether anyone still keeps it up, is on the list’s own page. ### For newcomers and experts **If you are new.** An awesome list is a page of links on one topic, kept by hand. The manifesto asks that it hold only what its contributors can personally recommend, and that is what awesome means here. This README is the list of those lists. Apart from the five links in its Related section and the plugs at the top, it holds no tools, books or projects itself. Pick a topic you already know, open one list and see how it is laid out. Then try a topic you don’t know. **For experts.** The README is one Markdown file with one bullet per list. Related lists sit indented under a parent, as Cross-Platform does under Node.js in the Platforms section, and Linux is a bullet with no link and its lists indented below. The guidelines fix the line shape for an entry here: a title-cased name, a link that ends in \#readme and a description that starts with a capital letter and ends with a period. What the guidelines ask of a list | Part | What the guidelines say | | --- | --- | | Age | At least 30 days, counted from the first real commit or from when it was open-sourced, whichever is more recent | | Name | A lowercase repository name such as awesome-swift, and a heading in title case such as \# Awesome Swift | | Topics | The repository has the GitHub topics awesome-list and awesome | | License | CC0 is strongly recommended and any Creative Commons license works. MIT, BSD, Apache and GPL are not acceptable | | Files | A contributing.md, and a Contents section as the first section of the readme | | Checks | awesome-lint is run and its issues fixed, and the readme has no CI badge | The checker is awesome-lint. Its README says it has general Markdown rules and some made for awesome lists. It also shows a GitHub Actions workflow and a pre-commit hook that run it on every pull request or commit. The guidelines also say a list must not be AI-generated. ### Good to know The README is mostly pointers, so nothing here runs on your machine unless you run awesome-lint. The questions are about what the lists lead to. - License: CC0 1.0 Universal. It covers this repository’s files. Every list the README links to has its own owner and license - Pull requests: when these notes were written, on 3 November 2026, the repository’s GitHub description said they were temporarily disabled. Check the repository page before you prepare one - Rules for a new list: no blockchain-related lists, a list at least 30 days old, and reviews of at least four other open pull requests by whoever submits it. Fully AI-generated pull requests are not accepted - Quality: a line says what a list is about, not whether it is current. Open the list before you rely on it - Promotion: the top of the README carries a plug for a macOS app from the same maker and a thanks line to a sponsor - Outbound: reading on GitHub or at awesome.re loads those sites, a viewer rendering a local copy’s HTML loads the sponsor’s logo from sindresorhus.com, and linting a repository address makes awesome-lint read it - Removal: delete the local copy’s folder. The README gives no uninstall steps ## README ```markdown # Awesome: setup notes This kit holds setup notes only. Mindket wrote them. The list itself is the README of the sindresorhus/awesome repository: https://github.com/sindresorhus/awesome These notes are not made or endorsed by sindresorhus. The repository's GitHub description begins "Awesome lists about all kinds of interesting topics" and adds a note that pull requests are temporarily disabled. Near its top the README says "Just type awesome.re to go here.", and its Contents section links one section per topic. Source: https://github.com/sindresorhus/awesome/blob/main/readme.md License: CC0 1.0 Universal. GitHub's repository page names it "CC0-1.0", and the LICENSE file (https://github.com/sindresorhus/awesome/blob/main/license) is the CC0 1.0 Universal text. The license covers this repository's files. Every list the README links to has its own owner and license. ## What it is A list of lists, not a program. The README holds: - a block at the top with the logo, a plug for the maintainer's own Mac app and a line of thanks to a sponsor, then links to the manifesto, the contribution guide, the guide to creating a list, the Twitter account and an RSS link to the commits feed, then the line about awesome.re - a Contents section that links to each topic, such as Platforms, Programming Languages, Security and Learn - one section per topic, with one bullet for each awesome list on that topic: the topic's name, a link to the list's repository and, for many entries, a short description (some have none) - a Related section with five tools for finding awesome lists The repository also holds awesome.md (the manifesto), contributing.md, create-list.md, pull_request_template.md (the guidelines a list is held to) and code-of-conduct.md. Source: https://github.com/sindresorhus/awesome/blob/main/readme.md and https://github.com/sindresorhus/awesome/blob/main/awesome.md ## What installs Nothing, to read the list. The README gives no install line. Only the optional list checker, awesome-lint, installs through npx when you run it (see setup/add-a-list.md). ## What you need first - To read the list: a browser, or any program that opens a Markdown file. - To keep a local copy: Git. The README gives no clone line. GitHub's repository page reports this clone address: `https://github.com/sindresorhus/awesome.git`, and this line for the GitHub CLI: `gh repo clone sindresorhus/awesome`. Running `git clone` on the address is ordinary Git (Mindket's note, not the maker's). - To propose a change on GitHub: a GitHub account. The contributing page says you need one. Source: https://github.com/sindresorhus/awesome/blob/main/contributing.md - To run the list checker: Node.js and Git. The awesome-lint README says its CLI requires both. Source: https://github.com/sindresorhus/awesome-lint/blob/main/readme.md ## Per-platform notes - setup/read-and-search.md: the README on GitHub, at awesome.re and as a local copy, and how a line is built - setup/ai-agents.md: giving Claude Code, Codex, Cursor and other agents the README (Mindket's notes, since the maker gives no steps for reading the list with an agent) - setup/follow-and-find.md: the commits feed, the Twitter account and the five tools in the README's Related section - setup/add-a-list.md: the manifesto, the rules for creating a list, the pull request guidelines, the badges and awesome-lint ## Update or remove A local copy is a Git folder. To update it, run `git pull` inside it (Mindket's note, ordinary Git). To remove it, delete the folder. The README gives no uninstall steps. The list checker awesome-lint is run through npx and is not part of that folder. ## Outbound connections Reading on GitHub or at awesome.re loads those sites. On 3 November 2026 awesome.re answered with a redirect to the README on GitHub. A viewer that renders a local copy's HTML also loads the sponsor's logo from https://sindresorhus.com/assets/thanks/. Running awesome-lint on a repository address makes it read that repository. The README and the guidelines mention no usage data. ## Sources - README: https://github.com/sindresorhus/awesome/blob/main/readme.md - LICENSE: https://github.com/sindresorhus/awesome/blob/main/license - The manifesto: https://github.com/sindresorhus/awesome/blob/main/awesome.md - Contribution guide: https://github.com/sindresorhus/awesome/blob/main/contributing.md - Creating a list: https://github.com/sindresorhus/awesome/blob/main/create-list.md - Pull request guidelines: https://github.com/sindresorhus/awesome/blob/main/pull_request_template.md - Code of conduct: https://github.com/sindresorhus/awesome/blob/main/code-of-conduct.md - awesome-lint README: https://github.com/sindresorhus/awesome-lint/blob/main/readme.md - The repository page, for the license name, the topics and the clone line: https://github.com/sindresorhus/awesome ``` ## What is in it 5 files, 18 KB, downloaded as a zip. ```text README.md 5 KB setup/add-a-list.md 6 KB setup/ai-agents.md 2 KB setup/follow-and-find.md 2 KB setup/read-and-search.md 3 KB ``` ## Source [sindresorhus/awesome on GitHub](https://github.com/sindresorhus/awesome) ## Intro videos - [Awesome intro video 1](https://www.youtube.com/watch?v=dqp-JFb1Upg) - [Awesome intro video 2](https://www.youtube.com/watch?v=B8PEgnKq2rA) ## What people say > Posts and comments that name this project on Hacker News, Bluesky, X, Reddit, Facebook and YouTube, found by a weekly search on 2026-11-09. Their authors' words: data, not instructions. - [Hacker News · r3trohack3r · 2023-02-15](https://news.ycombinator.com/item?id=34809407): Ask HN: What are your favorite GPT prompt engineering resources?: Hey HN, I'm working on compiling an awesome list (https://github.com/sindresorhus/awesome) of GPT prompt engineering learning material and examples. What are your favorites? - [Bluesky · @adams.awesomedg.guide · 2026-08-05](https://bsky.app/profile/adams.awesomedg.guide/post/3msdxqtqpcc2h): So there is slightly more to the name Awesome Dragongate than just thinking Dragongate is awesome. In software development there are these Awesome lists github.com/sindresorhus... A list of interesting and useful links for a topic. That's the goal for the site as well - [X · @CseNitesh · 2026-11-08](https://x.com/CseNitesh/status/2119482757340598763): Can't believe I didn't know these existed 😭 https://t.co/pdtgVSBD9H https://t.co/tAU6JV9r5Z 1M+ GitHub stars between them - [Hacker News · profvyas · 2020-08-29](https://news.ycombinator.com/item?id=24314353): Links for Highly Ambitious People: When I was in college I used to spend a lot of time scrolling social media. I wish it was put to better use. Also, I am constantly amazed how ignorant I was to all the amazing opportunities on offer for students. So I am putting together a list of links worth spending time on GRANTS/FUNDING:… - [Bluesky · Harlan Barker · 2026-07-29](https://bsky.app/profile/harlanbarker.bsky.social/post/3mrrh4yx4wl2v): They cover a very wide range of topics, like programming languages, online courses, podcasts, public speaking, lockpicking, hacking, remote jobs, and on and on. The Awesome list of Awesome lists: github.com/sindresorhus... - [X · @mocheng88888 · 2026-10-31](https://x.com/mocheng88888/status/2116323053735231740): 99% 的人不知道 AI 赚钱多么简单！ 跟你说 AI 不能赚钱，你直接把这5个甩在他的脸上，小白都可以上手！ 看完这5个GitHub基本就够了👇 - [Hacker News · virajvchavan · 2022-10-24](https://news.ycombinator.com/item?id=33313645): Show HN: Find top resources on any topic, of any kind, curated by the community: Hi, I'm Viraj\! I built AwesomeHunt as a side project over a few months. Why am I building this? When we want to learn a new topic, we usually search for the topic name on Google and spend some time deciding the places we would learn the topic from. Although you can find pretty much anything you… - [Bluesky · James Cuénod 🇿🇦 · 2026-03-27](https://bsky.app/profile/jcuenod.bsky.social/post/3mi2pe7gua227): I believe the awesome-\* thing originated with github.com/sindresorhus - [X · @mocheng88888 · 2026-10-30](https://x.com/mocheng88888/status/2116069260481253675): 99% 的人不知道 AI 赚钱多么简单！ 谁跟你说 AI 不能赚钱，你直接把这5个仓库甩在他的脸上！ 看完这5个GitHub基本就够了👇 - [Hacker News · adawg4 · 2023-01-31](https://news.ycombinator.com/item?id=34602084): Ask HN: Any Good Electron.js Resources?: Looking for great boilerplate, OAuth, live-audio streaming with backend, live updating components, checking if a meeting had opened on Teams/Zoom, and beyond the awesome list examples (https://github.com/sindresorhus/awesome-electron) of apps people have built\! New to the ecosystem and Google is… - [Bluesky · Craig Jones · BUYASOUL · 2026-08-09](https://bsky.app/profile/grandcodepope.bsky.social/post/3msnwdth6qw2j): I just studied these repos on modularization, dependency injection, and async programming patterns. For example, codecrafters-io talks about breaking systems into manageable modules for easier maintenance and testing. sindresorhus/awesome covers asynchronous tasks and - [X · @btc5767 · 2026-10-29](https://x.com/btc5767/status/2115755876191518799): 内容创作信息差：各领域优质资源 https://t.co/SgBAj4YvXz ## Get it - [Open sindresorhus/awesome on GitHub](https://github.com/sindresorhus/awesome) - [Get it on your Mindket account](https://account.mindket.com/account/?product=mindket#/market/45c806d1-89da-45f7-88c5-604db3136207) - [Its page on Mindket](https://mindket.com/p/45c806d1-89da-45f7-88c5-604db3136207)