write-docs-cn

Write and organize project documentation by separating tutorials from reference material.

96|8|Updated Aug 13, 2026
One-click install
npx skills add https://github.com/pingfanfan/hello-dsh --skill write-docs-cn-pingfanfan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-docs-cn
Source: https://github.com/pingfanfan/hello-dsh/tree/main/examples/skills/write-docs-cn
Command: npx skills add https://github.com/pingfanfan/hello-dsh --skill write-docs-cn-pingfanfan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Project documentation often fails because tutorials and reference material get mixed together, READMEs grow without bound, and docs drift out of sync with the code. This Skill provides a decision framework for classifying, placing, structuring, and maintaining project documentation in Chinese. ## Core Features & Use Cases - Tutorial vs. Reference Classification: Decide whether a document should be a sequential tutorial with verifiable steps or a randomly accessible reference organized by topic. - Placement and Structure Rules: Keep each README scoped to its own module, push details down to the layer that owns them, and structure READMEs so the first screen answers relevance and the second gets users running. - Writing and Maintenance Guidelines: Write verifiable step-by-step tutorials, self-contained reference entries, meaningful code comments, and keep docs synchronized with code changes in the same commit. - Use Case: When asked to write a README for a new module, the Skill first determines the audience's reading mode, then produces a structure with a one-line summary, quick start, common usage scenarios, and links to deeper docs. ## Quick Start Use the write-docs-cn skill to write a README for my new module, deciding first whether it should be a tutorial or a reference document.

Frequently Asked Questions about write-docs-cn

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

FAQPage Schema
How do I write a good project README?▼

Start with a one-line summary of what the project is, then provide the shortest executable quick start path, followed by two or three common usage scenarios and links to detailed docs. The first screen must let readers judge relevance, and the second must let them run it.

What is the difference between a tutorial and reference documentation?▼

A tutorial walks readers through a complete task in sequence with a clear finish line and verifiable steps. A reference is organized by topic for random access, with each entry self-contained and including defaults, value ranges, and error cases.

How do I decide where documentation content belongs?▼

Ask whose detail the content is. Implementation details of a submodule belong in that submodule's docs, while the parent level keeps only a one-sentence summary and a link. This rule prevents README files from growing without bound.

How do I keep documentation in sync with code changes?▼

Update the documentation in the same commit that changes the behavior, never separately. Periodically verify that commands and outputs in docs still work, ideally through automation, since outdated docs waste more time than missing docs.

What should code comments contain versus documentation?▼

Comments should capture non-obvious contracts, the reasoning behind design choices, and external constraints like protocol-derived constants. They should not restate what the code does, record change history, or narrate the author's thought process.