language-standards

name	language-standards
description	Language and tone standards for all written content across 3 languages — English (British, East African), French (Francophone African), and Kiswahili (East African standard). Enforces authentic, culturally appropriate, professional communication in each language. Apply throughout all content generation steps.

Language Standards

Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, [phone].

Use when

• The task matches this domain: Language and tone standards for all written content across 3 languages — English (British, East African), French (Francophone African), and Kiswahili (East African standard). Enforces authentic, culturally appropriate, professional communication in each language. Apply throughout all content generation steps.
• The work needs a quality gate or standard applied across other outputs.

Do not use when

• The task is unrelated to this standard or quality lens.
• A more specific execution skill should own the work instead.

Required inputs

• The content, interface, or artifact being reviewed or improved.
• Any brand, audience, regional, or conversion context that affects the judgment.

Workflow

1. Read the artifact and the decision context before applying rules.
2. Use only the parts of the preserved guidance that matter to the current task.
3. Review or revise the work using this skill as a focused quality lens.
4. Return actionable changes or acceptance criteria instead of abstract theory.

Quality standards

• Recommendations must be concrete enough to apply immediately.
• Changes should improve consistency, usability, or credibility without flattening the brand.
• The standard should support downstream implementation rather than slow it down.

Anti-patterns

• Do not apply every rule mechanically when only a subset is relevant.
• Do not give generic critique with no change implications.
• Do not override project reality with taste-based preferences alone.

Outputs

• Revisions, review findings, acceptance criteria, or quality guidance tied to the artifact under review.

References

• Start with references/legacy-guidance.md when you need the preserved detailed instructions from the previous skill version.
• Read only the specific files under references/ that match the current task instead of loading the whole directory.
• This skill has no bundled scripts by default; keep execution focused on the documented workflow and any existing project files.

Notes

• Treat this SKILL.md as the portable execution layer for both Codex and Codex.
• Preserve existing project behavior unless the current task explicitly requires a change.