Files
librefang-registry/workflows/job-application.toml
T
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

114 lines
3.9 KiB
TOML
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
id = "job-application"
name = "Job Application Package"
description = "Tailor a resume and cover letter to a specific job posting, then prepare targeted interview talking points."
category = "productivity"
tags = ["career", "resume", "job", "interview"]
[i18n.zh]
name = "求职材料准备"
description = "针对特定职位定制简历和求职信,并准备有针对性的面试谈话要点。"
[[parameters]]
name = "job_posting"
description = "The full job posting or description"
param_type = "string"
required = true
[[parameters]]
name = "resume"
description = "Your current resume or experience summary"
param_type = "string"
required = true
[[steps]]
name = "job_analysis"
prompt_template = """
Analyse the job posting as an experienced recruiter:
1. **Must-have requirements** — skills/experience that are non-negotiable
2. **Nice-to-have requirements** — preferred but not required
3. **Company signals** — culture, values, team dynamics from the language used
4. **Role signals** — what success looks like in 90 days, key challenges
5. **Keywords** — ATS-critical terms to include in application materials
6. **Red flags** — anything unusual or concerning in the posting
Job posting:
{{job_posting}}
"""
[[steps]]
name = "resume_tailoring"
prompt_template = """
Tailor the resume for this specific role:
1. **Reorder sections** — put most relevant experience first
2. **Rewrite bullet points** — for each experience, suggest stronger versions that match job keywords
3. **Quantify impacts** — flag any bullet points that should have metrics added
4. **Gaps to address** — experience or skills missing vs. the role requirements
5. **Summary statement** — write a 3-sentence tailored summary for the top of the resume
Job analysis:
{{job_analysis}}
Resume:
{{resume}}
"""
depends_on = ["job_analysis"]
[[steps]]
name = "cover_letter"
prompt_template = """
Write a compelling cover letter (3-4 paragraphs, under 400 words):
- Opening: specific hook connecting your background to the company's mission
- Body: 2 concrete achievements that directly address the job's must-haves
- Closing: clear ask + why this specific company
Avoid clichés like 'I am writing to apply' or 'I am a hard worker'.
Job analysis:
{{job_analysis}}
Resume:
{{resume}}
"""
depends_on = ["job_analysis"]
[[steps]]
name = "interview_prep"
prompt_template = """
Prepare interview talking points:
1. **STAR stories** — 3 specific situations from the resume mapped to the job's key requirements
2. **Questions to ask** — 5 smart questions that show deep interest
3. **Difficult questions** — likely tough questions for this role with suggested answers
4. **Salary research** — how to position compensation discussion
Job analysis:
{{job_analysis}}
Resume:
{{resume}}
"""
depends_on = ["job_analysis", "resume_tailoring"]
[i18n.zh-TW]
name = "求職應聘包"
description = "針對特定職位客製履歷與求職信,並準備具針對性的面試談話要點。"
[i18n.ja]
name = "応募パッケージ"
description = "特定の求人に合わせて履歴書とカバーレターをカスタマイズし、的を射た面接トーキングポイントを準備。"
[i18n.ko]
name = "입사 지원 패키지"
description = "특정 채용 공고에 맞춰 이력서와 커버레터를 맞춤화하고, 타겟팅된 면접 대화 포인트를 준비."
[i18n.de]
name = "Bewerbungspaket"
description = "Lebenslauf und Anschreiben passgenau auf eine Stellenausschreibung zuschneiden und gezielte Gesprächspunkte für das Interview vorbereiten."
[i18n.es]
name = "Paquete de candidatura"
description = "Adapta el CV y la carta de presentación a una oferta específica y prepara puntos clave enfocados para la entrevista."
[i18n.fr]
name = "Dossier de candidature"
description = "Adapter un CV et une lettre de motivation à une offre précise, puis préparer des points de discussion ciblés pour l’entretien."