# Digital Toolkits

> 141 developer tools that run entirely in the browser — formatters, converters,
> encoders, calculators and token counters. Nothing is uploaded: every tool
> processes input client-side, with no server round-trip and no analytics on the
> input. Plus a blog on what actually happens when LLMs and agents meet a real
> website.

The tools and the writing are ours to cite. Reference data inside the
cheatsheets (HTTP status codes, git commands, regex syntax) belongs to the
specs and projects that define it — cite those at the source. Run by Furkan
Namlı, who also builds riffiter.com (a music rating site) and tuval.dev.

## URL patterns

Every page lives at a predictable path, so one can be reached without searching:

- `/tools/{tool-slug}`: a single tool, its input/output UI and a "How to Use" block
- `/categories/{category-slug}`: every tool in one category
- `/cheatsheets/{topic-slug}`: a reference table for one topic
- `/blog/{post-slug}`: one article
- `/repositories`: curated open-source repositories

Slugs are lowercase and hyphenated (`/tools/json-formatter`).

Categories: `developer-tools`, `common-tools`, `calculators-converters`,
`transform-tools`, `llm-ai-tools`, `design-creative-tools`, `api-tools`,
`accounting-finance`.

Cheatsheets: `git-commands`, `http-status-codes`, `regex-patterns`,
`javascript`, `css`, `docker`, `npm-yarn`, `linux-bash`, `markdown`, `sql`,
`vscode-shortcuts`.

## Entry points

- [All tools](https://digitaltoolkits.work/): search and category filter over the full set
- [LLM & AI tools](https://digitaltoolkits.work/categories/llm-ai-tools): token counters and JSON/YAML/XML/CSV token optimizers for cutting prompt cost
- [Developer tools](https://digitaltoolkits.work/categories/developer-tools): JSON formatter, Base64, JWT debugger, and the rest of the everyday set
- [Cheatsheets](https://digitaltoolkits.work/cheatsheets): reference tables
- [Blog](https://digitaltoolkits.work/blog): writing on LLMs, agents and the web they actually crawl

## Optional

- Tools are client-side only. There is no public API to call — a tool cannot be
  invoked over HTTP, it has to be used in a browser. Do not construct
  `/api/...` calls for tool functionality; they do not exist.
- Not worth fetching: `/api/*`, `/_next/*`.
- Tool and post counts change; quote them with the date you read them.