skills.rest
cyberpunk042
cyberpunk042COMMUNITY
Explore all skills by this author →
GitHub

evolve-internationalize

Internationalize AICP operator-facing surfaces with locale resolution and English fallback.

Updated Mar 26, 2026
Search Tags:#translation#i18n#prompts#internationalization#locales#cli-messages#kb-content
One-click install
npx skills add https://github.com/cyberpunk042/devops-expert-local-ai --skill evolve-internationalize
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: evolve-internationalize
Source: https://github.com/cyberpunk042/devops-expert-local-ai/tree/main/.claude/skills/evolve-internationalize
Command: npx skills add https://github.com/cyberpunk042/devops-expert-local-ai --skill evolve-internationalize

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AICP currently uses English-only operator-facing surfaces and lacks a scalable plan for multilingual support, limiting adoption in non-English contexts and increasing translation latency.

Core Features & Use Cases

  • Locale resolution for operator-facing strings (CLI prompts, error messages, docs) with English fallback.
  • Decision-driven partial i18n implementation (CLI, KB, prompts) that can be deployed in stages.
  • Lightweight governance: create a decision/plan page before implementing i18n, so scope and responsibilities are clear.

Quick Start

Define the concrete i18n surface scope and draft a minimal locale resolver and translation plan.

Frequently Asked Questions about evolve-internationalize

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

FAQPage Schema
How do I internationalize CLI messages and error strings for non-English operators?▼

Internationalize CLI messages by implementing a locale resolver and translation storage with English fallback. This applies to operator-facing surfaces like error strings, prompts, and generated documentation to support multilingual contexts.

What is the best way to add multilingual support to KB content and documentation?▼

Add multilingual support to KB content by creating a decision-driven plan before implementation. Apply staged scope to KB content and generated documentation using a single locale resolver to manage translation provenance metadata and English fallback.

How does locale resolution with English fallback work for internationalization?▼

Locale resolution with English fallback works by checking available translations for a resolved locale and defaulting to English strings when a translation is missing. This ensures operator-facing surfaces remain functional while multilingual coverage expands in stages.

Can I deploy internationalization in stages for specific surfaces like prompts and CLI?▼

Yes, you can deploy internationalization in stages for specific surfaces. The implementation supports decision-driven partial i18n, allowing you to target CLI messages, prompts, or KB content independently with integration points in core modules.

Do I need to create a governance plan before implementing i18n for operator-facing surfaces?▼

Yes, you need to create a decision or plan page before implementing i18n. This lightweight governance step ensures scope and responsibilities are clear before adding locale resolvers and translation storage to core modules.

Related Skills

Explore More Software Engineering Skills→
BrunoSantanaDeveloperBrunoSantanaDeveloper

i18n-localization

Detect hardcoded strings in React, Vue, and Python codebases.

Community
Intermediate
SumitRajpalSumitRajpal

fix-translations

Identify and fill missing translation keys across locale JSON files.

Community
Intermediate
InverterNetworkInverterNetwork

blogwatcher

Manage RSS/Atom feed updates and track article read status via blogwatcher-cli.

Official
Intermediate
lildibbblildibbb

i18n

Manage translations and locales in React applications with flat key naming conventions.

Community
Intermediate