book-translation

f/prompts.chat · Agent Skill

Translates chapters and UI strings of "The Interactive Book of Prompting" to a new language, using Turkish as a base.

Jump to install ↓

Overview

PublisherfCommunity
Repositoryf/prompts.chat ↗
Skill folderbook-translation
Stars169,722
Bundled files1
Licensenot specified — check with the author
Last updatedJanuary 29, 2026
LinksSkill source ↗ · Repository ↗

Mozgi check

What we found in the skill files. Details come with a subscription.

Security
medium risk · 1 point needs attention
Compatibility
needs extra software
Similar skills
133 similar skills found
Also with subscription

Installation

A skill is a folder with a SKILL.md file. Pick your agent and run the commands in a terminal (macOS, Linux or Git Bash on Windows) from your project root.

Copy the prompt into Claude, Codex or another assistant: it will review the skill and install it for you.

Install the “book-translation” skill from mozgi.io (https://mozgi.io/skills/book-translation/) for me.

1. Download the archive: https://mozgi.io/skills/book-translation/download
   If it fails, take the skill folder from the source: https://github.com/f/prompts.chat/tree/main/.windsurf/skills/book-translation
2. Read SKILL.md and the other files. Check the skill is safe: no hidden commands, no sending data elsewhere, no scripts doing something other than described. If anything looks suspicious, stop and tell me.
3. Put the “book-translation” folder into your agent's skills folder: .claude/skills/ for Claude Code, .agents/skills/ for Codex, .cursor/skills/ for Cursor, .gemini/skills/ for Gemini CLI. Inside the project if we are in one, otherwise in the home folder (~/.claude/skills/ etc.).
4. Make sure <skills folder>/book-translation/SKILL.md exists.
5. Briefly tell me what this skill does and offer to try it on my task.

If you cannot do a step yourself, tell me what to click or type.

Review the source files

1 file Download Zip

Read SKILL.md and any companion files before deciding whether to install. Click a file to preview it.

SKILL.md contents

Original author text · read-only

Book Translation Skill

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

Overview

The book has 25 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)

| Slug | English Title |

|------|---------------|

| 00a-preface | Preface |

| 00b-history | History |

| 00c-introduction | Introduction |

| 01-understanding-ai-models | Understanding AI Models |

| 02-anatomy-of-effective-prompt | Anatomy of an Effective Prompt |

| 03-core-prompting-principles | Core Prompting Principles |

| 04-role-based-prompting | Role-Based Prompting |

| 05-structured-output | Structured Output |

| 06-chain-of-thought | Chain of Thought |

| 07-few-shot-learning | Few-Shot Learning |

| 08-iterative-refinement | Iterative Refinement |

| 09-json-yaml-prompting | JSON & YAML Prompting |

| 10-system-prompts-personas | System Prompts & Personas |

| 11-prompt-chaining | Prompt Chaining |

| 12-handling-edge-cases | Handling Edge Cases |

| 13-multimodal-prompting | Multimodal Prompting |

| 14-context-engineering | Context Engineering |

| 15-common-pitfalls | Common Pitfalls |

| 16-ethics-responsible-use | Ethics & Responsible Use |

| 17-prompt-optimization | Prompt Optimization |

| 18-writing-content | Writing & Content |

| 19-programming-development | Programming & Development |

| 20-education-learning | Education & Learning |

| 21-business-productivity | Business & Productivity |

| 22-creative-arts | Creative Arts |

| 23-research-analysis | Research & Analysis |

| 24-future-of-prompting | The Future of Prompting |

| 25-agents-and-skills | Agents & Skills |

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 ↗

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:

```bash

node scripts/check-translations.js

```

2. Start dev server and test:

```bash

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

Frequently asked questions

What does the book-translation skill do?

Translates chapters and UI strings of "The Interactive Book of Prompting" to a new language, using Turkish as a base.

How do I install book-translation?

Open the “Installation” block on this page and pick your agent — Claude Code, Codex, Cursor or Gemini CLI — for ready-made commands that copy the skill folder to the right place. Or copy the prompt from the “Via assistant” tab and let the assistant review and install the skill.

Which AI models work with book-translation?

Skills are plain Markdown instructions (the Agent Skills format), so book-translation works with any agent that reads SKILL.md: Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and more. The model loads the instructions only when a task matches the skill's description.

Is book-translation free?

The skill is published openly by f. The skill itself costs nothing — you only pay your AI provider for the tokens you use. No license is specified in the repository — check the terms with the author before commercial use.

Is it safe to install skills?

A skill is a set of instructions your agent will follow, so read SKILL.md and its companion files before installing. Scripts in the skill folder only run if your agent runs them — keep an eye on what it does and do not grant unnecessary permissions.

How is a skill different from an MCP server or a plugin?

An MCP server or plugin gives the model new tools — code that runs and returns a result. A skill gives it knowledge and process: how to approach a task, which steps to follow and what good output looks like. It needs no server or API key.

Related skills

All skills →