---
name: jehlp-technical-writing
description: "Write or revise original jehlp.net explanations, instructions, help, interface text, and mathematical exposition with ASD-STE100 Issue 9. Preserve source, translated, literary, and formal content."
---

# jehlp-technical-writing

Read the owning repository's AGENTS.md and site-theme/docs/WRITING-STYLE.md.
Locate site-theme beside the current repository, or resolve this skill's real path.
Use the writing policy for all new original technical text and substantive prose edits.

Classify original prose and protected content before the edit.
Preserve reader text, translations, quotations, names, citations, legal text, and code.
Preserve NDB fictional dialogue, story text, bestiary prose, and item descriptions.
Preserve data, formulas, formal statements, hypotheses, quantifiers, proof dependencies, and uncertainty.

Use short, complete sentences and consistent technical terms.
Give instructions in the imperative, with prerequisite conditions first.
Limit instructions to 20 words and descriptions to 25 words per sentence.
Limit a paragraph to one topic and six sentences.
Use active voice, simple verb forms, and no semicolons.
Check dictionary meanings and parts of speech when the official dictionary is available.
Retain precise mathematical and interface terms under the technical-term rules.

Edit the source of generated content. Rebuild affected pages, PDFs, exports, and indexes.
Compare protected content with the original. Run the repository's tests.
Obtain a separate technical-meaning review for mathematical proof edits.
Report actual checks and any dictionary-review limit. Do not claim unsupported complete compliance.