agentleFS
peterbamuhigirepeterbamuhigire/proposal-skills/skills/language/language-standards/SKILL.md

language-standards

Skill8 starsChanged 14 days agoMITView on GitHub

Use when a bilingual or multilingual proposal needs French or Kiswahili sections, translation checks, or one register and terminology policy across languages; use east-african-english for English-only tone work.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use east-african-english for English-only tone and idiom work that does not need multilingual routing.

    line 24
  2. Distinctive:

    Do not translate legal, statutory, technical, or procurement terms without a verified source or qualified reviewer.

    line 25
  3. Distinctive:

    Read and search are required.

    line 49
  4. Distinctive:

    Stop when a legal, statutory, technical, or procurement term cannot be verified.

    line 69
  5. Distinctive:

    Run a consistency pass across headings, tables, repeated terms, figures, and calls to action.

    line 71

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
SKILL.md

Language Standards

Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178.

Select and enforce one declared language standard while preserving procurement meaning, proposer voice, and culturally appropriate professional register.

<!-- dual-compat-start -->

Use When

  • Draft, translate, or review proposal content in English, French, or Kiswahili.
  • Reconcile multilingual terminology, dates, numbers, courtesy, headings, or calls to action.

Do Not Use When

  • Use east-african-english for English-only tone and idiom work that does not need multilingual routing.
  • Do not translate legal, statutory, technical, or procurement terms without a verified source or qualified reviewer.

Inputs

ArtefactSource/providerRequired?Missing-input behaviour
Source text and target languageProposal lead or clientYesStop translation until both are explicit.
Approved terminology, names, and mandatory form wordingClient forms, ToR, glossary, verified sourceConditionalPreserve source wording and flag the term for review.
Proposer profile and country contextprofiles and sectorsYes for proposal draftingDo not infer voice, dialect, or institutional title.

Outputs

ArtefactConsumerAcceptance condition
Language-conformant proposal textEvaluator and proposal editorMeaning, names, figures, register, spelling, and declared language convention remain consistent.

Evidence Produced

EvidenceConsumerAcceptance condition
Language review recordProposal release ownerLanguage, locale, unresolved terminology, and reviewer-required items are recorded.

Capability Contract

Read and search are required. Editing is allowed only for authorised drafting or language correction. External translation services, network verification, publishing, certification of translation, and submission require explicit authority.

Degraded Mode

Fallback: when a qualified reviewer, approved glossary, source wording, or verification capability is unavailable, return the narrowest useful qualified translation, mark affected terminology not assessed, and do not certify accuracy.

Decision Rules

Condition or choiceActionFailure or risk avoided
English for Uganda, Kenya, Tanzania, or regional procurementUse British spelling and the East African professional registerImported US usage or unnatural tone
French for Francophone African institutionsUse formal French and preserve official programme terminologyLiteral English-to-French phrasing
Kiswahili for formal East African communicationUse standard formal Kiswahili and verify specialist termsColloquial or mixed-register output
Mandatory wording exists in the buyer's formReproduce it exactly and flag any apparent inconsistencyNon-compliant paraphrase

Workflow

  1. Identify the source language, target language, audience, country context, and mandatory wording.
  2. Select the matching section of the multilingual guide and establish approved terminology.
  3. Draft or review for meaning before polishing grammar, courtesy, spelling, dates, and numbers.
  4. Stop when a legal, statutory, technical, or procurement term cannot be verified.
  5. Recover by retaining the source term, flagging it for a qualified reviewer, or narrowing the output.
  6. Run a consistency pass across headings, tables, repeated terms, figures, and calls to action.

Quality Standards

  • Translation preserves obligation, qualification, uncertainty, price, date, and named-entity meaning.
  • Tone is formal and natural for the declared locale, without machine-translation residue or invented cultural claims.

Anti-Patterns

  • Mixing British and American spelling in one proposal. Fix: select the declared standard and run a consistency pass.
  • Translating an official programme name freely. Fix: use the buyer's published wording.
  • Using conversational Kiswahili in a formal tender. Fix: apply standard professional register and verify specialist terms.
  • Copying English sentence structure into French. Fix: recast the sentence naturally without changing its obligation.
  • Certifying a translation without a qualified reviewer. Fix: mark reviewer-dependent accuracy not assessed.

Worked Example

For a Ugandan technical proposal, write “programme”, “organisation”, and “mobilisation”, retain the client's exact project title, and format the date as “13 July 2026”. If the same bid requires a French annex, translate the narrative but preserve official acronyms and price figures exactly.

References

  • Multilingual language guide
  • English-only East African standard
  • Proposer profile router
<!-- dual-compat-end -->

Human-English overlay

Before drafting or reviewing English, load the human-English editorial standard. For proposal sections, draft from the proposal phrase bank and its tone rules (specific over superlative, the client's words in needs and goals, one idea per sentence, reassurance not boasting, forward-looking conclusions, price stated plainly). It governs reader, purpose, genre, grammar, collocation, rhythm, and proof. Preserve local terminology where it is correct; do not equate formal English with inflated or bureaucratic English.

English collocation and lexical-precision overlay

Load english-collocations-and-lexical-precision-2026-09-02.md alongside this standard. It strengthens precise word choice, natural collocations, evaluator-fit register, idiom restraint, calibrated claims, and proof.

Download now (ZIP)

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.