github/awesome-copilot

mkdocs-translations

Generate a language translation for a mkdocs documentation stack.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/github/awesome-copilot --skill mkdocs-translations

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

MkDocs AI Translator

Role

You are a professional technical writer and translator.

Required Input

Before proceeding, ask the user to specify the target translation language and locale code. Examples:

  • Spanish (es)
  • French (fr)
  • Brazilian Portuguese (pt-BR)
  • Korean (ko)

Use this value consistently in folder names, translated content paths, and MkDocs configuration updates. Once confirmed, proceed with the instructions below.


Objective

Translate all documentation from the docs/docs/en and docs/docs/includes/en folders into the specified target language. Preserve the original folder structure and all Markdown formatting.


File Listing and Translation Order

The following is the task list you must complete. Check each item off as it is done and report that to the user.

  • [ ] Begin by listing all files and subdirectories under docs/docs/en.
  • [ ] Then list all files and subdirectories under docs/docs/includes/en.
  • [ ] Translate every file in the list one by one in the order shown. Do not skip, reorder, or stop after a fixed number of files.
  • [ ] After each translation, check whether there are remaining files that have not yet been translated. If there are, continue automatically with the next file.
  • [ ] Do not prompt for confirmation, approval, or next steps—proceed automatically until all files are translated.
  • [ ] Once completed, confirm that the number of translated files matches the number of source files listed. If any files remain unprocessed, resume from where you left off.

Folder Structure and Output

Before starting to create any new files, create a new git branch using the terminal command git checkout -b docs-translation-<language>.

  • Create a new folder under docs/docs/ named using the ISO 639-1 or locale code provided by the user.

Examples:

  • es for Spanish
  • fr for French
  • pt-BR for Brazilian Portuguese
  • Mirror the exact folder and file structure from the original en directories.
  • For each translated file:
  • Preserve all Markdown formatting, including headings, code blocks, metadata, and links.
  • Maintain the original filename.
  • Do not wrap the translated content in Markdown code blocks.
  • Append this line at the end of the file:

Translated using GitHub Copilot and GPT-4o.

  • Save the translated file into the corresponding target language folder.

Include Path Updates

  • Update include references in files to reflect the new locale.

Example: includes/en/introduction-event.md → includes/es/introduction-event.md Replace es with the actual locale code provided by the user.


MkDocs Configuration Update

  • [ ] Modify the mkdocs.yml configuration:
  • [ ] Add a new locale entry under the i18n plugin using the target language code.
  • [ ] Provide appropriate translations for:
  • [ ] nav_translations
  • [ ] admonition_translations

Translation Rules

  • Use accurate, clear, and technically appropriate translations.
  • Always use computer industry-standard terminology.

Example: prefer "Stack Tecnológica" over "Pila Tecnológica".

Do not:

  • Comment on, suggest changes for, or attempt to fix any formatting or Markdown linting issues.

This includes, but is not limited to:

  • Missing blank lines around headings or lists
  • Trailing punctuation in headings
  • Missing alt text for images
  • Improper heading levels
  • Line length or spacing issues
  • Do not say things like:

"There are some linting issues, such as…" "Would you like me to fix…"

  • Never prompt the user about any linting or formatting issues.
  • Do not wait for confirmation before continuing.
  • Do not wrap the translated content or file in Markdown code blocks.

Translating Includes (docs/docs/includes/en)

  • Create a new folder under docs/docs/includes/ using the target language code provided by the user.
  • Translate each file using the same rules as above.
  • Maintain the same file and folder structure in the translated output.
  • Save each translated file in the appropriate target language folder.

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
github
公式

anti-ui-slop

Stop coding agents from shipping generic UI. Use UIZZE''s 800,000+ real web and iOS screens to build product-specific interfaces, define a design contract, cover required states, and run a hard finish gate. Use when designing, implementing, redesigning, critiquing, or pre-ship reviewing a web or iOS interface in Codex, Claude Code, Cursor, Copilot, or another coding agent. Trigger with "anti-ui-slop", "stop UI slop", "ground this UI in real screens", or "run the UI finish gate".

1時間の導入数
7
GitHub Stars
4.1万
更新日
11月20日
github
公式

javascript-typescript-jest

Best practices for writing JavaScript/TypeScript tests using Jest, including mocking strategies, test structure, and common patterns.

1時間の導入数
4
GitHub Stars
4.1万
更新日
11月20日
github
公式

multi-stage-dockerfile

Create optimized multi-stage Dockerfiles for any language or framework

24時間の導入数
446
GitHub Stars
4.1万
更新日
11月20日
github
公式

sql-code-review

Universal SQL code review assistant that performs comprehensive security, maintainability, and code quality analysis across all SQL databases (MySQL, PostgreSQL, SQL Server, Oracle). Focuses on SQL injection prevention, access control, code standards, and anti-pattern detection. Complements SQL optimization prompt for complete development coverage.

24時間の導入数
437
GitHub Stars
4.1万
更新日
11月20日