unslop

Files (1)

• SKILL.md

SKILL.md (first lines)

# Unslop

Apply to prose you are writing or were asked to edit: documentation, reports, handoffs, specs, commit bodies, and client-facing text. Preserve meaning and the author's intended tone. Do not sweep unrelated repository text.

Exclude code, identifiers, code comments, quoted evidence, and user-authored text outside the request. Draht's prompt and skill corpus is outside this skill's scope. Keep fixed formats exact, including conventional commit subjects, `red:`/`green:`/`refactor:`, `STATUS:` lines, frontmatter, and verdict-first reports.

Lead with the concrete fact or action. Name actors, mechanisms, and evidence. Replace promotional claims, vague attribution, filler, repeated conclusions, and unnecessary jargon with specific information or remove them. Preserve established project terminology.

Use familiar words, active verbs, and stable names for the same concept. Vary sentence length when it improves readability. Use lists and headings for structure, not decoration. Keep uncertainty where the evidence requires it; editing for confidence must not turn an inference into a fact.

Match the register: technical reports need commands, results, and limits; explanatory prose can express a supported opinion and a more personal voice. Do not add artificial warmth or invented anecdotes.

## Procedures and simplified technical English

For runbooks, setup instructions, warnings, and requested STE-style text:

- Give one action per numbered step and put conditions before the action.
- Place warnings before the action they protect and explain the concrete consequence.
- Use consistent terminology and exact command/path/error text.
- Prefer short sentences; aim for 20 words in procedures and 25 in descriptions.
- Keep necessary articles and context so brevity does not make instructions ambiguous.

These are practical readability guidelines, not a claim of certified ASD-STE100 compliance. Apply the same clarity principles to German while preserving German grammar and established technical terms.

From draht-dev/draht, MIT.

More from draht-dev/draht