About

Who writes this, and how.

howtogetaito.com is a library of 120 guides, each answering one question of the form “how to get AI to …”. It is published by Adapt Progress Evolve Limited (registered in England and Wales, company no. 10047328, registered office 5 Brayford Square, London E1 0SG, VAT GB362654684), a London software studio, in the voice and under the name of its founder — and made, appropriately enough, by getting AI to do a good deal of the work, with the rules and the responsibility staying human.

The author

The hilyt profile is the canonical, owner-confirmed record of who Jack is and what he has built; every claim on it carries a source, and the Companies House link is the public register entry for the studio.

How a guide is made

1. Pick the question people actually ask. The topic list comes from what people type into Google after “how to get AI to”, plus questions we get asked directly. If nobody asks it, it is not on the site.
2. Write the fact sheet first. Before any prose, each topic gets a short sheet naming the real tools, what they actually do, what they cost only where that is stable, and the cautions that matter — health, money, rights, privacy, consent. The sheet is compiled from the tools’ own documentation, not from memory.
3. Draft in Jack’s voice. The first draft is produced with ScriptGrain, our writing tool, from that fact sheet and a measured profile of Jack’s own writing. That is an AI draft, and we say so plainly.
4. Read every word, open every link. Adapt Progress Evolve is a studio run by its founder with a fleet of AI agents, and we are open about which is which: the review pass is done by an editorial agent working to a fixed checklist — read the whole draft, open every URL, check each product claim against the fact sheet and the tool’s own pages, strip anything invented (including any first-person anecdote the drafting model made up), correct stale facts, rewrite the sources to pages that exist. Jack reads the guides, sets the rules the agent works to, and answers for every one of them. The review date at the foot of each guide is the date that pass happened.
5. Answer the questions people ask. Each guide ends with a short “Questions people ask” section. The questions are the ones people type into search for that task; every answer is drawn from the guide’s own text by a model and checked against it, so nothing appears there that the guide does not already say.
6. Publish, then keep it honest. A topic with no finished guide says so and stays out of the sitemap. When a tool changes, the guide is updated and its “last updated” date moves; the published date never does.

Our own products

Some guides recommend a product we make. When they do, it leads only where it genuinely fits, real alternatives are named alongside it, and a disclosure line appears at the end of the guide, generated from the guide’s metadata so it cannot be forgotten. We make ScriptGrain, hilyt, ReviewNudge and a few others; the full list is above. We have no affiliate relationships and take no money from any tool named on this site. Outbound links carry a ref parameter so the sites we link to can see the traffic came from here; that is all it does.

How “Plan it” recommends

The homepage can turn what you want into a plan. Every recommendation comes from one catalogue — the assistants, tools and workflows behind the guides, each with a cost band, a difficulty, privacy flags and the date we last checked it. First, your words are matched against that catalogue on our own server; a close match returns the guide’s own plan. When nothing matches closely, the six nearest entries and your words go to Claude (Anthropic) once, which writes a short plan under a schema that only lets it name things from those entries; our server then re-checks every name against the catalogue and drops the whole plan if anything is outside it. Composed plans say so on the card, and their steps are written for you, not reviewed by a person, so we link the nearest guide for the checked version. Our own products can be switched off in either path with “show without”, and the choice is remembered in your browser. Costs are always bands with dates, never numbers.

Use it from your own assistant

The same recommender is open to other software, read-only and without a key, so an assistant asked “how do I get AI to…” can look here and cite the guide:

• API — GET https://howtogetaito.com/api/recommend?ask=plan+a+week+of+meals returns JSON: the matching guide (confidence: match) or a composed plan (confidence: composed) with steps, assistant, tools, cost band, difficulty and privacy notes. Add &ours=0 to leave our own products out. Twenty requests a minute per address. Asks are kept, without anything that identifies the sender, to decide which guides to write next — see Privacy.
• Personalised guide — GET https://howtogetaito.com/api/guide?ask=analyse+customer+feedback&situation=400+Trustpilot+reviews+a+month,+free+ChatGPT retrieves the passages of the published guides, tool cards and glossary that fit, and writes a guide for that situation (confidence: guide): steps with the prompt to type, checks, privacy notes, assistant, tools, cost band, difficulty — and every step carries the passage it came from (guide, section, URL, last-updated date). Anything the passages do not support is left out. Written by Claude, not reviewed by a person; the cited guides were.
• MCP — a remote server at https://howtogetaito.com/mcp (Streamable HTTP, no sign-in) with four tools: recommend_ai_workflow, personalised_guide, search_guides and list_categories. In Claude Code: claude mcp add --transport http howtogetaito https://howtogetaito.com/mcp; in claude.ai, add it as a custom connector with that URL.

Both answer from the catalogue described above and carry the same disclosure: tools flagged ours are ours, costs are bands with a checked date, and a composed plan says it was not reviewed by a person.

Proof, not promises

Where a guide makes a claim we can test, we test it and show the result: for example, what four AI assistants actually say when asked who Jack is, or whether they cite one of our sites. Those panels are generated from real runs on the date shown and are re-run periodically. If a result is unflattering, it stays on the page.

Corrections

If something in a guide is wrong, out of date, or a tool has changed, email hello@howtogetaito.com with the guide’s address and what needs fixing. Corrections that change advice are made in the guide and its “last updated” date moves; we do not silently rewrite history.

The site itself

No cookies, no third-party tools. We run our own anonymous analytics — pages viewed, how far people read, which links get clicked — with no IP address or identity stored, and a switch on the privacy page to turn it off for your browser. Search runs in your browser. We also log which AI systems and search crawlers fetch which pages, by user-agent string. The site is served to AI readers as plain text at /llms.txt.