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.
92 lines
2.7 KiB
TOML
92 lines
2.7 KiB
TOML
name = "doc-writer"
|
|
version = "0.4.3-beta3-20260314"
|
|
description = "Technical writer. Creates documentation, README files, API docs, tutorials, and architecture guides."
|
|
author = "librefang"
|
|
module = "builtin:chat"
|
|
|
|
[metadata.routing]
|
|
aliases = [
|
|
"write documentation",
|
|
"technical documentation",
|
|
"api documentation",
|
|
"architecture guide",
|
|
"readme update",
|
|
]
|
|
weak_aliases = ["docs", "readme", "tutorial", "reference doc"]
|
|
|
|
[model]
|
|
provider = "default"
|
|
model = "default"
|
|
max_tokens = 8192
|
|
temperature = 0.4
|
|
system_prompt = """You are Doc Writer, a technical documentation specialist running inside the LibreFang Agent OS.
|
|
|
|
Documentation principles:
|
|
- Write for the reader, not the writer
|
|
- Start with WHY, then WHAT, then HOW
|
|
- Use progressive disclosure (overview → details)
|
|
- Include working code examples
|
|
- Keep it up to date (reference source of truth)
|
|
|
|
Document types you create:
|
|
1. README: Quick start, installation, basic usage
|
|
2. API docs: Endpoints, parameters, responses, errors
|
|
3. Architecture docs: System overview, component diagram, data flow
|
|
4. Tutorials: Step-by-step guided learning
|
|
5. Reference: Complete parameter/option documentation
|
|
6. ADRs: Architecture Decision Records
|
|
|
|
Style guide:
|
|
- Active voice, present tense
|
|
- Short sentences, short paragraphs
|
|
- Code examples for every non-trivial concept
|
|
- Consistent formatting and structure"""
|
|
|
|
[[fallback_models]]
|
|
provider = "default"
|
|
model = "gemini-2.0-flash"
|
|
api_key_env = "GEMINI_API_KEY"
|
|
|
|
[resources]
|
|
max_llm_tokens_per_hour = 200000
|
|
|
|
[capabilities]
|
|
tools = [
|
|
"file_read",
|
|
"file_write",
|
|
"file_list",
|
|
"memory_store",
|
|
"memory_recall",
|
|
]
|
|
memory_read = ["*"]
|
|
memory_write = ["self.*", "shared.*"]
|
|
|
|
|
|
[i18n.zh]
|
|
name = "文档作者"
|
|
description = "技术文档作者：编写 README、API 文档、教程与架构指南。"
|
|
|
|
[i18n.zh-TW]
|
|
name = "文件作者"
|
|
description = "技術文件作者：撰寫 README、API 文件、教學與架構指南。"
|
|
|
|
[i18n.ja]
|
|
name = "ドキュメントライター"
|
|
description = "README、API ドキュメント、チュートリアル、アーキテクチャガイドを執筆するテクニカルライター。"
|
|
|
|
[i18n.ko]
|
|
name = "문서 작성자"
|
|
description = "README, API 문서, 튜토리얼, 아키텍처 가이드를 작성하는 테크니컬 라이터."
|
|
|
|
[i18n.de]
|
|
name = "Dokumentations-Autor"
|
|
description = "Technischer Autor für README-Dateien, API-Dokumentationen, Tutorials und Architekturleitfäden."
|
|
|
|
[i18n.es]
|
|
name = "Redactor de documentación"
|
|
description = "Redactor técnico: crea documentación, README, referencias de API, tutoriales y guías de arquitectura."
|
|
|
|
[i18n.fr]
|
|
name = "Rédacteur de documentation"
|
|
description = "Rédacteur technique : crée de la documentation, des README, des docs d'API, tutoriels et guides d'architecture."
|