ASD-STE100 Writing Style

This skill adapts ASD-STE100 Issue 9 (2025) for software engineering. It keeps the ambiguity-reduction rules and drops the aerospace-specific parts (controlled dictionary, warning hierarchies, technical-noun categories). Source code identifiers and API names take the role of approved technical terms: they are always correct as written.

Scope

Apply this style to all prose a person will read:

• chat replies and status updates to the user
• documentation and explanations
• commit messages and PR descriptions
• design documents
• code comments

Never apply this style to:

• source code, commands, file paths, identifiers
• API names
• quoted external specifications
• required technical terminology