Repository navigation
Design Decisions
The reasoning behind how Mools is built, including the trade-offs.
Decision: no backend, no database, no accounts. Why: privacy is the point. People paste tokens, JSON and passwords into tools like these. If nothing is uploaded, nothing can leak. It also makes hosting free and permanent on GitHub Pages. Trade-off: tools that need a server (for example anything that fetches other websites) are out of scope. The Telegram tester works because it calls Telegram's API directly from the browser.
Decision: src/lib/tools.js is the one list of tools.
Why: the early site kept the same tool list in four places (sidebar, home, category pages, features) and they drifted apart. Generating everything from one list also made llms.txt, tools.json and search nearly free.
Decision: logic in src/lib, UI in components.
Why: it makes testing easy (132 tests so far) and lets one function power the web page, WebMCP and the MCP server. Several real bugs were caught this way, such as entities being unescaped twice.
Decision: ToolPage and ConvertPage.
Why: almost every tool is "text in, result out". Sharing the layout keeps tools consistent (copy, clear, errors, dark mode) and short to write.
Decision: upgrade from Svelte 4 and SvelteKit 1 in one go (v0.4.0).
Why: the old stack was two major versions behind and a bad base for new work. SvelteKit 3 moved its configuration into vite.config.js and removed $lib, so imports now use #lib/... through package.json imports.
Decision: keep Halfmoon for theming. Why: three ready-made cores (Default, Modern, Elegant) and dark mode with almost no custom CSS. The Halfmoon docs also inspired the sidebar layout and the command palette.
Decision: adapter-static with trailingSlash: 'always' and a /tools base path.
Why: GitHub Pages serves static files under the repository name. The base path is the reason for a few quirks, such as using resolve() for links.
Decision: heavy dependencies (PDF, HEIC, QR, bcrypt, SQL formatter...) are imported by the pages that use them. Why: the home page stays small and quick even with 115 tools.
Decision: publish llms.txt, tools.json, WebMCP and an MCP server.
Why: a lot of people now work with AI assistants, and small deterministic tools are exactly what agents are bad at doing in their heads (hashing, encoding, exact arithmetic).
- Token counts are estimates, not exact.
- The JWT decoder never verifies signatures.
- Offline use is not supported yet, because there is no service worker.
- The only automatic network request is a cached call to GitHub for the star count.
Mools (Maling-IT Online Tools) is open source under the MIT license. Found a mistake on a wiki page? Edit it, or open an issue.
The project
Using Mools
Building Mools