← ClaudeAtlas

dsh-doclisted

Create, restructure, review, audit, or migrate DeepSeek Harness Markdown documentation, package READMEs, and the documentation website using audience-first hierarchy, kind-mapped YAML metadata, bilingual line alignment, summary/contents navigation, progressive user-to-developer detail, executed-operation fact-checking, and repository validation. Use for new or revised DSH docs, docs-tree organization, documentation-quality audits and budgets, website page publishing, and bilingual documentation structure changes.
SOYL-AI/soyl-skills-hub · ★ 0 · Data & Documents · score 72
Install: claude install-skill SOYL-AI/soyl-skills-hub
# DeepSeek Harness documentation ## Summary The DeepSeek Harness documentation standard: make every page searchable, newcomer-readable, and exact enough for agents and maintainers, and keep the documentation website a tested projection of repository Markdown. Apply repository `AGENTS.md` files and executed gates first, then this workflow for kind-mapped metadata, progressive detail, line-aligned bilingual pages, corpus audits, and website publication. Preserve one owner per fact: source, tests, generated catalogs, package READMEs, guides, Agent Notes, and scratch each keep their own kind of truth. The `session-persistence-jsonl` README pair is the reference example of the format. ## Table of Contents - [Workflow](#workflow) - [Fact-check procedure: test, do not assume](#fact-check-procedure-test-do-not-assume) - [Kind system and templates](#kind-system-and-templates) - [Voice rules](#voice-rules) - [Quality criteria](#quality-criteria) - [Audit the corpus](#audit-the-corpus) - [Wordcount budgets](#wordcount-budgets) - [Website publication](#website-publication) - [Detailed references](#detailed-references) - [Validation](#validation) - [Dev Note](#dev-note) ## Workflow Follow this sequence for each requested scope. Keep the common reader path brief, but do not delete failures, ownership, limitations, or other required contracts merely to reduce words. 1. Read root and more-specific `AGENTS.md`, [the documentation standard](../../../docs/AGENTS.md), the target page, its