export declare const WRITING_STYLE_BLOCK = "Write in plain international English, guided by the principles of ASD-STE100 Simplified Technical English, a published international standard for technical writing. This is style guidance, not a claim of ASD-STE100 compliance. Apply its useful methods: short, direct sentences; one main idea per sentence; active voice where it is clearer, passive voice when the actor is unknown or unimportant; literal wording; and one consistent term for each concept, not alternating synonyms for variety. Do not restrict wording to the ASD-STE100 controlled dictionary of approved words. Do not enforce its formal sentence-length limits. Clarity, completeness, and accuracy come first.\n\nAssume the reader may be a non-native English speaker, unfamiliar with this project, or unfamiliar with the relevant subject or industry. Give the reader the context needed to understand the content; do not rely on unstated background knowledge. Use explicit subjects. Avoid a vague pronoun such as \"it,\" \"this,\" \"that,\" or \"they\" when the intended reference may be unclear. Define an uncommon or project-specific term the first time you use it.\n\nNever remove a fact, condition, assumption, limitation, risk, or trade-off merely to shorten text. Preserve each one even while you simplify sentence structure or wording. State cause and effect explicitly. Do not require the reader to infer an important connection between two statements that you could state directly. For each important decision, state what was decided, why, what problem it solves, what changes in practice, and what limitation or trade-off remains.\n\nDo not restyle text whose exact wording must stay stable: a heading that another tool matches, a file path, an identifier, code, a command, a configuration value, a schema field name, an API name, a protocol name, or an exact quotation. Keep that text exactly as given, character for character.\n\nWhere this instruction disagrees with the skill's own statement about its audience or about how much context to give, the skill's own statement wins.\n\nWrite professional, natural prose. Do not write prose that sounds childish, robotic, or artificially simplified.";
//# sourceMappingURL=writing-style-block.d.ts.map