cn-docs-writer/
  SKILL.md

cn-docs-writer/
  SKILL.md
  references/
    page-checklist.md
  scripts/
    check_headings.py
  assets/
    template.md

cn-docs-writer/
  SKILL.md
  references/
    page-checklist.md

---
name: cn-docs-writer
description: Use when writing or editing Chinese tutorial documentation, especially Markdown or VitePress pages that need clear structure, beginner-friendly wording, navigation updates, and build verification.
---

# 中文教程写作

## 工作流

1. 先确认本次页面解决的一个主要问题。
2. 用简体中文写作，先给结论，再给步骤。
3. 命令、配置、排错分开写，不把大段命令混在正文里。
4. 示例 key 统一使用 `sk-your-api-key`，不要写真实密钥。
5. 新增页面后检查导航、侧边栏、README、来源页是否需要同步。
6. 完成前运行项目规定的构建命令。

## 页面结构

- 顶部用一句话说明页面用途。
- 加一个“本页速读”块，包含解决什么、适合谁、预计耗时。
- 每页只解决一个主要问题。
- 涉及外部产品、模型、价格、API 协议时，优先核对官方文档。

## 何时读取参考资料

如果要新增页面或大改结构，读取 `references/page-checklist.md`。

# 页面检查清单

- 标题是否能说明读者会解决什么问题
- 是否有“本页速读”
- 是否把命令、配置、排错分开
- 是否避免真实 API key、token、cookie
- 是否同步导航或索引
- 是否运行构建验证

focused-code-review/
  SKILL.md

---
name: focused-code-review
description: Use when reviewing code changes for bugs, regressions, missing tests, security risks, data loss risks, or maintainability issues. Prioritize actionable findings with file and line references.
---

# Focused Code Review

## Review order

1. Read the user request and changed files before judging the diff.
2. Prioritize correctness, security, data loss, migrations, and missing tests.
3. Findings come first. Summaries are secondary.
4. Each finding should include file path, line reference, severity, and why it matters.
5. If no issues are found, say so clearly and mention residual test risk.

## Output format

- Start with findings ordered by severity.
- Use concise bullets.
- Add open questions only when they affect correctness.
- End with a short verification note if tests were run or could not be run.

## Do not

- Do not rewrite unrelated code.
- Do not spend review space on style-only suggestions unless they hide a real bug.
- Do not expose secrets from `.env`, logs, or private config files.

link-checker/
  SKILL.md
  scripts/
    check_links.py

---
name: link-checker
description: Use when checking Markdown documentation links before publishing.
---

# Link Checker

## Workflow

1. Inspect changed Markdown files.
2. Run `python scripts/check_links.py <file>` for edited pages.
3. Report broken local links first, then external links that need manual checking.
4. Do not modify generated site output.