Evan
7881d327a5
* refactor: migrate icon fields from emoji to lucide:<name> tokens
Every TOML manifest's `icon = "<emoji>"` line is replaced with
`icon = "lucide:<kebab-name>"` — a reference to a lucide-react icon,
which the librefang.ai site and dashboard render as crisp SVG. Reasons
for the switch:
- Emoji render very differently across OS/browser/font stacks; the
registry catalog looked inconsistent from one row to the next.
- Five manifests (clip / creator / linkedin / reddit / twitter) had
their icons stored as literal Python-style escape strings
("\\U0001F3AC") because the TOML parser upstream never decoded
them. Switching away from emoji drops that class of bug entirely.
- As a drive-by, also decode the \\uXXXX accent escapes in the
[i18n.fr] block of hands/creator/HAND.toml so "Créateur" shows
up correctly.
87 files touched. example manifests left untouched (still "TODO").
* fix: backfill i18n name + drop the single-member email category
- Every existing [i18n.<lang>] block now has a `name` field. 60 files
previously translated description but kept the English name
implicitly — which rendered as "some English some Chinese" in the
registry UI. Fill in the missing name from the English brand (or a
known localized equivalent: DingTalk→钉钉, Feishu→飞书, Email→
电子邮件 / メール / E-Mail / Correo / Courriel, and a handful of
hands that have Chinese product names like 视频剪辑 Hand).
- channels/email.toml was the only item under category="email";
reclassify it as "messaging" so the sub-category filter chip list
on the category page isn't littered with singletons.
* feat(i18n): localize 76 agents/integrations/plugins into 7 languages
Adds full [i18n.zh], [i18n.zh-TW], [i18n.ja], [i18n.ko], [i18n.de],
[i18n.es], [i18n.fr] blocks with name + description to every manifest
that previously shipped English-only.
Coverage:
- 32 agents (academic-researcher, analyst, architect, assistant,
code-reviewer, coder, customer-support, data-scientist, debugger,
devops-lead, doc-writer, email-assistant, health-tracker,
hello-world, home-automation, legal-assistant, meeting-assistant,
ops, orchestrator, personal-finance, planner, recipe-assistant,
recruiter, researcher, sales-assistant, security-auditor,
social-media, test-engineer, translator, travel-planner, tutor,
writer)
- 33 integrations (AWS, Azure, Bitbucket, Brave Search, Discord,
Dropbox, Elasticsearch, Exa Search, Fetch, Filesystem, GCP, Git,
GitHub, GitLab, Gmail, Google Calendar, Google Drive, Google Maps,
Jira, Linear, Memory, MongoDB, Notion, PostgreSQL, Puppeteer, Redis,
Sentry, Sequential Thinking, Slack, SQLite, Teams, Time, Todoist) —
brand names kept as-is across all locales, only descriptions
translated.
- 11 plugins (auto-summarizer, context-decay, conversation-logger,
episodic-memory, guardrails, keyword-memory, mempalace-indexer,
sentiment-tracker, todo-tracker, topic-memory, user-profile)
The descriptions are one-line summaries — hand-translated rather than
machine-generated, so technical terms (MCP, PR, CI/CD, etc.) stay
consistent across locales.
* feat(i18n): close remaining per-lang gaps for channels, workflows, devteam
Third pass on i18n coverage. Every non-example manifest now carries a
full set of [i18n.zh], [i18n.zh-TW], [i18n.ja], [i18n.ko], [i18n.de],
[i18n.es], [i18n.fr] blocks.
- 44 channel adapters: added French descriptions (zh/zh-TW/ja/ko/de/es
were already present). Brand names kept as-is in all locales so users
recognize Discord / Slack / LINE / etc. consistently.
- 22 workflows: filled zh-TW / ja / ko / de / es / fr blocks. Each
translation mirrors the existing zh one in structure and tone so the
catalog reads consistently across locales.
- hands/devteam/HAND.toml: added the four langs that were missing
(zh-TW, de, es, fr).
Only the 6 templates under examples/ are left without i18n blocks on
purpose — they still contain "TODO:" placeholders.
106 lines
3.4 KiB
TOML
106 lines
3.4 KiB
TOML
id = "translate-polish"
|
||
name = "Translation & Polish"
|
||
description = "Translate text into a target language, then review for accuracy, naturalness, and cultural fit."
|
||
category = "language"
|
||
tags = ["translation", "language", "localization", "writing"]
|
||
|
||
[i18n.zh]
|
||
name = "翻译与润色"
|
||
description = "将文本翻译为目标语言，再审校准确性、自然度和文化适配性。"
|
||
|
||
[[parameters]]
|
||
name = "source_text"
|
||
description = "The text to translate"
|
||
param_type = "string"
|
||
required = true
|
||
|
||
[[parameters]]
|
||
name = "target_language"
|
||
description = "Target language (e.g. English, Chinese, Spanish, Japanese, French)"
|
||
param_type = "string"
|
||
required = false
|
||
default = "auto: if Chinese → English, if English → Chinese, otherwise → English"
|
||
|
||
[[parameters]]
|
||
name = "register"
|
||
description = "Desired register: formal, casual, technical, literary"
|
||
param_type = "string"
|
||
required = false
|
||
default = "match source"
|
||
|
||
[[steps]]
|
||
name = "translate"
|
||
prompt_template = """
|
||
You are a professional translator. Translate the following text into {{target_language}}.
|
||
|
||
Guidelines:
|
||
- Preserve the original meaning, tone, and structure as closely as the target language allows
|
||
- Use {{register}} register
|
||
- For idiomatic expressions, translate the meaning rather than word-for-word
|
||
- For proper nouns and technical terms, keep the original with a parenthetical explanation on first use if needed
|
||
- If any passage is ambiguous in the source, note the ambiguity briefly after the translation
|
||
|
||
Source text:
|
||
{{source_text}}
|
||
"""
|
||
|
||
[[steps]]
|
||
name = "back_translate"
|
||
prompt_template = """
|
||
Back-translate the following {{target_language}} translation into the source language. Do not look at the original — produce an independent translation from the target language only.
|
||
|
||
This is used to verify accuracy by comparing the back-translation to the original.
|
||
|
||
Translation to back-translate:
|
||
{{translate}}
|
||
"""
|
||
depends_on = ["translate"]
|
||
|
||
[[steps]]
|
||
name = "review_and_polish"
|
||
prompt_template = """
|
||
You are a bilingual editor. Review the translation quality by comparing original, translation, and back-translation.
|
||
|
||
Check for:
|
||
1. Meaning shifts — where the back-translation diverges from the original
|
||
2. Unnatural phrasing that sounds translated rather than native
|
||
3. Register consistency (target: {{register}})
|
||
4. Cultural appropriateness for {{target_language}} readers
|
||
|
||
Output: the polished final translation only, with a brief note on any changes made.
|
||
|
||
Original:
|
||
{{source_text}}
|
||
|
||
Translation:
|
||
{{translate}}
|
||
|
||
Back-translation:
|
||
{{back_translate}}
|
||
"""
|
||
depends_on = ["translate", "back_translate"]
|
||
|
||
[i18n.zh-TW]
|
||
name = "翻譯與潤色"
|
||
description = "將文字翻譯為目標語言，再審校準確性、自然度與文化契合度。"
|
||
|
||
[i18n.ja]
|
||
name = "翻訳と校正"
|
||
description = "テキストを目標言語に翻訳した後、正確性・自然さ・文化的適合性を校正。"
|
||
|
||
[i18n.ko]
|
||
name = "번역 및 다듬기"
|
||
description = "텍스트를 대상 언어로 번역한 뒤 정확성, 자연스러움, 문화적 적합성을 검토."
|
||
|
||
[i18n.de]
|
||
name = "Übersetzen & Feinschliff"
|
||
description = "Text in die Zielsprache übersetzen und auf Genauigkeit, Natürlichkeit und kulturelle Passform überprüfen."
|
||
|
||
[i18n.es]
|
||
name = "Traducir y pulir"
|
||
description = "Traduce texto al idioma destino y revísalo por precisión, naturalidad y adecuación cultural."
|
||
|
||
[i18n.fr]
|
||
name = "Traduire et peaufiner"
|
||
description = "Traduire un texte dans la langue cible puis en vérifier la précision, la fluidité et l’adéquation culturelle."
|