Too many websites
Common tasks like formatting JSON, decoding tokens, and converting text often require jumping between unrelated pages.
Project Taste developer toolbox documentation
Project Taste is a privacy-first collection of browser-based developer tools. This page explains what the app is, why it exists, how to use it, and what every registered tool is expected to do.
Problems Project Taste Solves
Developers often need small utilities many times a day. The problem is not that these tools are complex; the problem is that they are scattered, inconsistent, and often unsafe for sensitive content.
Sensitive data risk
API payloads, JWTs, logs, keys, and configuration snippets should not be pasted into unknown remote services.
Workflow friction
A utility should open fast, explain itself clearly, process input locally, and let the user copy or export the result.
How To Use The App
Project Taste is designed around quick movement: search, open, paste, process, copy, and continue working.
- Open the app from `index.html` through a local static server.
- Use the sidebar, global search, or `Ctrl + K` command palette to find a tool.
- Paste text, upload a file, or enter the input required by the selected tool.
- Use the tool action buttons to format, validate, convert, generate, inspect, or compare.
- Copy, download, or reuse the output without leaving the browser.
Documentation Model
Registry driven
Tool names, categories, descriptions, badges, icons, and statuses are loaded from `data/tools.json`.
Local-first
Tools are expected to process input in the browser. If a future tool needs network access, it should document that behavior.
Easy to extend
Each ready tool should have a matching `tools/<tool-id>.html` file and an initializer registered in `window.TasteTools`.
Tool Catalog
Search the catalog or filter by readiness. Each tool entry includes its purpose, common use cases, usage steps, expected output, and privacy notes.
Loading documentation...