mkl-localize-pl-en

Translate and localize Polish and English technical documentation while preserving code and placeholders.

11|1|Updated Sep 13, 2026
One-click install
npx skills add https://github.com/00200200/maintainer-skills-lab --skill mkl-localize-pl-en-00200200
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mkl-localize-pl-en
Source: https://github.com/00200200/maintainer-skills-lab/tree/main/providers/cursor/.cursor/skills/mkl-localize-pl-en
Command: npx skills add https://github.com/00200200/maintainer-skills-lab --skill mkl-localize-pl-en-00200200

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Translating technical content between Polish and English often breaks commands, placeholders, and formatting, or loses factual nuance like uncertainty and negation. This Skill produces natural PL/EN translations that keep protected content intact and respect project terminology. ## Core Features & Use Cases - Protected Content Handling: Preserves code, commands, paths, URLs, identifiers, interpolation tokens, and quoted literals while translating surrounding prose. - Glossary-Aware Terminology: Applies an existing project glossary before choosing new terms, keeping English technical terms where the project uses them. - Locale and Grammar Precision: Handles Polish case, aspect, forms of address, and plural systems, and flags ambiguous dates like 04/05/2026 instead of guessing. - Use Case: Localize a Polish README section containing kit --dry-run and a {max_mb} placeholder into English, receiving a translation where every command and token is byte-identical to the source. ## Quick Start Translate this Polish documentation paragraph into English, keeping all commands, placeholders, and units unchanged.

Frequently Asked Questions about mkl-localize-pl-en

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

FAQPage Schema
How do I translate Polish technical documentation to English without breaking code snippets?▼

Separate prose from protected content such as code, commands, paths, URLs, and interpolation tokens before translating. Translate only the prose, then verify every protected span against the source so commands and placeholders remain byte-identical.

How to localize UI text between Polish and English with placeholders?▼

Keep interpolation tokens like {max_mb} untouched and translate only the surrounding display text. In localization files, preserve keys and valid syntax, and follow the project's plural system rather than treating Polish as a two-form language.

Should English technical terms be translated into Polish?▼

Keep English technical terms when the project glossary already uses them. Apply the existing glossary before choosing new terminology so translations stay consistent with established project vocabulary.

What happens with ambiguous dates like 04/05/2026 during translation?▼

Ambiguous dates are flagged for clarification rather than interpreted. Numbers, units, versions, and time zones are kept equivalent, and measurements or currencies are never converted unless explicitly requested.

Can machine translation handle Polish grammar correctly for product UI?▼

Polish requires correct case, aspect, forms of address, and plural categories, which generic translation often mishandles. This Skill selects forms to fit the product or author and uses neutral phrasing when the user's gender is unknown.