YunYouJun/valaxy

# doc-i18n: Bilingual Documentation Translation Skill

## Purpose

Translate, compare, and synchronize bilingual (Chinese / English) Markdown documentation in path-based i18n projects. Ensure structural alignment, content consistency, and adherence to project-specific conventions.

## When to Use

- Translating a documentation file from one language to another
- Comparing two language versions for content drift or missing sections
- Checking translation coverage across the documentation tree
- Fixing heading IDs, internal links, or container syntax after translation
- Creating a new translation file from an existing source

# Valaxy

Next-generation static blog framework: Vue 3 + Vite + UnoCSS + file-based routing + markdown-it.

## Quick Reference

```bash
pnpm create valaxy          # scaffold new site
pnpm i                      # MUST use pnpm
pnpm dev                    # dev server at localhost:4859
pnpm build                  # SSG build to dist/
```

**Two config files:**

# Valaxy theme authoring

Turn the user's visual direction into a source-distributed theme and a working demo. Read [the theme contract](references/theme-contract.md) before changing rendering or package entrypoints. Read [the AK UI recipe](references/ak-ui.md) only when the user chooses AK UI or an Arknights-inspired theme.

## Skill and brief have different roles

This Skill supplies reusable framework knowledge and the development/verification workflow. The user's brief supplies this task's theme name, audience, visual direction, required pages and constraints. A brief generated by the docs is ordinary task input: preserve its choices, without treating its preset as a mandatory theme architecture. Do not ask the user for a second, full engineering prompt when this Skill is available.

For a new theme, establish the package/demo baseline and implement the reading experience. For an existing theme, inspect the requested change and preserve unrelated behavior, package identity and content. Do not re-run initialization or regenerate the whole theme for an iteration. Scale validation to what changed: style edits need affected-page checks; rendering, dependencies or exports need the corresponding build/package checks.

## Establish the baseline

- Inspect the current workspace, applicable AGENTS.md, package scripts, installed Valaxy version and exported types. Adapt an existing theme when that is the request.
- For a new independent theme, use https://github.com/valaxyjs/valaxy-theme-starter in a new directory. Its `theme/` package and `demo/` consumer are the starting point. If `theme:init` exists, run `pnpm theme:init <name>` inside the new workspace, adding `--owner <owner>` only when the repository owner is known; otherwise update package references and `theme` configuration together. Run `pnpm install` after renaming.