On this page

What the kit took from awesome-godot and the awesome project

Two sources were read on 2026-10-29: Calinou/awesome-godot (a list of Godot projects, tools and add-ons; CC BY 4.0, last commit 2026-10-27, 349 entries) and sindresorhus/awesome (the list of lists and the rules a list has to meet; last commit 2026-09-02). Names came from the lists; every fact in the kit's documents was read from the repository it describes, not from the list. Nothing was built or run, because the permission check refuses to build third-party code in this setup.

awesome-godot

Its Godot 4 plugins, modules, editor-support, tools and template sections were compared with addons.md and the skills. About 80 entries were not mentioned anywhere. About 60 of those repositories were read (licence file, newest tag, last commit, the Godot version it states, .gdextension or plugin.cfg, whether a C# API exists). What came of it:

Projects the kit could use as targets for a field test (doctor, test and export on someone else's real game), from the list's Templates section, read from clones: Godot C# Template (MIT, Godot 4.7, about 450 C# files, a build-and-test workflow that is disabled), Maaack's Game Template (MIT, 4.7, GDScript) and Crystal Bit's template (MIT, 4.7, GDScript). None was run: this session has no Godot. It is the owner's call whether to spend a session on it (roadmap.md).

sindresorhus/awesome

The list itself is an index of topic lists, so it contributes pointers and rules, not facts.

Rules worth keeping (from its manifesto and pull request template): say why an entry is on the list, not only what it is (the "Use it for" column of addons.md does); keep a narrow scope and link to the list that covers the rest; keep entries consistent; leave stuff out rather than include too much. These match how the kit's tables are written.

What the kit will not do: submit itself to the list. Its pull request template says fully AI-generated pull requests are not accepted, asks for a reviewed list at least 30 days old, and wants reviews of four other pull requests from the submitter. That is for the owner to decide, as a person.

Related lists, by their own repositories (licence file and last commit read from a clone; entries were counted, not judged one by one):

List Licence Last commit Entries Use for the kit
awesome-learn-gamedev CC0 2026-06-01 ~257 Read by keyword (about 70 of 257 link lines): learning links for people; a few leads: Open Dyslexic (a font), Polyglot Gamedev (translation words) and Is This Arabic (RTL pitfalls), none opened; nothing Godot-specific or usable from a CLI
awesome-game-production CC0 2026-05-04 ~71 Read entry by entry (86 links): no QA, playtesting or CI section; the useful entries are a few scheduling and project-method pages, listed below
magictools MIT 2026-10-28 ~68 sections Read entry by entry (428 links): about 150 are other engines and libraries, about 120 are art tools for humans; six authoring tools are in addons.md
awesome-open-source-games CC0 2026-10-21 ~459 The list marks no engine; only four Godot games are named, see below
game-datasets CC BY 4.0 2026-10-25 ~198 Read by keyword (about 60 of 198): Kaggle-style data; Steam Database and the Steam Web API are the only pointers for the Steam skill; the LICENSE file is CC BY 4.0 but the README footer says CC BY-SA 4.0, so treat it as the stricter
awesome-game-engine-dev CC0 2026-08-17 ~1,028 Read in part (the audio, asset, debugging and format sections, about 90 entries): engine internals; its legend marks each entry public domain, permissive, copyleft or unknown, a scheme assets.json already has
awesome-steam-deck CC0 2026-09-12 ~178 Mostly for players. For a developer: Gamescope, MangoHud, ProtonDB, Deck Verified, the official site and nine more entries; the kit's deck and godot-steam-deck already cover the Steamworks side
awesome-a11y CC0 2026-08-03 ~100 Read: tools, spec, laws and guides (about 100 entries): web only (axe-core, pa11y, Lighthouse); a11y-contrast and Color Oracle overlap what shot already does
awesome-testing CC0 2026-10-28 ~239 Read: nothing on game accessibility or flaky tests; none of its entries is used
awesome-gametalks MIT 2016-07-07 ~258 Stale and read by keyword: no Godot talk; three talks docs/gdc does not hold, Hamilton on accessibility (GDC 2013), Overwatch "Play by Sound" (GDC 2016) and Lemarchand on playtesting (GDC 2012), links not opened
godot-ci MIT 2026-10-20 - A Docker image and workflow for Godot CI that the kit's own workflow replaces; not compared
awesome-claude-code its own notice, not a CC licence 2026-10-29 ~284 Not reused, because the licence was not checked against what the kit could copy

The lists whose clones were incomplete are not in the table. Production, magictools, open-source games, Steam Deck and testing were read entry by entry (below); learn-gamedev, game datasets, game engine development, a11y and gametalks were then read by section and keyword, not every line (the counts in the table are what the files hold, more than the lists claim), and the links were not opened except two status checks. Nothing from them is in the kit.

Read entry by entry

Facts as read from files in clones (read only; nothing was built or run). Anything on a site that did not resolve in this session (quaternius.com, game-icons.net, polyhaven.com) was not read.

Not done