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.2 KiB
TOML
106 lines
3.2 KiB
TOML
id = "refactor-plan"
|
||
name = "Refactor Plan"
|
||
description = "Analyse code for quality issues, prioritise refactoring opportunities, and produce a safe incremental migration plan."
|
||
category = "engineering"
|
||
tags = ["refactoring", "code-quality", "engineering", "architecture"]
|
||
|
||
[i18n.zh]
|
||
name = "重构计划"
|
||
description = "分析代码质量问题，优先排序重构机会，制定安全的增量迁移计划。"
|
||
|
||
[[parameters]]
|
||
name = "code"
|
||
description = "Code to refactor"
|
||
param_type = "string"
|
||
required = true
|
||
|
||
[[parameters]]
|
||
name = "context"
|
||
description = "Why refactoring is being considered (performance, maintainability, tech debt)"
|
||
param_type = "string"
|
||
required = false
|
||
default = "general code quality improvement"
|
||
|
||
[[steps]]
|
||
name = "smell_analysis"
|
||
prompt_template = """
|
||
You are a senior software architect performing a code quality audit. Identify all code smells and issues:
|
||
|
||
For each issue found:
|
||
- Category: naming / duplication / complexity / coupling / abstraction / performance / security
|
||
- Severity: critical / high / medium / low
|
||
- Location: function/class name
|
||
- Description: what is wrong
|
||
- Impact: why it matters
|
||
|
||
Context: {{context}}
|
||
|
||
Code:
|
||
{{code}}
|
||
"""
|
||
|
||
[[steps]]
|
||
name = "prioritised_opportunities"
|
||
prompt_template = """
|
||
Prioritise refactoring opportunities by: (impact × risk_reduction) / effort.
|
||
|
||
For the top 5 opportunities:
|
||
- What to change
|
||
- Expected benefit
|
||
- Estimated effort: hours
|
||
- Risk level: low / medium / high
|
||
- Prerequisites: what must be done first
|
||
- Whether tests are needed before refactoring
|
||
|
||
Smell analysis:
|
||
{{smell_analysis}}
|
||
"""
|
||
depends_on = ["smell_analysis"]
|
||
|
||
[[steps]]
|
||
name = "migration_plan"
|
||
prompt_template = """
|
||
Design an incremental refactoring plan that keeps the system working throughout:
|
||
|
||
**Phase 1 — Safety net** (tests and coverage)
|
||
**Phase 2 — Low-risk quick wins**
|
||
**Phase 3 — Structural changes**
|
||
**Phase 4 — Validation and cleanup**
|
||
|
||
For each phase:
|
||
- Specific changes in order
|
||
- How to verify nothing broke after each change
|
||
- Rollback strategy
|
||
- Definition of done
|
||
|
||
Also note: what NOT to change in this refactoring cycle.
|
||
|
||
Prioritised opportunities:
|
||
{{prioritised_opportunities}}
|
||
"""
|
||
depends_on = ["prioritised_opportunities"]
|
||
|
||
[i18n.zh-TW]
|
||
name = "重構計劃"
|
||
description = "分析程式碼品質問題、優先排序重構機會，制定安全的漸進式遷移計劃。"
|
||
|
||
[i18n.ja]
|
||
name = "リファクタリング計画"
|
||
description = "コードの品質問題を解析し、リファクタリングの優先度を決め、安全な漸進的移行計画を作成。"
|
||
|
||
[i18n.ko]
|
||
name = "리팩터링 계획"
|
||
description = "코드 품질 이슈를 분석하고 리팩터링 기회를 우선순위화하며, 안전한 점진적 마이그레이션 계획을 수립."
|
||
|
||
[i18n.de]
|
||
name = "Refactoring-Plan"
|
||
description = "Code auf Qualitätsprobleme analysieren, Refactoring-Chancen priorisieren und einen sicheren, inkrementellen Migrationsplan erstellen."
|
||
|
||
[i18n.es]
|
||
name = "Plan de refactorización"
|
||
description = "Analiza problemas de calidad, prioriza oportunidades de refactorización y elabora un plan incremental y seguro de migración."
|
||
|
||
[i18n.fr]
|
||
name = "Plan de refactoring"
|
||
description = "Analyser les problèmes de qualité, prioriser les opportunités de refactoring et produire un plan de migration incrémental et sûr."
|