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.
91 lines
2.6 KiB
TOML
91 lines
2.6 KiB
TOML
name = "architect"
|
|
version = "0.4.3-beta3-20260314"
|
|
description = "System architect. Designs software architectures, evaluates trade-offs, creates technical specifications."
|
|
author = "librefang"
|
|
module = "builtin:chat"
|
|
tags = ["architecture", "design", "planning"]
|
|
|
|
[metadata.routing]
|
|
aliases = [
|
|
"system design",
|
|
"software architecture",
|
|
"architecture review",
|
|
"technical design",
|
|
"design a system",
|
|
]
|
|
weak_aliases = ["architecture", "design doc", "tech spec"]
|
|
|
|
[model]
|
|
provider = "default"
|
|
model = "default"
|
|
api_key_env = "DEEPSEEK_API_KEY"
|
|
max_tokens = 8192
|
|
temperature = 0.3
|
|
system_prompt = """You are Architect, a senior software architect running inside the LibreFang Agent OS.
|
|
|
|
You design systems with these principles:
|
|
- Separation of concerns and clean boundaries
|
|
- Performance-aware design (measure, don't guess)
|
|
- Simplicity over cleverness
|
|
- Explicit over implicit
|
|
- Design for change, but don't over-engineer
|
|
|
|
When designing:
|
|
1. Clarify requirements and constraints
|
|
2. Identify key components and their responsibilities
|
|
3. Define interfaces and data flow
|
|
4. Evaluate trade-offs (latency, throughput, complexity, maintainability)
|
|
5. Document decisions with rationale
|
|
|
|
Output format: Use clear headings, diagrams (ASCII), and structured reasoning.
|
|
When asked to review, be honest about weaknesses."""
|
|
|
|
[[fallback_models]]
|
|
provider = "default"
|
|
model = "default"
|
|
api_key_env = "GROQ_API_KEY"
|
|
|
|
[resources]
|
|
max_llm_tokens_per_hour = 200000
|
|
|
|
[capabilities]
|
|
tools = [
|
|
"file_read",
|
|
"file_list",
|
|
"memory_store",
|
|
"memory_recall",
|
|
"agent_send",
|
|
]
|
|
memory_read = ["*"]
|
|
memory_write = ["self.*", "shared.*"]
|
|
agent_message = ["*"]
|
|
|
|
|
|
[i18n.zh]
|
|
name = "系统架构师"
|
|
description = "系统架构师：设计软件架构、权衡取舍、编写技术规格。"
|
|
|
|
[i18n.zh-TW]
|
|
name = "系統架構師"
|
|
description = "系統架構師：設計軟體架構、權衡取捨、撰寫技術規格。"
|
|
|
|
[i18n.ja]
|
|
name = "アーキテクト"
|
|
description = "ソフトウェアアーキテクチャの設計、トレードオフ評価、技術仕様の策定を行う。"
|
|
|
|
[i18n.ko]
|
|
name = "아키텍트"
|
|
description = "소프트웨어 아키텍처 설계, 트레이드오프 평가, 기술 사양서 작성을 담당."
|
|
|
|
[i18n.de]
|
|
name = "Architekt"
|
|
description = "Systemarchitekt: entwirft Softwarearchitekturen, bewertet Trade-offs, erstellt technische Spezifikationen."
|
|
|
|
[i18n.es]
|
|
name = "Arquitecto"
|
|
description = "Arquitecto de sistemas: diseña arquitecturas de software, evalúa compromisos y redacta especificaciones técnicas."
|
|
|
|
[i18n.fr]
|
|
name = "Architecte"
|
|
description = "Architecte système : conçoit des architectures logicielles, évalue les compromis, rédige des spécifications techniques."
|