translation-keys

Generate and validate i18n translation keys using predefined conventions.

6|1|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/MinBZK/storybook --skill translation-keys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: translation-keys
Source: https://github.com/MinBZK/storybook/tree/main/.claude/skills/translation-keys
Command: npx skills add https://github.com/MinBZK/storybook --skill translation-keys

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the creation and management of translation keys for internationalization (i18n) microcopy, ensuring consistency and efficiency in multilingual applications.

Core Features & Use Cases

  • Standardized Key Generation: Automatically generate or validate translation keys based on predefined conventions.
  • Component-Specific Keys: Create and manage keys for individual UI components.
  • Customizable Types: Support various text formatting types like lowercase, capitalize, title, and label.
  • Use Case: Ideal for developers and designers working on applications requiring multilingual support, such as web and mobile apps.

Quick Start

Generate translation keys for the component 'button' using the translation-keys skill.

Frequently Asked Questions about translation-keys

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate consistent i18n translation keys for UI components?

Generate i18n translation keys for UI components by applying predefined naming conventions to your microcopy. This approach automates key creation and validation, ensuring structured and consistent internationalization keys for multilingual applications.

What is the best way to manage microcopy translation keys for internationalization?

Managing microcopy translation keys for internationalization requires a standardized approach to naming and formatting. This skill provides structured key generation based on component-specific conventions and text formatting types like lowercase, capitalize, title, and label.

Can I validate existing i18n translation keys against predefined conventions?

Yes, you can validate existing i18n translation keys against predefined conventions. The skill checks component-specific keys and various text formatting types to ensure your multilingual application maintains a consistent internationalization structure.

Does this translation key generator support different text formatting types?

Yes, translation key generation supports multiple text formatting types including lowercase, capitalize, title, and label. This allows you to create component-specific i18n keys that match the exact microcopy context required by your UI.

When do I need automated translation key generation for my application?

You need automated translation key generation when building multilingual web or mobile applications that require consistent i18n microcopy. It is ideal when your UI components demand structured internationalization keys following strict predefined conventions.