So a small side project just quietly turned into 96 tiny tools. I only found out because someone dropped the whole list in r/PromptEngineering like it was no big deal. Ninety-six is not a typo. That is the full count, from a Sudoku solver to a Merkle tree folder, sitting in one place for free.
The original poster, u/greentide008, started out making free apps to give away on their site. They weren’t trying to build a platform. But somewhere between gift number twelve and gift number sixty, the shape of a platform just fell out of the work. Now it has a name: the Gifts platform.
What’s new
The latest update isn’t more tools stacked on more tools. It’s the connective tissue between them. All 96 Gifts share three traits by design. They’re dependency-free: no install step, small enough to read start to finish. They’re atomic: one job each, no framework wrapped around them. And they’re lock-in-free: MIT licensed, so you copy the file and owe nothing back. None of them import each other either. Every one is built to stand alone, on purpose.
That independence is what makes the new stuff worth a look. Each tool is exact about what it takes in and what it spits out. That means you can wire two of them together without a coordinating framework holding hands in the middle. If you’re used to reaching for an npm package for a job like this, this takes the opposite approach. It’s one file, with no chain of transitive dependencies to trust. Some of the 96 read data in, like csv-source, json-source, and dir-walk. Some fold or filter it, like running-stats, dedup-filter, and topk-fold. Some just draw the result, like svg-sink and heatmap-sink. Line them up in that order and you have a small pipeline built entirely out of Gifts. The creator built three new pages around that idea. There’s a Dev Guide for using a Gift inside a real workflow. There’s a Recipes page showing Gifts chained into bigger tools. And there’s a “Building Differently” page laying out the reasoning behind it all.
The twist
Here’s the part that made me sit up. The platform now ships a compiler and something called a Schematic system. A Schematic describes how Gifts wire together into a program, and the compiler is supposed to build that program from the spec. Instead of hand-wiring csv-source into schema-filter into a sink every time, you’d write the wiring down once. The compiler would assemble it for you. Cool, expected, on brand.
Then the disclosure: it’s been verified but not yet run in practice. The creator says so right on the site instead of burying it in the fine print. Most tool launches oversell the shiny new feature and quietly skip the caveats. This one flags its own newest piece as early and unproven, and somehow that makes the other 96 tools feel more trustworthy, not less.
Try it yourself
If you want to actually use this instead of just admiring it from the thread, here’s the fast path.
- 🔧 Pick one small, boring problem you hit weekly. Something like “I keep hand-checking CSV columns” or “I keep losing track of what’s actually still TODO in this repo.”
- 📋 Scan the list of 96 for a Gift that matches. Things like csv-source, Census, or schema-filter are built for exactly this kind of chore.
- 📥 Copy the single file into your project. No npm install, no lockfile, no dependency tree to audit before you trust it.
- 🔗 Check the Recipes page for a worked example first. If two Gifts already got chained for a similar job, steal that wiring instead of guessing at your own. Read the whole file once before you run it against real data. That is the entire point of dependency-free: you actually can read it end to end in a few minutes.
Pro tip
Start with the JSONL pipeline tools if you’re doing any AI dev work. One commenter on the thread, u/Practical-Mess-4584, said they’d already been running pluck, schema-filter, and uniq-filter together. The composability held up in real use, not just on paper. When strangers on Reddit start chaining your tools together unprompted, you’re onto something!
Second tip: don’t try to read all 96 pages in one sitting. Bookmark the Dev Guide first. Pick the two or three Gifts that solve a problem you actually have this week, and ignore the rest until you need them. That’s the whole point of atomic tools. You’re never buying the set, just the piece you need right now. And because everything is MIT, you don’t owe anyone a credit line before you ship it.
Go check the thread
This is one of those finds where the value sits in the list, not the pitch. Go skim the full rundown of all 96 Gifts. Grab whichever ones solve a problem sitting on your desk today. Then keep an eye on that compiler update once it’s actually been run for real. 🚀
Frequently Asked Questions
Q: How do the JSONL pipeline tools actually compose together?
Each Gift has a clear contract for what it accepts and emits, so you can wire them in sequence without a framework doing the coordination. Users have successfully chained pluck, schema-filter, and uniq-filter together for data transforms, the output of one lines up naturally with the next tool’s input, making the pipeline transparent and easy to debug.
Q: What’s the real advantage over using npm packages or traditional libraries?
You copy a single file into your project and it just works, no installation step, no version conflicts, no supply-chain overhead. For quick data transforms or one-off analysis tasks, skipping npm entirely is a bigger relief than it sounds, especially when you only need one specific tool.
Q: Can I use these for code cleanup and analysis?
Yes. The census tool, for example, scans your codebase to find stale TODO comments that have been sitting there for years. You can use it standalone or compose it with other Gifts to build larger analysis workflows tailored to your code-quality needs.
Q: Where do I start, and how do I actually use these?
Head to the Dev Guide for hands-on setup instructions, then check the Recipes page for worked examples of Gifts wired together into real workflows. Both are designed for immediate action rather than background reading.
I expanded my Gifts platform- 96 atomic dependency-free, composable MIT-licensed code tools. Super handy for AI dev work
by u/greentide008 in PromptEngineering