How to use /tools/t runner pages (presets, instructions, and length)

Many “how to use [tool name]” queries refer to our lightweight runners at /tools/t/<slug>. Examples: email writer, AI summarizer, sentence rewriter. They share one pattern: instruction + optional advanced fields + generate.

1. Read the placeholder example

Each tool ships an example line tuned to that task. Replace it with your specifics; keep constraints (word limits, tone, bullet vs prose) explicit.

2. Use advanced options as contract hints

Presets (email vs poem vs rewrite) fold into the prompt sent for generation. They help the model stay in lane when the instruction is short.

3. Language and tone

Set target language and tone in the panel when those options appear. If output language drifts, restate “Answer in …” in the instruction as a backup.

4. Iterate in small edits

For rewrites, say exactly what must stay unchanged (names, dates, legal phrases). For generators, ask for variants (“give three subject lines”) instead of one vague “improve.”

5. Discover more runners

Browse the full list in the directory; anything without a dedicated workspace card still opens under /tools/t/ when clicked.