Translate Skill

Use this skill to translate upstream mattpocock/skills content into Simplified Chinese for vinvcn/mattpocock-skills-zh-CN.

This skill is for content localization, not Git synchronization.

Operating principle

Translate user-facing English prose into natural Simplified Chinese while preserving all behavior-critical content exactly.

The target repo is an independent Simplified Chinese localized edition. It should receive translated content, not upstream repository metadata.

What to translate

Translate natural-language prose, including:

README explanations
skill instructions
skill descriptions
agent-facing guidance
maintainer-facing guidance
docs prose
examples that are written as prose

What to preserve exactly

Do not translate or rewrite:

directory names
skill names
slash commands
CLI commands
code blocks
inline code
file paths
package names
tool identifiers
API identifiers
environment variable names
frontmatter keys
JSON/YAML/TOML keys
Markdown link URLs
behavior-critical labels

Preserve Markdown structure, heading levels, list nesting, tables, link targets, relative paths, and code fences.

Repository-path localization

When translating user-facing installation examples, replace the upstream repo path:

mattpocock/skills

with the localized repo path:

vinvcn/mattpocock-skills-zh-CN

Only make this replacement where the command or prose is telling users how to install or use the localized repo.

Do not remove attribution to the upstream project.

Frontmatter rules

Preserve frontmatter keys exactly.

For frontmatter values:

• Keep name values unchanged.
• Keep identifiers, commands, paths, package names, URLs, and tool names unchanged.
• Translate description only when it is natural-language prose.
• Flag ambiguous values rather than guessing.

Translation style

Use Simplified Chinese that is:

natural
developer-friendly
concise
accurate
consistent with existing repo tone

Keep common engineering terms in English when the English term is standard among developers or when translating it would reduce clarity.

Workflow for a single file

When translating one file:

1. Identify the file path and file type.
2. Classify the file as translatable prose, mixed content, config/metadata, or non-translatable.
3. Protect behavior-critical spans before translation.
4. Translate only natural-language prose.
5. Restore protected spans exactly.
6. Check that commands, code blocks, paths, URLs, identifiers, and frontmatter keys are unchanged.
7. Check that localized install commands use vinvcn/mattpocock-skills-zh-CN.
8. Return the translated file content or a patch, plus any review flags.

Workflow for a repo refresh

When refreshing from upstream:

1. Treat upstream as a content source, not as Git history.
2. Identify new, changed, and removed content files.
3. Translate new and changed prose-bearing files.
4. Copy or preserve non-translatable support files only when they are in scope.
5. Preserve the localized repo’s README positioning and install path.
6. Add a concise entry to the README sync log.
7. Flag ambiguous files, removed files, or risky transformations for maintainer review.
8. Summarize translated files, copied files, removed files, skipped files, and review flags.

README sync log

Each upstream refresh should update the top-level README.md sync log with one short entry.

The entry should include:

• the refresh date in YYYY-MM-DD format
• the upstream source revision, usually mattpocock/skills@<short-sha>
• the local sync commit, if it already exists; otherwise use a short pending note and replace it after commit
• a one-sentence description of the visible content change

Keep this record concise. Do not move the detailed translation workflow into the README; link to this skill instead.

Example:

- 2026-05-09: Synced upstream `mattpocock/skills@733d312`, local commit `c9fe120`. Added Chinese translations for `prototype` and `in-progress` content, and refreshed public skill indexes.

Required output format for review

When reviewing a translation refresh, provide:

Changed files:
- ...

Translated files:
- ...

Copied or preserved files:
- ...

Removed or stale files:
- ...

Review flags:
- ...

README sync log:
- ...

Invariant checks:
- install commands point to vinvcn/mattpocock-skills-zh-CN
- code blocks preserved
- frontmatter keys preserved
- paths and identifiers preserved
- Markdown structure preserved

Fail-closed rule

When unsure whether text is behavior-critical, preserve it and flag it.

Do not silently rewrite anything that could affect installation, skill discovery, command execution, file references, API calls, tool use, or agent behavior.