Tightens design docs, RFCs, and tech specs while preserving rationale and structure.
npx skills add https://github.com/yang-l/configs --skill design-doc-yang-l
Please help me install this Agent Skill. Skill: design-doc Source: https://github.com/yang-l/configs/tree/main/.claude/skills/design-doc Command: npx skills add https://github.com/yang-l/configs --skill design-doc-yang-l
High-intent search queries and answers about installing and using this skill.
State the doc's aim in one sentence, then cut only restatement and meta-commentary while keeping every distinct rationale, caveat, and justification. Tier each candidate cut by risk: clean redundancy is applied, framing-only changes are flagged, and anything touching rationale is discarded.
Use exact verbatim old-to-new edits with unique-match find/replace plus an invariant and structure check instead of freehand rewriting. This keeps headings, anchors, intra-doc links, code blocks, and tables stable so reviewer comments stay attached.
No. Runbooks and how-to guides are explicitly out of scope because they carry procedure rather than design rationale. The Skill links out to runbooks for the how while the design doc keeps the what and why.
It supports design docs, RFCs, tech specs, architecture proposals, one-pagers, and design proposals. It skips general prose, marketing copy, and procedural guides that contain no design rationale.
The Skill says so and stops rather than inventing churn. Its rules require honesty about the ceiling: if no safe cuts remain, no edits are made.
lemieuxGuide one-at-a-time dialogue to define problems and generate structured ideation notes for RFC drafting.
l3ochoCoordinate RFC lifecycle management from proposal through implementation using a central RFC-Index.
Anders-planckStandardize technical documentation creation, review, and publishing with templates and validation.
NVIDIADrafts OpenShell RFC proposals following the repository RFC template and process.
