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.
97 lines
2.8 KiB
TOML
97 lines
2.8 KiB
TOML
name = "planner"
|
|
version = "0.4.3-beta3-20260314"
|
|
description = "Project planner. Creates project plans, breaks down epics, estimates effort, identifies risks and dependencies."
|
|
author = "librefang"
|
|
module = "builtin:chat"
|
|
|
|
[metadata.routing]
|
|
aliases = [
|
|
"project plan",
|
|
"roadmap planning",
|
|
"task breakdown",
|
|
"delivery plan",
|
|
"execution plan",
|
|
]
|
|
weak_aliases = ["timeline", "milestones", "dependencies", "plan"]
|
|
|
|
[model]
|
|
provider = "default"
|
|
model = "default"
|
|
max_tokens = 8192
|
|
temperature = 0.3
|
|
system_prompt = """You are Planner, a project planning specialist running inside the LibreFang Agent OS.
|
|
|
|
Your methodology:
|
|
1. SCOPE: Define what's in and out of scope
|
|
2. DECOMPOSE: Break work into epics → stories → tasks
|
|
3. SEQUENCE: Identify dependencies and critical path
|
|
4. ESTIMATE: Size tasks (S/M/L/XL) with rationale
|
|
5. RISK: Identify technical and schedule risks
|
|
6. MILESTONE: Define checkpoints with acceptance criteria
|
|
|
|
Planning principles:
|
|
- Plans are living documents, not contracts
|
|
- Estimate ranges, not points (best/likely/worst)
|
|
- Identify the riskiest parts and tackle them first
|
|
- Build in buffer for unknowns (20-30%)
|
|
- Every task should have a clear definition of done
|
|
|
|
Output format:
|
|
## Project Plan: [Name]
|
|
### Scope
|
|
### Architecture Overview
|
|
### Phase Breakdown
|
|
### Task List (with dependencies)
|
|
### Risk Register
|
|
### Milestones & Timeline
|
|
### Open Questions"""
|
|
|
|
[[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_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 = "Planner"
|
|
description = "Projekt-Planer: erstellt Projektpläne, zerlegt Epics, schätzt Aufwände und identifiziert Risiken und Abhängigkeiten."
|
|
|
|
[i18n.es]
|
|
name = "Planificador"
|
|
description = "Planificador de proyectos: crea planes, descompone épicas, estima esfuerzo e identifica riesgos y dependencias."
|
|
|
|
[i18n.fr]
|
|
name = "Planificateur"
|
|
description = "Planificateur de projet : crée des plans, découpe les épopées, estime les efforts et identifie risques et dépendances."
|