← ClaudeAtlas

astro-mdx-localizationlisted

Translate or update localized Markdown and MDX content in Astro projects while preserving content identity, executable examples, components, assets, and locale navigation. Use when a source article and target locale are provided or inferable from the request.
rgglez/rgglez-dev-skills · ★ 0 · Web & Frontend · score 73
Install: claude install-skill rgglez/rgglez-dev-skills
# Astro MDX localization Translate the requested content using the project's own localization model. Support any source and target languages; do not assume a particular theme, directory layout, package manager, or hosting provider. ## Discover the project conventions Before writing the translation, inspect: - The source file, any existing target translation, and a nearby localized article. An existing target may contain edits worth preserving. - Applicable repository instructions and the content collection schema or loader. Locate these within the actual Astro application, which may be in a monorepo subdirectory. - The routing and translation lookup used by this content. Determine whether translations share a filename, an explicit identifier, a slug, or another key. Do not assume filenames and slugs serve the same purpose. - The application package scripts, package manager, formatter configuration, and Markdown/MDX plugins, including generated table-of-contents behavior. Use this evidence to determine the destination, localized URL, metadata fields, and validation commands. Ask only if the target language or a consequential convention remains ambiguous. Create only the requested locales. ## Preserve identity and meaning - Preserve the article's scope, structure, technical claims, qualifications, numbers, and versions. Translate naturally without adding new material. If the source appears incorrect, report the issue separately rather than silently revi