Files
Evan 7881d327a5 refactor: migrate icon fields from emoji to lucide:<name> tokens (#63)
* 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.
2026-04-17 22:04:26 +09:00

132 lines
4.3 KiB
TOML

id = "content-pipeline"
name = "Content Creation Pipeline"
description = "Research a topic, build a structured outline, write a full article, then edit for clarity, flow, and factual consistency."
category = "creation"
tags = ["content", "writing", "article", "research"]
[i18n.zh]
name = "内容创作流水线"
description = "调研主题,构建结构化提纲,撰写完整文章,再编辑润色以提升清晰度、流畅性和事实准确性。"
[[parameters]]
name = "topic"
description = "The topic to research and write about"
param_type = "string"
required = true
[[parameters]]
name = "audience"
description = "Target audience (e.g. general public, developers, executives, students)"
param_type = "string"
required = false
default = "general audience"
[[parameters]]
name = "word_count"
description = "Target word count for the article"
param_type = "string"
required = false
default = "800-1200"
[[parameters]]
name = "tone"
description = "Desired tone (informative, conversational, technical, persuasive)"
param_type = "string"
required = false
default = "informative"
[[steps]]
name = "researcher"
prompt_template = """
You are a research journalist. Investigate the following topic for a {{audience}} audience:
1. Background and context — why this topic matters now
2. Key facts and data points (be specific)
3. Multiple perspectives — mainstream view, contrarian view, expert consensus
4. Recent developments or trends
5. Concrete examples, case studies, or anecdotes
6. Common misconceptions to address
Topic: {{topic}}
"""
[[steps]]
name = "outline"
prompt_template = """
You are a content strategist. Create a detailed article outline using the research below.
Include:
- Three headline options (hook-driven, question-based, and statement-based)
- Opening hook strategy
- H2 sections with H3 subsections and the key point each section makes
- Which research fact or example belongs in each section
- Closing argument and call to action
Target: {{word_count}} words, {{tone}} tone, audience: {{audience}}
Research:
{{researcher}}
"""
depends_on = ["researcher"]
[[steps]]
name = "writer"
prompt_template = """
Write the full article following the outline. Requirements:
- Use the best headline from the outline
- Open with the hook strategy from the outline
- Short paragraphs (3-4 sentences max)
- Subheadings for each major section
- Weave in the specific facts and examples from research — no vague generalities
- Match the {{tone}} tone throughout
- End with a concrete takeaway and CTA relevant to a {{audience}} reader
- Target length: {{word_count}} words
Outline:
{{outline}}
Research:
{{researcher}}
"""
depends_on = ["outline", "researcher"]
[[steps]]
name = "editor"
prompt_template = """
You are a senior editor. Polish the article below:
1. Fix grammar, punctuation, and spelling
2. Tighten wordy or repetitive sentences
3. Improve transitions between sections
4. Flag any factual claims that seem unsupported and suggest how to strengthen them
5. Verify the tone is consistent with '{{tone}}' throughout
Output the final polished article only, then add a brief editor's note listing the main changes made.
Draft:
{{writer}}
"""
depends_on = ["writer"]
[i18n.zh-TW]
name = "內容創作流水線"
description = "調研主題、建立結構化大綱、撰寫完整文章,再潤色以提升清晰度、流暢度與事實一致性。"
[i18n.ja]
name = "コンテンツ制作パイプライン"
description = "トピック調査、構造化アウトライン、完全記事の執筆、明快さ・流れ・事実整合性の編集を一気通貫で実施。"
[i18n.ko]
name = "콘텐츠 제작 파이프라인"
description = "주제 조사, 구조화된 개요 작성, 전체 기사 집필, 명확성·흐름·사실 일관성을 위한 편집까지 수행."
[i18n.de]
name = "Content-Pipeline"
description = "Thema recherchieren, Outline erstellen, vollständigen Artikel schreiben und anschließend auf Klarheit, Fluss und sachliche Konsistenz editieren."
[i18n.es]
name = "Pipeline de contenido"
description = "Investiga un tema, crea un esquema, escribe el artículo completo y luego lo edita para claridad, fluidez y consistencia factual."
[i18n.fr]
name = "Pipeline de contenu"
description = "Rechercher un sujet, bâtir un plan structuré, rédiger un article complet puis le relire pour la clarté, la fluidité et la cohérence factuelle."