localisation skillA
localisation is agent-read markdown (skill) from vmobifystudio/app-dev-team: Use when the product ships in more than one locale, or when a string, date, number, currency or layout could differ by region — by ux-architect when the locale set changes navigation, by privacy-reviewer when region determines obligation, and by any IC writing a user-visible string. Triggers on the first string, not on the first translation..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Localisation Localisation is an architecture decision taken at the first string, and a translation task only at the end. Teams that reverse the order pay for it twice. Where a platform skill exists, use it: `axiom-localization` on Apple platforms. **External and optional** — missing → follow this file, never file its absence as a defect. ## Do this from the first ticket, in every locale count including one - **Every user-visible string is a key in the catalogue.** No string literal in a view, ever. This is cheap now and a full re-read of the codebase later. - **Never concatenate a sentence from fragments.** Word order differs by language. Use one parameterised string per sentence. - **Plurals use the platform's plural rules**, not `if count == 1`. Several languages have more than two plural forms and `1 items` is the cheapest possible way to look unfinished. - **Dates, times, numbers, currencies and units go through the locale-aware formatter.** A hand-formatted date is wrong in most of the world, silently. - **Never sort or compare user-facing text with byte comparison.** Use the locale-aware collator. ## Layout …
Read the whole file at its exact version.
How to install
mdr add vmobifystudio/app-dev-team/localisation@git:20260729.071181emdr add vmobifystudio/app-dev-team/localisation@sha256:1837077323c30320Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_onk3nupdf2hstn4c)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2633 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
vmobifystudio/app-dev-team · 4 stars · license MIT · pushed 2026-09-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_onk3nupdf2hstn4c GET https://markdownregistry.com/api/v1/resolve?ref=vmobifystudio/app-dev-team/localisation GET https://markdownregistry.com/api/v1/blob/1837077323c303205d039c23f51ce352f6033458cf1d2bac8e8fc91e0b649c1b
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.