SkillsAdd

smithery/bnomei

kirby-i18n-workflows

Manages Kirby multi-language workflows, translations, and localized labels. Use when dealing with languages, translation keys, placeholders, or importing/exporting translations.

Installation

$ npx skills add smithery/bnomei --skill kirby-i18n-workflows
View on skills.sh ↗ Website ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

find-skills Same topic
vercel-labs/skills

Helps users discover and install agent skills when they ask questions like "how do I do X", "fi…

3.3M installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-prepare Same topic
microsoft/azure-skills

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Te…

568.3K installs

Also in this package

Other skills from smithery/bnomei · top by installs.

npx skills add smithery/bnomei
kirby-upgrade-and-maintenance 0 kirby-security-and-auth 0 kirby-project-tour 0 kirby-plugin-development 0 kirby-performance-and-media 0 kirby-panel-and-blueprints 0 kirby-ide-support 0 kirby-headless-api 0 kirby-forms-and-frontend-actions 0 kirby-debugging-and-tracing 0

Browse all from smithery/bnomei

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,964 B
  • docs SUMMARY.md 205 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Kirby i18n Workflows

KB entry points

  • kirby://kb/scenarios/46-i18n-field-options-and-labels
  • kirby://kb/scenarios/47-i18n-find-translation-keys
  • kirby://kb/scenarios/48-i18n-import-export-translations
  • kirby://kb/scenarios/72-filter-by-language
  • kirby://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(' site and compare keys with site/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

  1. Confirm language setup with kirby://config/languages and locate language files via kirby://roots.
  2. Inspect templates/snippets/controllers for translation usage; use rg to find t( calls if needed.
  3. Search the KB with kirby:kirby_search (examples: "translate field options", "find translation keys", "import export translations", "language variables placeholders").
  4. Update language files (site/languages/*.php) or config maps for option labels.
  5. Ensure templates render translated labels (not stored keys) and use fallbacks.
  6. Verify by rendering representative pages in each language (kirby:kirbyrenderpage).