kirby-i18n-workflows
Manages Kirby multi-language workflows, translations, and localized labels. Use when dealing with languages, translation keys, placeholders, or importing/exporting translations.
pinned to #3474420updated 3 weeks ago
Ask your AI client: “install skills/kirby-i18n-workflows”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/kirby-i18n-workflowsmetahub onboarded this repo on the author's behalf.
If you own github.com/bnomei/kirby-mcp on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
56
Last commit
3 weeks ago
Latest release
published
- #agent-tools
- #agentic-workflow
- #claude-code
- #cli
- #codex-cli
- #commands
- #developer-tools
- #google-gemini
- #kirby
- #kirby-cms
- #knowledge-base
- #mcp-server
- #model-context-protocol
- #php8
- #prompts
- #resources
- #tools
Evaluation report
WarningsAutomated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.3474420· 3 weeks ago
Kind-specific
31Skill: SKILL.md present
found at skills/kirby-i18n-workflows/SKILL.md · frontmatter source: SKILL.md
Skill: body content present
212 words · 1,736 chars · 7 sections · 1 code block
Skill: triggers declaredwarn
No `trigger` phrases in SKILL.md frontmatter
Add `trigger:` lines so Claude knows when to activate this skill — e.g. `when building MCP servers` or `for diagram creation`.
Skill: allowed-tools scope
no allowed-tools restriction (Claude may use anything)
Release history
1- releasecurrent3474420warn3 weeks ago
Contents
KB entry points
kirby://kb/scenarios/46-i18n-field-options-and-labelskirby://kb/scenarios/47-i18n-find-translation-keyskirby://kb/scenarios/48-i18n-import-export-translationskirby://kb/scenarios/72-filter-by-languagekirby://kb/scenarios/73-language-variables-and-placeholders
Required inputs
- Enabled languages and default language.
- Where translation keys live and desired naming scheme.
- Which content is translated vs label-only.
Default translation rule
- Use
t('key', 'fallback')in templates and snippets. - Keep stored content language-neutral when possible; translate labels at render time.
- Maintain fallback strings in the default language file.
Import/export hint
return [
'site.title' => 'Example',
];
Missing key audit
- Run
rg -F 't(' siteand compare keys withsite/languages/*.php. - Add missing keys to the default language file first.
Common pitfalls
- Storing translated labels in content instead of language files.
- Using translation keys without fallback strings.
Workflow
- Confirm language setup with
kirby://config/languagesand locate language files viakirby://roots. - Inspect templates/snippets/controllers for translation usage; use
rgto findt(calls if needed. - Search the KB with
kirby:kirby_search(examples: "translate field options", "find translation keys", "import export translations", "language variables placeholders"). - Update language files (
site/languages/*.php) or config maps for option labels. - Ensure templates render translated labels (not stored keys) and use fallbacks.
- Verify by rendering representative pages in each language (
kirby:kirby_render_page).
Reviews
No reviews yet. Be the first.
Related
orchestration-patterns
>
migration-patterns
>
deployment-sop
>
mh install skills/kirby-i18n-workflows