← All guides

Guide 01 · Estonian

Help your AI write more natural Estonian

“Write in Estonian” is a start, not the whole brief. Give AI your preferred wording, good examples and sources to check uncertainty.

Copyable textDownloadable .mdNo installation required
Quick start

Copy. Fill in the blanks. Try it.

Paste the instructions into your AI chat or attach the file. Fill in the audience, form of address and tone. Then provide the text to revise.

Language instructions with sources
Download .md 
Help me write natural, clear Estonian. Apply these instructions in this conversation. Do not claim that reading a file retrained you or saved the instructions permanently.

MY PREFERENCES
Audience: [who the text is for]
Address: [informal sina or formal teie]
Tone: [for example, practical and friendly]
Preferred terms and corrections: [add here]

WRITING
- Use natural Estonian word order, short sentences and concrete verbs.
- Preserve facts, numbers, dates, names and meaning. Do not add promises or unknown facts.
- Keep code, URLs, commands and filenames unchanged. Preserve õ, ä, ö, ü, š and ž.
- Use consistent terminology. Avoid unnecessary English and em dashes.
- Apply my corrections in this conversation. Ask before broader edits if their meaning or scope is unclear.

SOURCES AND UNCERTAINTY
- For general vocabulary, word meanings and forms, use EKI and Sõnaveeb: https://eki.ee/ and https://sonaveeb.ee/ . Find relevant dictionaries through Keeleveeb: https://keeleveeb.ee/ .
- For IT, information security and data-protection terms, check AKIT: https://akit.cyber.ee/ . Do not label an invented equivalent an official term.
- When explaining a word form, distinguish its lemma, part of speech and inflection. Translate according to meaning and domain rather than isolated words.
- If browsing is unavailable or a source fails to open, say so. Do not claim a lookup happened. Flag the uncertain term and ask for context or a source excerpt when needed.
- If you actually checked a source, link the entry used. Do not reproduce long dictionary definitions or bulk-download dictionaries.

ANSWER
For a rewrite, give the revised text first. Add a short note only for material ambiguity or an unverified term. For a word-meaning or morphology question, give the lemma, a plain explanation and one natural example sentence.

MY TASK OR TEXT
[paste here]

This is a condensed practical adaptation of the existing language-resource guide, not a dictionary or the full source document. It does not guarantee flawless language.

How to use it
  1. 01Original text
  2. 02Your language brief
  3. 03Revised wording
  4. 04Meaning preserved?

If essential information is missing, ask for it. Do not let AI invent the gaps.

Prepared example, not a live AI response

Change the wording, not the promise.

This guide produces a language instruction and checked text, not a newly trained model. The same check applies when rewriting Estonian.

  1. Starting input

    “We hereby wish to inform you that we will provide the quotation no later than 15 September.”

  2. A precise instruction

    Use plain language. Preserve the action and deadline. Add no price, guarantee or new commitment.

  3. Example of the intended result

    “We will send the quotation by 15 September.”

Three checks before use

  • The action is still sending a quotation.
  • The deadline is still 15 September.
  • No price or new commitment was added.

Next: define the whole task more clearly

Same meaning. Less fog.

Prepared examples, not live AI
BEFORE

Teostame teie päringu osas täiendava kontrolli.

AFTER

Kontrollime sinu päringut veel.

BEFORE

Soovime teid informeerida asjaolust, et teie tellimus on teele pandud.

AFTER

Sinu tellimus on teel.

BEFORE

Write it better.

AFTER

Write a short reply to the customer in Estonian. Preserve the facts and dates. Do not add promises.

These examples use informal address. If your business prefers formal address, add that to the language brief.

Give AI sources, not just a role.

This guide adapts the existing “Estonian AI agent training resource guide.md” and OEJ language-review workflow. The principle is simple: verify an uncertain word and its usage instead of merely sounding more confident.

EKI and Sõnaveeb ↗
Word meanings, forms and usage examples.
Keeleveeb ↗
Finding a relevant dictionary or language resource.
AKIT ↗
IT, information security and data-protection terminology.

An AI without browsing cannot open these sources. Ask it to flag unverified terms, or provide a short permitted excerpt with attribution. A URL in an instruction is not evidence that the AI visited it.

Check it with three small tasks
  1. Ask it to explain “majades”. It should distinguish the lemma “maja” from the plural inessive form.
  2. Ask it to correct “Ma õpin Eesti keel.”. The expected sentence is “Ma õpin eesti keelt.”.
  3. Ask it to distinguish encryption from encoding. It must not call them synonyms or claim a source was checked when it was not.

These examples help expose mistakes. They do not certify flawless Estonian.

A source map is not a dictionary copy. Check reuse terms before collecting or distributing dictionary content. Attaching a file does not retrain the model.

Once or for repeated use

Choose one route. You do not need all of them.

1. Paste it into a conversation

The simplest start. Provide the instructions before the task and correct specific errors in the response. A new conversation may need the instructions again.

2. Attach the Markdown file

Download and attach the file. Add: “Use the attached file as the language instructions for my Estonian writing.” If attachments are unsupported, paste the file contents into the chat.

Reading the file does not retrain the model. Do not include customer data or confidential text unless you know where the service sends it.

3. Save reusable instructions or a skill

If your software supports personal or project instructions, save the same text there. Names and limits vary. Agent skills are a separate mechanism: renaming a file to SKILL.md does not prove it was installed.

“I want to reuse the attached language instructions. First ask which AI software I use. Check its supported instruction or skill format. Propose the file and installation location, and ask before changing existing settings. If you lack file access, give manual steps. Do not claim installation is complete until it has been verified.”

After saving, open a new conversation and try one of the checks above. This helps check whether the instructions are active, although one good answer does not establish lasting reliability.

A correction beats a complaint.

“This sounds bad” leaves AI guessing. Instead say: “Use seadistus here, not viisard. Change only this paragraph.” When corrections repeat, add the recurring preferences to your instructions.

These are your style preferences, not a universal list of forbidden Estonian words. In technical writing, a precise specialist term can be better than a simpler substitute.

Next · Guide 02From a short idea to a clear prompt →

Support my AI habit

You chip in. I keep experimenting. The useful bits become guides. The rest make good stories.

The guides stay free. Chipping in is entirely optional.