Build your own tools

You can have an AI build you a small tool — a calculator, an analysis, a checklist. What you get back is one file — a small folder for bigger tools. Save it, double-click it, done. No installation, no account, no server. Your data stays on your device.

How it works

Open an AI that can read web pages — a chat is enough.
Paste the paragraph below.
Write what you need after it, in plain words.
Save what you get and double-click it.

Paste this:

Follow the build guide at
https://ai-build-guide.flomotlik.me/llms.txt
before you write any code.

Give me something I can save and open by
double-clicking — no installation, no
server, no terminal.

What I need:

It points the AI at the build guide, which sets out how such a tool has to be built. Add "write the interface in <your language>" if that is not English.

The same paragraph works in tools that write straight into a folder on your machine — Claude Code, Cowork or Projects, and the equivalents from other providers. Then you save nothing by hand: the folder arrives finished, and you double-click the index.html inside it.

Examples

"Work out four options for compensation payments to neighbouring municipalities, with a control total."
"Read this attendee list as CSV and show me the breakdown by district."
"A meeting-preparation checklist that remembers what I ticked off."
"A form that produces a finished motion text I can copy out."
"An image in our layout with title, date and location, ready to download."

If a task happens only once, you do not need a tool — the chat answer is faster. Tools pay off when something recurs, or when the result has to be defensible.

What else is here

The build guide

The actual rules the AI follows: what to build, how to read and write files, charts, images, layout, and how to make the result checkable. You do not have to read it — the AI fetches it.

When one file is not enough

For later: several pages, a public address via GitHub Pages, and what to check before a folder becomes public.

Two things up front

What the AI should not see

Names with addresses, dates of birth, bank details, donor and member lists, confidential papers. Describe the structure instead ("a table with the columns Name, District, Amount"), have the tool built against that, and open the real file only in the finished tool — it never leaves your device.

The same applies to tools with folder access: whatever sits in the project folder can be read, including files you never showed it. Keep such documents somewhere else.

Checking the numbers stays with you

The AI computes, you know the subject. Check a total you already know, and whether something you expect is missing. Ask explicitly for a control total and for the number of rows it actually read.