dstack-writing

Plugin dstack-writing from marketplace dstack in gosuda/dalcom-skills. Commands read from the repo's manifest — 3 days ago.

Skills (14)

• articulate

  Use when the user knows what they mean but cannot express it completely or clearly. Not for discovery, ideation, or style-only editing: use unslop for style.

• copywriting

  Use when asked to write or fix product/marketing copy, landing pages, UI strings, brand voice, AI tells, an end-of-article CTA, or a hook/lede. Not for whole articles.

• docs-update

  Use when documentation has drifted from code changes and the user asks to synchronize it. Delivers the fixes as local commits or as a reviewable PR after preview approval. Not for ADRs, architectural rationale, or writing an isolated document (use docs-writing).

• docs-writing

  Use when asked to write, restructure, or audit documentation with Diataxis types, or to draft a feature docs page or diagram source. Not for ADRs or architectural rationale.

• good-readme

  Use when the user asks to create, rewrite, review, or polish an open-source README. Produces one evidence-backed README.md in a fixed section order and checks it with five gates. Not for remote, credential, publish, deploy, or irreversible changes.

• humaniseur-fr

  Use when the user supplies French text that reads like AI output and asks to naturalize it. Rewrites hollow formulas, stacked connectors, systematic hedging, heavy nominalization, and unintegrated anglicisms while keeping register and meaning. French only; not for English (use humanizer-plain-englis

• humanizer-korean-plain

  Use when Korean prose reads as machine-generated (기계 문체), machine-translated (번역투), or bureaucratic (행정 문체) and must be rewritten as plain, natural Korean without changing its meaning. Covers rewriting, drafting from notes, and reviewing notices, emails, READMEs, and explanatory text. Not for contro

• humanizer-korean-ste

  Use when Korean technical documents such as runbooks, procedures, manuals, or operating guides (절차서, 운영 지침, 매뉴얼, 장애 대응 문서) need controlled wording: one action per step, conditions before actions, unified terms, and warnings placed before risky steps. Unofficial Korean profile inspired by ASD-STE100.

• humanizer-plain-english

  Use when asked to make English plain, clear, natural, and readable while keeping its meaning and voice. Not for ASD-STE100 controlled-language work: use humanizer-simple-english-asd-ste100. Not for stripping AI tells from otherwise clear prose: use unslop. Not for Korean or French: use humanizer-kor

• humanizer-simple-english-asd-ste100

  Use when asked to rewrite technical English toward ASD-STE100 Simplified Technical English: short, unambiguous sentences, one instruction per step, consistent terms, and AI-style padding removed. An STE-inspired pass, not certification. English only; not for general readability (use humanizer-plain-

• proof

  Use when asked to publish, read, comment on, suggest to, or pull a Proof collaborative markdown document. Not for proofreading, math proofs, or test evidence.

• reorder

  Use when asked to reorder a drifted listing under one stated principle, moving items only and rewording nothing. Not for deliberately ranked listings.

• rewrite-clean-v0

  Use when a document or file has been edited piecemeal and reads as sediment. Not for re-deriving a code subsystem contract: use breaking-driven.

• rhythmic-taste

  Use when the user says "give this rhythm", "vary the structure", or "the sections all read the same". Not for judging an artifact''s overall taste: use taste.

Similar plugins