book-translation_skill

This skill translates The Interactive Book of Prompting content and UI strings into a target language, preserving structure and usability for multilingual

HTML

145.3k

GitHub Stars

1

Bundled Files

3 weeks ago

Catalog Refreshed

2 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstart where the catalogue uses aiagentskills.

npx veilstart add skill f/prompts.chat --skill book-translation

SKILL.md7.2 KB

Overview

This skill helps translate The Interactive Book of Prompting chapters and UI strings into a new language. It provides a practical workflow, file locations, and required edits so the book and its interactive demos work in your target locale. Follow the steps to copy base content, translate MDX and JSON keys, and register locale data for interactive elements.

How this skill works

The skill inspects the book content in src/content/book/{locale}/ and the UI strings in messages/{locale}.json, using Turkish or English as starting templates. It guides copying files, translating MDX prose while preserving JSX and code blocks, and updating the locale data file for interactive demos. Finally, it verifies translations using the provided check script and a local dev server.

When to use it

Adding a new language localization for the interactive book
Updating or improving an existing locale's translations
Preparing localized interactive demo content (tokenizer, temperature samples)
Onboarding translators to a consistent, repeatable workflow
Ensuring interactive components and UI strings are fully localized

Best practices

Start from the provided Turkish template (tr) or English (en) to preserve component structure
Translate only prose; preserve JSX, imports, and code blocks verbatim
Keep terminology consistent across chapters (decide how to translate “prompt”, “API”, “AI”)
Localize interactive demo data in src/components/book/elements/locales/{locale}.ts — this is required
Register the new locale in locales/index.ts so the app recognizes it

Example use cases

Create a German translation by copying tr folder, translating MDX files, and updating messages/de.json
Add Japanese interactive samples (tokenizer, temperature) in the locale TS file so demos remain meaningful
Batch-translate chapter descriptions and titles in messages/{locale}.json before translating long MDX files
Run scripts/check-translations.js and npm run dev to validate content loads at /book for the target locale
Adapt examples culturally (dates, currencies, local places) while keeping code and components unchanged

FAQ

Translate MDX prose in src/content/book/{locale}/ and the book section in messages/{locale}.json. Also translate the locale TS file for interactive demos.

Can I translate from English instead of Turkish?

Yes. Turkish is suggested as a convenient base, but English (en) can be used as the authoritative reference structure.

What must I not change in MDX files?

Do not modify JSX components, import statements, code blocks, className attributes, or Markdown syntax — only translate headings, paragraphs, lists, and link text.