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.
111 lines
3.3 KiB
TOML
111 lines
3.3 KiB
TOML
id = "market-research"
|
||
name = "Market Research Report"
|
||
description = "Analyse a market opportunity: size, trends, customer segments, key players, and go-to-market entry points."
|
||
category = "business"
|
||
tags = ["market", "research", "strategy", "business"]
|
||
|
||
[i18n.zh]
|
||
name = "市场调研报告"
|
||
description = "分析市场机会：市场规模、趋势、客户细分、主要参与者和进入市场的切入点。"
|
||
|
||
[[parameters]]
|
||
name = "market"
|
||
description = "The market or industry to research"
|
||
param_type = "string"
|
||
required = true
|
||
|
||
[[parameters]]
|
||
name = "business_context"
|
||
description = "Your company, product, or investment thesis context"
|
||
param_type = "string"
|
||
required = false
|
||
default = ""
|
||
|
||
[[steps]]
|
||
name = "market_landscape"
|
||
prompt_template = """
|
||
You are a market research analyst. Map the current landscape for: {{market}}
|
||
|
||
1. **Market definition** — precise scope and adjacent markets
|
||
2. **Market size** — TAM, SAM, SOM estimates with methodology
|
||
3. **Growth rate** — historical and projected CAGR
|
||
4. **Maturity stage** — emerging / growth / mature / declining
|
||
5. **Key trends** — top 5 forces shaping the market (technology, regulation, behaviour)
|
||
6. **Geographic distribution** — where activity is concentrated
|
||
|
||
Context: {{business_context}}
|
||
"""
|
||
|
||
[[steps]]
|
||
name = "customer_segments"
|
||
prompt_template = """
|
||
Identify and profile the customer segments in this market:
|
||
|
||
For each segment (aim for 3-5):
|
||
- Name and size
|
||
- Demographics/firmographics
|
||
- Key pain points and jobs-to-be-done
|
||
- Current solutions they use
|
||
- Willingness to pay signals
|
||
- Acquisition channels
|
||
- Which segment is most underserved
|
||
|
||
Market landscape:
|
||
{{market_landscape}}
|
||
"""
|
||
depends_on = ["market_landscape"]
|
||
|
||
[[steps]]
|
||
name = "research_report"
|
||
prompt_template = """
|
||
Write a structured market research report:
|
||
|
||
## Executive Summary
|
||
3 bullet points: opportunity, risk, recommended entry point.
|
||
|
||
## Market Overview
|
||
## Customer Segments
|
||
## Competitive Landscape
|
||
Top players by segment, their moats and vulnerabilities.
|
||
|
||
## Market Entry Analysis
|
||
- Best beachhead segment
|
||
- Entry barriers and how to overcome them
|
||
- Differentiation opportunities
|
||
- Estimated time to meaningful traction
|
||
|
||
## Key Risks
|
||
## Recommended Next Steps
|
||
|
||
Market landscape:
|
||
{{market_landscape}}
|
||
|
||
Customer segments:
|
||
{{customer_segments}}
|
||
"""
|
||
depends_on = ["market_landscape", "customer_segments"]
|
||
|
||
[i18n.zh-TW]
|
||
name = "市場研究報告"
|
||
description = "分析市場機會：市場規模、趨勢、客戶區隔、主要玩家與進入切入點。"
|
||
|
||
[i18n.ja]
|
||
name = "市場調査レポート"
|
||
description = "市場機会を分析：規模、トレンド、顧客セグメント、主要プレイヤー、GTM の切り口。"
|
||
|
||
[i18n.ko]
|
||
name = "시장 조사 보고서"
|
||
description = "시장 기회 분석: 규모, 트렌드, 고객 세그먼트, 주요 플레이어, GTM 진입점."
|
||
|
||
[i18n.de]
|
||
name = "Marktforschungsbericht"
|
||
description = "Eine Marktchance analysieren: Größe, Trends, Kundensegmente, Key-Player und Go-to-Market-Einstiegspunkte."
|
||
|
||
[i18n.es]
|
||
name = "Informe de investigación de mercado"
|
||
description = "Analiza una oportunidad de mercado: tamaño, tendencias, segmentos de clientes, actores clave y puntos de entrada GTM."
|
||
|
||
[i18n.fr]
|
||
name = "Étude de marché"
|
||
description = "Analyser une opportunité de marché : taille, tendances, segments clients, acteurs clés et points d’entrée GTM."
|