mcpField
B
book-translation

book-translation

github.com/fDocuments174.9k675 installsUpdated today
Repository

About book-translation

A translation workflow skill for localizing The Interactive Book of Prompting. It guides contributors through MDX chapters, JSON interface strings, locale registration, and validation.

Key features

  1. 01MDX chapter translation workflow
  2. 02JSON strings and metadata localization
  3. 03Locale file setup and registration
  4. 04Translation checks and browser verification

Use cases

  1. 01Localizing book chapters into a new language
  2. 02Translating interactive examples and UI labels
  3. 03Checking that a locale loads correctly

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/f/prompts.chat --skill book-translation

After installing, type/book-translationin Claude Code to confirm it loaded.

Details

From the project README

Book Translation Skill

This skill guides translation of book content for The Interactive Book of Prompting at prompts.chat.

Overview

The book has 29 chapters across 7 parts. Translation requires:

  1. MDX content files - Full chapter content in src/content/book/{locale}/
  2. JSON translation keys - UI strings, chapter titles, and descriptions in messages/{locale}.json

Prerequisites

Before starting, identify:

  • Target locale code (e.g., de, fr, es, ja, ko, zh)
  • Check if locale exists in messages/ directory
  • Check if src/content/book/{locale}/ folder exists

Step 1: Copy Turkish Folder as Base

The Turkish (tr) translation is complete and well-tested. Copy it as your starting point instead of translating from English:

mkdir -p src/content/book/{locale}
cp -r src/content/book/*.mdx src/content/book/{locale}/
cp src/components/book/elements/locales/en.ts src/components/book/elements/locales/{locale}.ts

⚠️ IMPORTANT: After copying, you MUST register the new locale in src/components/book/elements/locales/index.ts:

  1. Add import: import {locale} from "./{locale}";
  2. Add to locales object: {locale},
  3. Add to named exports: export { en, tr, az, {locale} };

This is faster because:

  • Turkish and many languages share similar sentence structures
  • All JSX/React components are already preserved correctly
  • File structure is already set up
  • You only need to translate the prose, not recreate the structure

Step 2: Translate MDX Content Files

Edit each copied file in src/content/book/{locale}/ to translate from Turkish to your target language.

Process files one by one:

Chapter List (in order)
SlugEnglish Title
00a-prefacePreface
00b-historyHistory
00c-introductionIntroduction
01-understanding-ai-modelsUnderstanding AI Models
02-anatomy-of-effective-promptAnatomy of an Effective Prompt
03-core-prompting-principlesCore Prompting Principles
04-role-based-promptingRole-Based Prompting
05-structured-outputStructured Output
06-chain-of-thoughtChain of Thought
07-few-shot-learningFew-Shot Learning
08-iterative-refinementIterative Refinement
09-json-yaml-promptingJSON & YAML Prompting
10-system-prompts-personasSystem Prompts & Personas
11-prompt-chainingPrompt Chaining
12-handling-edge-casesHandling Edge Cases
13-multimodal-promptingMultimodal Prompting
14-context-engineeringContext Engineering
15-common-pitfallsCommon Pitfalls
16-ethics-responsible-useEthics & Responsible Use
17-prompt-optimizationPrompt Optimization
18-writing-contentWriting & Content
19-programming-developmentProgramming & Development
20-education-learningEducation & Learning
21-business-productivityBusiness & Productivity
22-creative-artsCreative Arts
23-research-analysisResearch & Analysis
24-future-of-promptingThe Future of Prompting
25-agents-and-skillsAgents & Skills
27-tools-mcp-connectorsTools, MCP and Connectors
26-the-harnessesThe Harnesses
28-persistent-botsAlways-On Bots: Agents That Keep Working
MDX Translation Guidelines
  1. Preserve all JSX/React components - Keep <div>, <img>, className, etc. unchanged
  2. Preserve code blocks - Code examples should remain in English (variable names, keywords)
  3. Translate prose content - Headings, paragraphs, lists
  4. Keep Markdown syntax - ##, **bold**, *italic*, [links](url)
  5. Preserve component imports - Any import statements at the top

Step 3: Translate JSON Keys

In messages/{locale}.json, translate the "book" section. Key areas:

Book Metadata
"book": {
  "title": "The Interactive Book of Prompting",
  "subtitle": "An Interactive Guide to Crafting Clear and Effective Prompts",
  "metaTitle": "...",
  "metaDescription": "...",
  ...
}
Chapter Titles (book.chapters)
"chapters": {
  "00a-preface": "Preface",
  "00b-history": "History",
  "00c-introduction": "Introduction",
  ...
}
Chapter Descriptions (book.chapterDescriptions)
"chapterDescriptions": {
  "00a-preface": "A personal note from the author",
  "00b-history": "The story of Awesome ChatGPT Prompts",
  ...
}
Part Names (book.parts)
"parts": {
  "introduction": "Introduction",
  "foundations": "Foundations",
  "techniques": "Techniques",
  "advanced": "Advanced Strategies",
  "bestPractices": "Best Practices",
  "useCases": "Use Cases",
  "conclusion": "Conclusion"
}
Interactive Demo Examples (book.interactive.demoExamples)

Localize example text for demos (tokenizer samples, temperature examples, etc.):

"demoExamples": {
  "tokenPrediction": {
    "tokens": ["The", " capital", " of", " France", " is", " Paris", "."],
    "fullText": "The capital of France is Paris."
  },
  "temperature": {
    "prompt": "What is the capital of France?",
    ...
  }
}
Book Elements Locales (REQUIRED)

⚠️ DO NOT SKIP THIS STEP - The interactive demos will not work in the new language without this.

Translate the locale data file at src/components/book/elements/locales/{locale}.ts:

  • Temperature examples, token predictions, embedding words
  • Capabilities list, sample conversations, strategies
  • Tokenizer samples, builder fields, chain types
  • Frameworks (CRISPE, BREAK, RTF), exercises
  • Image/video prompt options, validation demos

Then register it in src/components/book/elements/locales/index.ts:

import {locale} from "./{locale}";

const locales: Record<string, LocaleData> = {
  en,
  tr,
  az,
  {locale},  // Add your new locale here
};

export { en, tr, az, {locale} };  // Add to exports
UI Strings (book.interactive.*, book.chapter.*, book.search.*)

Translate all interactive component labels and navigation strings.

Step 4: Verify Translation

  1. Run the check script:

    node scripts/check-translations.js
    
  2. Start dev server and test:

    npm run dev
    
  3. Navigate to /book with the target locale to verify content loads

Reference: English Translation

The English (en) translation is complete and serves as the base template for all new translations:

  • MDX files: src/content/book/*.mdx — copy this files to src/content/book/{locale}/*.mdx
  • JSON keys: messages/en.json → book section — use as reference for structure
Recommended Workflow
  1. Copy src/content/book/*.mdx to src/content/book/{locale}/*.mdx
  2. Copy the "book" section from messages/en.json to messages/{locale}.json. Translate these in multiple agentic session instead of single time (token limit may exceed at once)
  3. Edit each file, translating English → target language
  4. Keep all JSX components, code blocks, and Markdown syntax intact

Quality Guidelines

  • Consistency: Use consistent terminology throughout (e.g., always translate "prompt" the same way)
  • Technical terms: Some terms like "AI", "ChatGPT", "API" may stay in English
  • Cultural adaptation: Adapt examples to be relevant for the target audience where appropriate
  • Natural language: Prioritize natural-sounding translations over literal ones

Comments

Markdown supported