Turn any idea, plan, or codebase into a beautiful interactive diagram. An agent skill for Claude Code, Codex, and more.
HTML agent-skillsai-agentsarchitecture-diagramclaude-codeclaude-skillscodexcoding-agentsdeepseek-harnessdeveloper-toolsdiagramsdiagrams-as-codedsh-pluginflowchartllmmermaidopencodesequence-diagramsoftware-architecturesystem-designvisualization
docs(skill): scope meta.translations to Viewer chrome only
uygnoeyd0d900a389e9
diff --git a/archify.zip b/archify.zipindex 6385f975..e3c43e23 100644Binary files a/archify.zip and b/archify.zip differdiff --git a/archify/SKILL.md b/archify/SKILL.mdindex c10282cb..c39577b9 100644--- a/archify/SKILL.md+++ b/archify/SKILL.md@@ -123,6 +123,8 @@ Read `references/viewer-runtime.md` only when the user explicitly asks for Share## Localizing the Viewer UI with meta.translations+This section is about renderer-owned Viewer chrome only. Write titles, node labels, cards, and every other authored string directly in whatever language the user explicitly requested or the conversation established — Archify never machine-translates authored content or calls a translation service, before or after delivery.+**Any well-formed locale tag works, for any language — not just the ones listed below.** `en`, `zh-CN`, and `es` ship as built-in Viewer-chrome catalogs (`renderers/shared/i18n.mjs`), so those three need nothing further. Every other locale — including ones with no example on disk — is supplied as translation *data* you (the authoring agent) write into the document, not a renderer code change and not a fixed list anywhere in this repo. To localize a diagram in a language with no existing example, set `meta.locale` to its tag and write `meta.translations` yourself: an object mapping canonical message keys (see `catalogKeys()`, or any key in `examples/locales/ko.json`) to translated strings whose `{placeholder}` tokens match the English source exactly. `validate`/`render`/`deliver` report coverage to stderr (`archify: meta.translations for locale "…" covers N/519 renderer-owned messages…`); a key that is missing, unknown, or has mismatched placeholders falls back to its English string rather than breaking the render. `meta.locale` without a built-in catalog or `meta.translations` falls back entirely to English Viewer UI and `<html lang="en">`, with the same disclosure on stderr — never a half-translated page. The renderer itself never translates anything or calls a translation service; every string in `meta.translations` must already be present in the document when you call `validate`/`render`/`deliver`.`examples/locales/` carries reusable, checked-in catalogs so a diagram doesn't need retranslating from scratch every time: `examples/locales/ko.json`, `fr.json`, `pt.json`, `ja.json`, `de.json`, `it.json`, and `ru.json` are each complete (519/519 keys). `examples/locales/fr.partial.json` is a small, deliberately partial French catalog demonstrating the missing-key/coverage-report path specifically. None of these are a closed enum — they're starting points to copy or extend, and a language with no file here works exactly the same way once you write its `meta.translations`.