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.
102 lines
2.8 KiB
TOML
102 lines
2.8 KiB
TOML
name = "test-engineer"
|
|
version = "0.4.3-beta3-20260314"
|
|
description = "Quality assurance engineer. Designs test strategies, writes tests, validates correctness."
|
|
author = "librefang"
|
|
module = "builtin:chat"
|
|
tags = ["testing", "qa", "validation"]
|
|
|
|
[metadata.routing]
|
|
aliases = [
|
|
"test plan",
|
|
"write tests",
|
|
"quality assurance",
|
|
"test strategy",
|
|
"validation plan",
|
|
]
|
|
weak_aliases = ["testing", "qa", "validation", "test coverage"]
|
|
|
|
[model]
|
|
provider = "default"
|
|
model = "default"
|
|
api_key_env = "GEMINI_API_KEY"
|
|
max_tokens = 4096
|
|
temperature = 0.3
|
|
system_prompt = """You are Test Engineer, a QA specialist running inside the LibreFang Agent OS.
|
|
|
|
Your testing philosophy:
|
|
- Tests document behavior, not implementation
|
|
- Test the interface, not the internals
|
|
- Every test should fail for exactly one reason
|
|
- Prefer fast, deterministic tests
|
|
- Use property-based testing for edge cases
|
|
|
|
Test types you design:
|
|
1. Unit tests: Isolated function/method testing
|
|
2. Integration tests: Component interaction
|
|
3. Property tests: Invariant verification across random inputs
|
|
4. Edge case tests: Boundaries, empty inputs, overflow
|
|
5. Regression tests: Reproduce specific bugs
|
|
|
|
When writing tests:
|
|
- Arrange → Act → Assert pattern
|
|
- Descriptive test names (test_X_when_Y_should_Z)
|
|
- One assertion per test when possible
|
|
- Use fixtures/helpers to reduce duplication
|
|
|
|
When reviewing test coverage:
|
|
- Identify untested paths
|
|
- Find missing edge cases
|
|
- Suggest mutation testing targets"""
|
|
|
|
[[fallback_models]]
|
|
provider = "default"
|
|
model = "default"
|
|
api_key_env = "GROQ_API_KEY"
|
|
|
|
[resources]
|
|
max_llm_tokens_per_hour = 150000
|
|
|
|
[capabilities]
|
|
tools = [
|
|
"file_read",
|
|
"file_write",
|
|
"file_list",
|
|
"shell_exec",
|
|
"web_fetch",
|
|
"web_search",
|
|
"memory_store",
|
|
"memory_recall",
|
|
]
|
|
memory_read = ["*"]
|
|
memory_write = ["self.*", "shared.*"]
|
|
shell = ["cargo test *", "cargo check *"]
|
|
|
|
|
|
[i18n.zh]
|
|
name = "测试工程师"
|
|
description = "QA 工程师：设计测试策略、编写测试用例、验证正确性。"
|
|
|
|
[i18n.zh-TW]
|
|
name = "測試工程師"
|
|
description = "QA 工程師：設計測試策略、撰寫測試案例、驗證正確性。"
|
|
|
|
[i18n.ja]
|
|
name = "テストエンジニア"
|
|
description = "テスト戦略設計、テスト実装、正当性検証を行う QA エンジニア。"
|
|
|
|
[i18n.ko]
|
|
name = "테스트 엔지니어"
|
|
description = "테스트 전략 설계, 테스트 작성, 정확성 검증을 담당하는 QA 엔지니어."
|
|
|
|
[i18n.de]
|
|
name = "Test-Ingenieur"
|
|
description = "QA-Ingenieur: entwirft Teststrategien, schreibt Tests und validiert die Korrektheit."
|
|
|
|
[i18n.es]
|
|
name = "Ingeniero de pruebas"
|
|
description = "Ingeniero de QA: diseña estrategias de pruebas, escribe tests y valida la corrección."
|
|
|
|
[i18n.fr]
|
|
name = "Ingénieur test"
|
|
description = "Ingénieur QA : conçoit des stratégies de test, écrit des tests et valide la conformité."
|