translate-lesson

Translates English MDX lessons into peninsular Spanish twins while preserving frontmatter, slugs, and component props.

3|1|Updated Jun 20, 2026
One-click install
npx skills add https://github.com/alexfdez1010/mental-models --skill translate-lesson-alexfdez1010
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: translate-lesson
Source: https://github.com/alexfdez1010/mental-models/tree/main/.claude/skills/translate-lesson
Command: npx skills add https://github.com/alexfdez1010/mental-models --skill translate-lesson-alexfdez1010

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Bilingual education sites must keep every English lesson and its Spanish twin in perfect parity — same slugs, order, headings, and interactive component labels — which is tedious and error-prone to maintain by hand. ## Core Features & Use Cases - Locale-aware translation: Produces peninsular Spanish (es-ES, Castilian) with vosotros register and Spain-specific vocabulary, never Latin-American variants. - Structural parity enforcement: Keeps frontmatter fields (order, minutes, icon, accent), heading hierarchy, imports, code blocks, and client directives identical across the en/es pair. - Component label localization: Translates interactive island props (MCQ, Quiz, MatchConcepts, FillBlank, MindMap labels) so UI chrome renders in Spanish. - Use Case: After authoring a new English lesson on mental models, run this Skill to generate the mirrored es-ES MDX file, then verify parity with bun run check and regenerate OG cards. ## Quick Start Translate the English lesson at src/content/lessons/en/biases/anchoring.mdx into its Spanish twin and keep all frontmatter and component labels in parity.

Frequently Asked Questions about translate-lesson

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

FAQPage Schema
How do I translate an MDX lesson into Spanish for an Astro site?

Mirror the English file at the same path under the es/ content folder, translate title, description, tagline, prose, and component label props, and keep slugs, order, imports, and code blocks identical. Run bun run check to verify parity.

How do I keep bilingual content in sync across locales?

Keep slugs and folder names identical across locales, copy frontmatter with only locale-bound fields changed, match heading counts and nesting, and bump the updated field on both twins whenever content changes.

What Spanish variant should I use for a Spain-based audience?

Use peninsular Spanish (es-ES, Castilian): vosotros for informal plural, tú for singular, and Spain vocabulary like ordenador, móvil, and vale. Avoid Latin-American forms such as ustedes, computadora, or celular.

Which component props need translation in interactive MDX islands?

Translate UI label props such as MCQ checkLabel and retryLabel, Quiz questionLabel and scoreLabel, FillBlank instructions and answer options, and every MindMap node label. Confirm exact prop names against the component source before writing.

Why does my bilingual lesson fail the parity check?

Parity checks fail when heading counts differ, slugs or order values diverge, or frontmatter fields like minutes and icon were translated instead of copied. Compare both twins and ensure only prose and label props differ.