agentleFS
Sign inStart free
beingDurgeshbeingDurgesh/asd-ste100-simplified-technical-english-agent-skill/.cursor/rules/ste100.mdc

asd-ste100-simplified-technical-english-agent-skill / rules

Cursor rule4 starsChanged 21 days agoMITView on GitHub

ASD-STE100 Simplified Technical English

We split this ste100.mdc into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write plain English that a smart reader outside your field understands on one read.

    line 8
  2. Distinctive:

    Write or rewrite text in Simplified Technical English, STE100, or plain English

    line 15
  3. Distinctive:

    Remove jargon, slop, or AI writing from docs, prompts, or replies

    line 17
  4. Distinctive:

    Write or check error messages, runbooks, incident reports, release notes, commit messages, agent prompts, or UI copy

    line 18
  5. Distinctive:

    Use trigger phrases: "STE", "plain English", "layman terms", "explain it simply", "no jargon", "de-slop", "make this readable", "write for …

    line 20
  6. Distinctive:

    Read it before drafting or checking text.

    line 32
  7. Distinctive:

    Run the shipped linter to check text:

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 6,350 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
ste100.mdc
---
description: ASD-STE100 Simplified Technical English
globs: **/*.md
alwaysApply: false
---
# ASD-STE100 Simplified Technical English

Write plain English that a smart reader outside your field understands on
one read. The rules come from ASD-STE100, the controlled language that
aerospace uses for maintenance manuals.

## When to use

Apply this rule when the user asks to:
- Write or rewrite text in Simplified Technical English, STE100, or plain English
- Disambiguate text, or rewrite so an agent cannot misread it
- Remove jargon, slop, or AI writing from docs, prompts, or replies
- Write or check error messages, runbooks, incident reports, release notes,
  commit messages, agent prompts, or UI copy
- Use trigger phrases: "STE", "plain English", "layman terms", "explain it
  simply", "no jargon", "de-slop", "make this readable", "write for
  non-native readers", "disambiguate this", "controlled-language rewrite"

## Default mode

Plain (structural rules only). Strict mode applies when the user names
STE, ASD-STE100, or compliance.

## The full skill

The complete skill with all 53 rules lives in `skills/ste100/SKILL.md`.
Read it before drafting or checking text. The reply always stays Plain.

## Linter

Run the shipped linter to check text:

```
python3 skills/ste100/scripts/ste-lint.py --selftest
python3 skills/ste100/scripts/ste-lint.py path/to/file.md
python3 skills/ste100/evals/ste_lint.py examples --baseline 5
```

## Dictionary toolchain

The official ASD dictionary is copyrighted and not redistributed. To build
the dictionary-backed checker from your own free PDF copy:

```
pdftotext -layout -enc UTF-8 your_ste100.pdf ste.txt
python3 tools/ste-dictionary/parse_dict.py ste.txt
python3 tools/ste-dictionary/emit.py
python3 tools/ste-dictionary/ste_dict_lint.py --self-test
```

Download now (ZIP)

  • Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.

    Of the Cursor rule files we read, the 3,978 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository4 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free