What problem it solves

LLM responses and technical documents often contain jargon, hedging, fragmented sentences, and unnecessary formatting that can make instructions difficult to understand. This project applies structured writing rules so agents produce clear, direct technical content in either a plain default register or a stricter ASD-STE100-oriented mode.

Key features

• Plain and strict writing modes — The default Plain mode applies the core rules to replies and documents. Strict mode adds ASD-STE100 dictionary discipline when the request names STE, ASD-STE100, or compliance, while replies remain in Plain mode.

  Source: README

• Clear chat responses — Chat answers use prose without headers, bullets, bold, or tables, begin with the answer, and avoid em-dashes, contractions, filler, and unexplained jargon.

  Source: README

• Structured technical documents — The document rules cover instructions, descriptions, conditions, tense, voice, terminology, and headings. They apply to content such as READMEs, runbooks, incident reports, error messages, and release notes.

  Source: README

• Agent and editor integration — The skill can be installed with the skills CLI or added through the Claude Code and Codex plugins. Users without skill support can paste the supplied rule block into a system prompt, AGENTS.md, or .cursorrules.

  Source: README, .claude-plugin

• Evaluation and linting tools — The repository includes committed evaluation results, a number-checking script, a word-choice linter, and an extractor that builds word lists from a user-provided Issue 9 PDF.

  Source: README, tools

Quick start

Copied verbatim from the project's README.

npx skills add AminBlg/SimpleEnglish

claude plugin marketplace add AminBlg/SimpleEnglish && claude plugin install simple-english@simple-english

codex plugin marketplace add AminBlg/SimpleEnglish
codex plugin add simple-english@simple-english

Who it may suit

This may suit developers, technical writers, and documentation teams that want agents to produce clearer instructions and technical prose. It may also suit teams working with ASD-STE100-oriented writing requirements.

Topics to discuss

• Which technical writing workflows would benefit most from plain and strict modes?

• How should the rules balance concise instructions with a writer’s natural voice?

• Which evaluation methods best measure whether technical readers can understand generated instructions correctly?

Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.

Read the original README https://github.com/AminBlg/SimpleEnglish#readme

ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.