dsh-studio: Skill for Claude Code

Applying the DeepSeek Harness Documentation Standard

The documentation rules live in docs/AGENTS.md. This workflow covers placement, corpus audits, budgets, and validation across Markdown, JSDoc, and code comments. It is guidance, not a script; use dsh-prose-standard for required coverage and editorial judgment, and never treat length alone as a defect.

Sources of truth (read, don't re-summarize)

• docs/AGENTS.md — hierarchy, tutorial/reference forms, taxonomy, budgets, and slop checklist.
• .agents/notes/README.md — when a decision earns an Agent Note, how to file it, and what goes inside one (the header block, per-lifecycle skeleton, and Alternatives-considered mandate, gated by verify-agent-note-format); docs/postmortem/README.md — when an incident earns a postmortem.
• docs/i18n/README.md — the bilingual pairing rules; editing either side of a pair obligates the counterpart in the same change.
• Root AGENTS.md — the standing orders whose budget discipline this skill protects.
• Archived Agent Notes — frozen historical snapshots excluded from editorial maintenance and evolving documentation gates.

Review structure before prose

Apply the standard's authoring order to every human-facing document in scope. Do not apply this structural pass to Agent Notes. Classify a postmortem as a reference scoped to one incident; preserve its required chronological evidence without treating chronology as a teaching sequence.

1. Locate the document in the repository and navigation trees. State its own subject and identify its direct children.
2. Set the permitted level of detail. Keep full detail about the document's subject, summarize direct children by purpose, responsibility, and high-level behavior, and move deeper explanations to their owning descendants with links. Treat test infrastructure as descendant-owned unless it is the document's subject.
3. Classify the document from its intended use, not its path or title. A tutorial must lead through ordered work to an observable outcome; a reference must support lookup within an explicit scope without requiring sequential reading.
4. For a tutorial, privately classify the starting reader and concepts as beginner, intermediate, or advanced. Trace each concept to its prerequisites, reorder premature material, and move optional advanced detail to a later tutorial or reference.
5. Split substantial mixed forms. Put a small secondary form in a clearly labeled section.