200 tools and 200 forms that don't live in a separate menu

200 tools and 200 forms that don't live in a separate menu

Most developers maintain a collection of one-off utilities. A JSON formatter in one bookmark folder. A base64 decoder in another. A cron expression tester in a third. Each tool opens in its own tab, often with its own login. Forms follow the same pattern. You need a contact form, a bug report form, a sign-up form – each built on a different platform, each with its own database. The result is constant context switching. You leave your editor, open a browser, use the tool, copy the output, paste it back. The process repeats for every utility you reach for.

The problem with tool silos

Every tool is a silo. It has its own interface, its own way of handling input and output. When you finish using it, you are left with a text result that you must manually transfer to where it matters. Forms are similar. A submission goes to its own destination – a spreadsheet, an email, a database table – that has no connection to the rest of your work. None of these utilities talk to each other. The friction is not technical; it is architectural.

Xenition’s library: 200 tools and 200 forms

Xenition ships with 200 tools and 200 forms. The tools cover the range of tasks developers reach for every day: JSON validation and formatting, base64 encoding and decoding, UUID generation, URL encoding, cron expression parsing, regular expression testing, code minification, color conversion, timestamp conversion, CSV to JSON, HTML entity encoding, markdown preview, SSL certificate checker, and many more. The forms cover common data collection needs: contact forms, feedback forms, bug report forms, feature request forms, registration forms, survey forms, subscription forms, order forms, RSVP forms, and more.

Both sets are ready to use as-is. But because no single collection fits every workflow, you can also build your own tools and forms. You duplicate an existing tool, modify its logic, and save it as a new one. You duplicate a form, rearrange fields, change the submission target. The library doubles as a starting point for your own creations.

They don’t sit in a separate menu

Most tool collections live in a sidebar or a menu. You click a link, the tool opens in a new page or a modal. You use it, close it, and you’re back where you started – but now you have a window to close and a tab to remove. Xenition does the opposite. Its tools and forms are designed to plug into the applications you already use. When you are editing a document, you can insert a tool inline. When you are inside a spreadsheet, you can attach a form to a cell. When you are in a chat window, you can call a tool without switching apps. The utilities do not require you to leave your current context.

What integration looks like in practice

Imagine writing a blog post in a document editor. You want to check the JSON sample you are about to include. Instead of opening a new browser tab, you type a shortcut and a JSON validator appears directly in the document. You paste the data, it is validated, and you continue writing. No context switch, no copy-paste.

Or consider collecting feedback from users about a new feature. You select a form template, customize the questions, and embed it directly in the documentation page where the feature is described. Responses flow into your project’s issue tracker because the form is plugged into it. You never open a separate form builder or set up a webhook manually.

Tools and forms are not independent windows. They are part of your workspace.

Build your own without leaving your flow

Creating a new tool does not require starting from scratch. You pick a similar one, duplicate it, and modify the logic. The same for forms. Because every tool and form uses the same plugin system, anything you build automatically inherits the integration capabilities – it can appear anywhere the built-in ones can. You never write boilerplate or set up a new server. You extend the library incrementally.

The result: fewer distractions, more consistency

When tools and forms are embedded in your workflow, you make fewer pointless clicks. You keep your mental context. You also gain consistency: all tools share a common interface, all forms share a common submission pattern. No more learning a different UI for every utility. No more wondering where a form submission went. Everything works together because it was designed to.

What to do next

Xenition is an AI workspace built on this idea. If you are a developer who wants to reduce the overhead of separate tools and forms, and you want the ability to create exactly what you need without leaving your current application, open Xenition. Start with one of the 200 tools or forms. Then build one of your own. Notice how often you no longer need to open another menu. That is the shift: from managing a collection of isolated utilities to having a workspace where everything is at hand.