i18n-language-standards
Skill12 starsChanged 6 days agoMITView on GitHub
Enforce ASD-STE100 (English) and clear Korean UI language standards across LibrAgent. Audits UI text, Settings descriptions, and i18n locales for prohibited engineering jargon, internal code identifiers (browser="userChrome", awaitAgent, pollProcess, createSession), passive translations, and ensures terminology parity across all 8 supported languages. Triggers on: "언어 규약", "language standards", "i18n standards", "ASD-STE100", "i18n audit", "i18n 검증", "언어 규약 검사", "layman-friendly UI text", "i18n-language-standards".
In this repository51 other files it gives its agents.
- agents.mdAGENTS.md
- .agents/skills/react-best-practices/AGENTS.mdAGENTS.md
- .agents/skills/react-native-skills/AGENTS.mdAGENTS.md
- .agents/skills/react-view-transitions/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- agent-initSkill
- agy-delegateSkill
- audit-docsSkill
- code-audit-expertSkill
- computer-diagnosisSkill
- create-builtin-toolSkill
- create-prSkill
- critique-builtin-toolSkill
- doc-auditorSkill
- docxSkill
- extract-log-debugSkill
- feature-refactor-proposalSkill
- gatekeeper-loopSkill
- harbor-harness-improvement-loopSkill
- harness-eval-loopSkill
- jobs-trace-analyzerSkill
- lean-builtin-tool-auditorSkill
- libragent-qualitySkill
- libr-delegateSkill
- libr-tool-e2e-harness-loopSkill
- modular-large-file-refactorSkill
- performance-auditSkill
- pptxSkill
- producer-loopSkill
- vercel-react-best-practicesSkill
- vercel-react-native-skillsSkill
- vercel-react-view-transitionsSkill
- readme-showcase-syncSkill
- refactor-builtin-toolSkill
- release-head-self-e2eSkill
- release-managerSkill
- review-local-changesSkill
- review-pr-commentsSkill
- science-searchSkill
- setup-wizardSkill
- skill-creatorSkill
- soul-awakeningSkill
- sqlite-analyzerSkill
- sync-pending-approvalsSkill
- tool-creatorSkill
- trace-analyzerSkill
- trace-eval-loopSkill
- vitepress-doc-syncSkill
- worker-loopSkill
- x-cliSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
- Distinctive: line 19
Never expose code syntax or internal function names in user-facing text.
- Very specific: line 31
All settings keys and UI strings must maintain semantic and structural parity across en, ko, ja, zh, de, fr, es, and pt.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
i18n Language Standards & Enforcement
This skill defines, audits, and enforces user-facing language standards across LibrAgent. It ensures that UI labels, settings descriptions, tool documentation, and i18n locales adhere to ASD-STE100 for English and Clear Korean UI Standards for Korean, while maintaining rigorous parity across all 8 supported languages (en, ko, ja, zh, de, fr, es, pt).
1. Core Principles
- No Internal Code Identifiers in UI:
- Never expose code syntax or internal function names in user-facing text.
- Prohibited examples:
browser="userChrome",browser="sidecar",createSession,awaitAgent,pollProcess.
- Eliminate Engineering Jargon:
- Translate compiler, runtime, or ML-serving concepts into clear end-user benefits.
- Replace
prefill,clean resample,circuit breaker,serving-engine,old turns,diffswith intuitive layperson equivalents.
- ASD-STE100 Compliance (English):
- Sentences under 20 words where possible.
- Active voice, clear imperatives, one word for one meaning.
- Clear Korean Standards (한국어):
- 번역투 및 피동형(
~되어지다) 배제, 능동형 단문 구성. - 불필요한 한자어나 외래어(
거버넌스) 대신 직관적인 표준 용어 사용.
- 번역투 및 피동형(
- Multilingual Parity (8 Locales):
- All settings keys and UI strings must maintain semantic and structural parity across
en,ko,ja,zh,de,fr,es, andpt.
- All settings keys and UI strings must maintain semantic and structural parity across
2. Automated Validation Workflow
To check compliance across all locale files and Settings components, execute the bundled validator:
node .agents/skills/i18n-language-standards/scripts/validate_i18n_standards.cjsThe script verifies:
- Absence of forbidden internal identifiers in
src/locales/andsrc/features/settings/. - Absence of flagged engineering jargon.
- JSON syntax validity and key parity against
en/common.json.
3. Reference Guides
Consult the reference documents for specific translation rules:
- ASD-STE100 English Guidelines: Active voice, controlled vocabulary, brevity rules.
- Clear Korean UI Guide: 한국어 UI 표준 어휘, 번역투 제거 및 능동형 문체 규약.
- Multilingual Translation Guide: Rules for
ja,zh,de,fr,es, andpt.
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
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.

