Awesome Figma - Curated Resources for Figma and Development Workflows

react-figma/awesome-figma is a curated list of Figma resources — plugins, libraries, API tooling and articles about moving between design and code. It is released under CC0 1.0.

We audited it, and the result was the opposite of what we expected. The links are fine. The list is not.

Every link works, and that is not the point

We extracted every GitHub repository link from the README — 70 total links, 42 of them distinct repositories — and checked each one:

git ls-remote --exit-code https://github.com/<owner>/<repo>.git HEAD

42 out of 42 reachable. Zero dead links.

Then we checked the repository’s own history. The most recent commit on the default branch is from 30 May 2024 — over two years before this review.

Those two facts together are the finding, and they are worth sitting with, because they contradict how most people judge a curated list. Link rot is the failure mode everyone looks for and it is not what went wrong here. Software repositories are sticky: once published, they tend to stay published. A list can have a perfect link-check score and still be useless.

The actual failure mode is omission. A list of Figma tooling frozen in May 2024 cannot contain anything released since, and this is a fast-moving corner — plugin APIs, variables, dev mode, code-generation tooling and the whole category of agent-driven UI work have all moved substantially in that window. The list is not wrong about what it contains. It is silent about everything after its last commit, and silence looks identical to completeness.

The staleness marker hiding in the CI file

There is a .github/workflows/node.yml, which at first glance is reassuring — this list does have CI. Reading it is more informative:

strategy:
  matrix:
    node-version: [12.x]
steps:
  - run: npm run speller
  - run: npm run lint

Two things. First, what it checks: a speller and a markdown linter. Not links. So unlike a list that runs an automated link checker, nothing here would have told the maintainer if entries had gone dead — the 42/42 result is luck rather than process.

Second, the pinned Node version. Node 12 reached end of life in April 2022. A workflow still pinned to it is a fossil in its own right, and a neat illustration of the point: the repository’s infrastructure stopped being updated at the same time as its content.

How to read a list like this

The lesson generalises, and it changes the check worth running on any curated index.

Most advice says to look at stars or at dead links. Both are weak signals. The two that actually matter:

The last commit date, which tells you the newest thing the list could possibly contain. Compare it against how fast the subject moves. Two years is nothing for a list of Unix utilities and fatal for a list of AI tooling.

What the CI checks, if any. A link checker means links are maintained. A speller means prose is tidy. Nothing means nothing.

git clone --depth=1 <list-repo> && git log -1 --date=short --format=%ad
cat .github/workflows/*.y*ml

Thirty seconds, and you know what you are holding.

What it is still good for

Not nothing. A frozen list retains real value in one specific way: the entries that have survived unchanged for two years are, by selection, the stable ones.

If you want the Figma API client that has been around long enough to be dependable, or the plugin boilerplate that predates the churn, a 2024 list is arguably a better filter than a current one — it has already excluded everything that did not last. Use it as a conservative shortlist.

What you must not use it for is a survey of what is available. For that, go to Figma’s own plugin directory and developer documentation, which are first-party and current.

For the design-to-code question specifically, the interesting work has moved on considerably. Curated component sources such as 21st.dev and design-standard skills like taste-skill are addressing the handoff from a direction that did not exist when this list was last updated — which is precisely what a 2024 index cannot tell you.

Verdict on the list, and on list-reading

CC0 means anyone can fork it and bring it current without asking, and adding a link-checking workflow would take the same seven lines that keep other lists healthy. Until someone does, treat this as an archive with a known date.

The finding: all 42 GitHub repositories in this list still resolve, and the list has not been updated since 30 May 2024 — so its problem is omission rather than rot. Its CI runs a speller and a linter on Node 12, which is both unhelpful for link health and a fair summary of the repository’s state. When judging a curated list, read the last commit date against the pace of the field, not the dead-link count.