cook: translate skill to English (remove all Czech)

This commit is contained in:
lachtan
2026-09-08 20:43:40 +02:00
parent 6708c59464
commit 18b0586ad7

View File

@@ -3,8 +3,8 @@ name: cook
description: >
Capture and search recipes and tea notes (brewing parameters, origins, tasting
notes) in the cook/ directory — one markdown file per item. Triggers on:
"cook: X", "zapiš recept X", "save recipe X", "co mám na X" (tea/food lookup),
"čaj X", tea temperature/time questions against stored notes. For growing
"cook: X", "save recipe X", "what do I have for X" (tea/food lookup),
"tea X", tea temperature/time questions against stored notes. For growing
personal food & tea knowledge — not a one-off task or a durable user fact.
---
@@ -36,11 +36,11 @@ Subdirs are created by the script on first `add`.
```yaml
type: recept | caj # the only fixed value
category: volná hodnota # polévka, hlavní-chod / zelený, černý...
cuisine: volná # recepts only
origin: volná # caj only
tags: [chata, zima] # user hashtags, no '#'
added: 2026-09-08 # auto
category: free value # soup, main-course / green, black...
cuisine: free value # recepts only
origin: free value # caj only
tags: [chata, winter] # user hashtags, no '#'
added: 2026-09-08 # auto
```
Taxonomy is deliberately free-form — it settles over time, don't force enums.
@@ -56,14 +56,17 @@ Taxonomy is deliberately free-form — it settles over time, don't force enums.
`cook/` — never `git add -A`.
4. Confirm the file path and quote what was filed.
Language: user's (Czech), verbatim where sensible. New content appends **at
the end** of a file; never insert into the middle.
Body language: the user's own (Czech), verbatim where sensible — the content
stays in whatever language the user sends. New content appends **at the end**
of a file; never insert into the middle.
### Body formats — conventions, not rigid schemas
Recipe: `# <název>`, **Ingredience**, **Postup**, **Zdroj**, **Poznámky**.
Tea: `# <název čaje>`, **Země/Typ/Teplota/Čas**, **Poznámky** (chuť, vůně,
odkud koupeno). Adapt to what the user sends; don't force empty fields.
Recipe: `# <name>`, **Ingredients**, **Steps**, **Source**, **Notes**.
Tea: `# <tea name>`, **Country/Type/Temperature/Time**, **Notes** (taste,
smell, where bought). Adapt to what the user sends; don't force empty fields.
Body section headings are free-form — match the user's language and material;
the formats above are defaults, not enforced schemas.
## Search / answer