doc-writer

Create bilingual VitePress documentation pages verified against Relax source code.

71|Updated May 9, 2026
One-click install
npx skills add https://github.com/DeepExperience/HyperEyes --skill doc-writer-deepexperience
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-writer
Source: https://github.com/DeepExperience/HyperEyes/tree/main/RL/relax-hypereyes/Relax/skills/doc-writer
Command: npx skills add https://github.com/DeepExperience/HyperEyes --skill doc-writer-deepexperience

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents inaccurate or incomplete project documentation by enforcing bilingual coverage, source-code verification, and consistent VitePress formatting for the Relax project.

Core Features & Use Cases

  • Bilingual Documentation Creation: Produces matching English and Chinese documentation pages with consistent structure and content coverage.
  • Code-Verified Writing Workflow: Ensures APIs, classes, functions, configuration options, CLI flags, and repository paths are checked against the actual codebase before documentation is written.
  • Use Case: When a developer adds a new Relax feature, use this Skill to create publish-ready VitePress guides, update sidebars, and maintain documentation quality without inventing unsupported functionality.

Quick Start

Use the doc-writer skill to create or update bilingual VitePress documentation for the requested Relax feature while verifying all details against the source code.

Frequently Asked Questions about doc-writer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create bilingual VitePress documentation from source code?

You can create bilingual VitePress documentation by verifying project features against the source code, ensuring matching English and Chinese content, and updating sidebars to maintain consistent structure and coverage.

How does source verification work for API docs generation?

Source verification for API docs works by checking APIs, classes, functions, configuration options, and repository paths against the actual codebase before writing, preventing the inclusion of fabricated APIs or unsupported features.

What is the best way to maintain bilingual parity in project documentation?

The best way to maintain bilingual parity is to generate matching English and Chinese documentation pages simultaneously through a code-verified writing workflow, ensuring consistent structure and content coverage across both languages.

Does this documentation workflow support updating VitePress sidebars and configuration pages?

Yes, the documentation workflow supports updating VitePress guides, API references, configuration pages, and sidebar updates, applying formatting compliance to produce publish-ready bilingual documentation pages.

Why does my generated API documentation include unsupported features?

Generated API documentation includes unsupported features when source verification is bypassed; enforcing a code-verified writing workflow checks APIs, CLI flags, and repository paths against the codebase to avoid fabricated functionality.

Can I use this for generating documentation without checking the actual codebase?

No, this workflow requires source verification against the actual codebase to ensure accuracy; it is specifically designed to prevent inaccurate documentation by enforcing bilingual coverage and verification of APIs and configuration options.