Loading...
Loading...
Found 15 Skills
Write and rewrite technical documents in ASD-STE100 Simplified Technical English. Use this skill when the user asks for STE, ASD-STE100, Simplified Technical English, simplified English, controlled language, or plain technical English. Also use it for aircraft, defense, machine, or industrial maintenance procedures, work instructions, warnings, cautions, safety notices, and manuals that must be easy to translate or easy to read for non-native readers.
Write or rewrite English into ASD-STE100 Simplified Technical English and strip AI artifacts (decorative emojis, Markdown residue) from technical documentation — maintenance manuals, procedures, medical device instructions, and API docs read by non-native speakers or machine translation. Enforces approved word meanings, technical noun and verb categories, the 20/25-word sentence limits, banned verb tenses, and passive-voice restrictions. Trigger on simplified technical english, STE, ASD-STE100, controlled language, translation-ready docs, de-slop this manual. Do NOT use for marketing copy, brand voice, or narrative writing; for French text use samber/cc-skills@humaniseur-fr instead.
Make the agent speak and write in ASD-STE100 Simplified Technical English: short sentences, approved words, active voice, imperative for instructions, one idea per sentence, American spelling. Shapes every reply to the user AND every technical document, rewrite, or STE compliance check. Invoke with /speak-ste; stays on until "stop ste mode".
ASD-STE100 Simplified Technical English, and the reply shape a reader with ADHD can act on. A standing style rule, not an on-request tool. Layer 1 governs the words of every text a human reads — chat replies, docs, READMEs, commit messages, PR text, code comments, error messages, release notes, tool descriptions, task trackers, wiki pages. Layer 2 governs the order of a reply to a person — the next action first, numbered steps, real time estimates, no preamble and no closer. Neither layer touches code, identifiers, or command syntax. Load it before you write prose, and also when asked to remove "AI slop", make writing clear or plain, enforce a controlled style, or review text for STE violations. Two word modes — strict (procedures, runbooks, safety text, error messages) and STE-flavored (general prose, the default).
Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop. Use for documentation, READMEs, runbooks, procedures, error messages, release notes, incident reports, and API guides. Also use when the user says "STE", "Simplified Technical English", "ASD-STE100", "de-slop", "make this readable", "write for non-native readers", or asks for docs that translate well. Enforces the standard's 53 rules: 20/25-word sentence limits, one word one meaning, simple tenses, active voice, condition before command.
Use when an agent is asked to draft, rewrite, edit, review, polish, copyedit, simplify, humanize, or create written prose, including creative writing, essays, posts, scripts, speeches, emails, documentation, product copy, and other style-sensitive text. Apply George Orwell's six rules and ASD-STE100 Simplified Technical English as a plain-English discipline while preserving the user's intended meaning, audience, tone, and explicit constraints.
Write, rewrite, or review products, tools, features, projects, and release notes directly in a factual and functional order. Apply ASD-STE100 clear-expression principles to check subjects, actions, referents, terminology, conditions, and commitment strength. Preserve the original meaning and user-locked wording without adding marketing hooks, pain-point dramatization, or abstract packaging. Use when the user requests plain, direct writing, wants capabilities listed one by one, asks to check ambiguous wording, or requests a change to only one location. The Chinese guidance is an adaptation of the principles and does not represent official compliance certification.
Write, refactor, and organize technical documents based on readers' tasks and verifiable main threads, and handle document types, paths, filenames, frontmatter, indexes, and lifecycles in accordance with project conventions. For technical documents, protect facts, commands, paths, and identifiers in mixed Chinese-English content; follow the general principles of ASD-STE100 for English explanatory text. When users provide both a legally obtained standard PDF and a local checker, automatic auxiliary checks can be performed. This skill should be used whenever users need to add or substantially rewrite plans, investigations, analyses, research, progress updates, guides, runbooks, tutorials, reference materials, principle explanations, decisions, incidents, meeting minutes, changelogs, or specifications; it also applies to organizing docs directories and topic indexes. Do not use it for pure translation, minor text polishing, only modifying code, or verifying a single fact.
Turn any explanation, summary, or AI/agent output into the format a human can understand fastest. Picks from a ladder of formats (controlled-language writing in the style of ASD-STE100 Simplified Technical English, diagrams, interactive HTML pages, narrated explainer videos) and produces it. Use this skill whenever the user asks to explain, summarize, simplify, or "help me understand" something; asks for "STE", "ASD-STE100", "Simplified Technical English", "plain/clear/readable" writing, or "80% STE"; asks to "diagram it", "show me", "make it in HTML", "make an explainer", or a "3Blue1Brown / 3b1b style video"; or needs to review, audit, or oversee what an LLM or agent produced (diffs, logs, long reports, research output). Use it even when the user does not name a format but the content is complex enough that plain prose would be hard to read.
Stop. That last message did not land — re-pitch it.
Wait. I didn't understand the previous message—please re-explain it.
Hold on. The previous message wasn't clear enough—please rephrase it.