Locale typography
Skill sebastian-software/skills.sebastian-software.com/skills/locale-typography
Practice-built skills that give AI agents practical judgment for product, web, engineering, delivery, go-to-market, communication, and compliance work.
npx -y skills add sebastian-software/skills.sebastian-software.com --skill locale-typographyAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Apply and review locale-appropriate typography in visible prose for German, English, French, Dutch, Luxembourgish, European Spanish (es-ES), Italian, Danish, Norwegian, Swedish, Polish, Czech, and Croatian. Use when writing, editing, localizing, proofreading, or implementing text in Markdown, HTML, JSX, templates, UI copy, documents, or print layouts where quotation marks, punctuation spacing, dashes, apostrophes, non-breaking spaces, numbers, dates, currency, or hyphenation must match a supported language and region.
SKILL.md
3.4 KB, as published. Nobody here has run it
Locale Typography
Produce typography that belongs to the reader's locale without turning the task into a grammar, translation, or house-style rewrite.
Workflow
- Determine the locale from an explicit locale tag, the document's
lang, product configuration, or the stated audience. Never infer one language from a multilingual country alone. - Preserve an established house style when it intentionally differs from the locale default. Preserve punctuation inside verbatim quotations unless the user asks to normalize it.
- Read Shared rules and the relevant row in the locale matrix.
- Read only the matching language profile listed below. Load more than one profile only for mixed-language content.
- For web or application code, also read implementation. Delegate dynamic numbers, units, currency, dates, times, lists, and plurals to locale-aware APIs.
- Apply changes only to visible prose. Do not alter code, identifiers, URLs, file paths, commands, data keys, attribute values, or copy-paste literals.
- Review nested quotations, punctuation adjacency, line-breaking hazards, and locale tags before finishing.
If the locale remains ambiguous and the choice would visibly change the result, ask for it. For low-risk work, state the assumed locale briefly and continue.
Language profiles
- German:
de-DE,de-AT,de-CH,de-BE,de-LU - English:
en-US,en-GB,en-CA - French:
fr-FR,fr-CA,fr-CH,fr-BE,fr-LU - Dutch:
nl-NL,nl-BE - Luxembourgish:
lb-LU - Spanish:
es-ES - Italian:
it-IT,it-CH - Danish:
da-DK - Norwegian:
nb-NO,nn-NO - Swedish:
sv-SE - Polish:
pl-PL - Czech:
cs-CZ - Croatian:
hr-HR
Routing Boundaries
- Correct typography and locale-sensitive presentation, not spelling, grammar, translation, tone, or general content style unless requested.
- Encode durable rules and frequent error cases, not a complete national style manual.
- Treat locale defaults as defaults, not universal law. Product terminology, legal requirements, quoted source material, and an explicit house style win.
- Do not hand-format dynamic locale data. Use
Intl, ICU, CLDR-backed libraries, or the platform equivalent and test the exact runtime. - Do not insert manual soft hyphens throughout prose. Prefer correct language metadata and automatic hyphenation; add discretionary breaks only for known, reviewed exceptions.