[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BBJ1B52X0QMJ2QVBMPJB37":3,"skill-same:01M7BBJ1B52X0QMJ2QVBMPJB37":61},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":6,"ownerDescription":45,"updatedAt":46,"install":47,"resources":60},"01M7BBJ1B52X0QMJ2QVBMPJB37","i18n-layout",null,"Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL\u002Fbidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF\u002FBOM issues surface.","5throck\u002Fai-workspace-standards","5throck","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10958964?v=4","01M73BFEH0V0VS483TW4JD49JW","01M73BFEJ5VQZJHJSFTVPAZGDM",25,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.codex\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: i18n-layout\ndescription: >\n  Text layout and encoding guidance: character encoding (UTF-8, legacy\n  Korean code pages, BOM hazards), line endings, RTL\u002Fbidi handling, and\n  script-specific font selection (Hangul focus). Use when: encoding is\n  corrupted or mojibake appears, an RTL locale must render correctly,\n  fonts must be chosen for a script, or CRLF\u002FBOM issues surface.\nversion: 1.1.2\nowner: i18n-specialist\nstatus: active\nlast_reviewed: 2026-11-13\nscope: co-work\nprerequisites: none\nmetadata:\n  type: process\n  triggers:\n    - character encoding\n    - RTL\n    - bidi\n    - font selection\n    - CRLF\n    - BOM\n---\n\n## Purpose\n\nDefines how text is encoded, ordered, and rendered across scripts. Locale configuration (the `i18n-locale-config` skill) decides *what* a locale is; formatting (the `i18n-formatting` skill) decides *how values are written*; this skill decides *how text physically lays out*: bytes, direction, and glyphs.\n\n## Character Encoding\n\n**UTF-8 is the only default.** Every file this workspace produces — source, docs, JSON, CSV — is UTF-8 unless a declared external interface demands otherwise.\n\n### Legacy Korean code pages (CP949 \u002F EUC-KR)\n\n- Windows Korean legacy content is often CP949 (a superset of EUC-KR). Opening it as UTF-8 produces mojibake; opening UTF-8 as CP949 silently double-encodes.\n- When consuming legacy Korean files, detect the code page first, convert once to UTF-8, and never round-trip back. Conversion tools may fail on characters that exist in CP949 but not EUC-KR — convert with the CP949 mapping.\n- Windows terminals default to a legacy code page; garbled Korean in console output is a terminal-encoding symptom, not a data corruption. Fix the terminal (UTF-8 code page) before touching the data.\n\n### BOM pitfalls\n\n- A UTF-8 BOM is an invisible byte sequence (`EF BB BF`) at the file head. It breaks shebang lines, JSON parsers that expect `{` as the first byte, and any content-hash or byte-diff check.\n- **Tools can materialize a BOM unintentionally**: writing the six ASCII characters that spell a BOM escape as literal text causes some editors and file APIs to decode it into a real BOM byte. After any edit involving BOM-related escapes, verify the file head with byte-level inspection, not a text viewer.\n- If a BOM must be removed, rewrite the file's first bytes programmatically — text-editor deletion can leave the invisible residue behind.\n\n### Line endings\n\n- Repositories store LF; Windows checkouts may see CRLF. Both are fine — **mixed endings within one file are not**: they break byte-level verification and make diffs noisy.\n- Keep each file uniform. When a byte-exact check exists for a file, match the ending that check expects.\n\n## RTL and BiDi\n\nArabic (`ar`) is right-to-left — constitution §4.1 requires `dir=\"rtl\"` on the root element (or `direction: rtl` in CSS) when `ar` is the active locale.\n\n### Logical vs visual ordering\n\n- **Store and exchange text in logical order** — the order a reader types and reads it. Never store visually-reordered text; reversal is the renderer's job (the Unicode bidi algorithm), not the data model's.\n- Manually reversing an RTL string breaks searching, cursor movement, and every downstream consumer. If a pipeline outputs reversed Arabic, the bug is in that pipeline.\n\n### Embedding LTR runs inside RTL text\n\nNumbers, code identifiers, and URLs inside Arabic sentences are LTR islands:\n\n- In HTML, wrap them with `\u003Cbdi>` or apply `unicode-bidi: isolate` so the bidi algorithm contains them.\n- In plain text, use the directional marks (RLM\u002FLRM) at run boundaries — sparingly; stray marks are invisible characters that pollute diffs and search.\n- Directional icons and progress affordances mirror in RTL layouts; logos, media playback controls, and clocks do not.\n\n## Script-Specific Fonts\n\n### Hangul (Korean)\n\nHangul fonts are heavy: the script has 11,172 precomposed syllable blocks, so full fonts reach multiple megabytes. This drives every practical rule:\n\n| Context | Guidance |\n|---------|----------|\n| Decks \u002F UI (per co-deck practice) | Sans-serif faces **Pretendard** and **NanumSquareNeo** are the house choices for Korean presentation material |\n| Web | Serve **Noto Sans KR** \u002F **Noto Serif KR** with unicode-range subsetting (split woff2 chunks); never ship one monolithic Korean font |\n| System fallbacks | Windows ships a default Korean sans (Malgun Gothic); macOS ships its own — declare both after the web font in the stack, then a generic sans-serif |\n| Monospace \u002F tables | Hangul is double-width in monospace contexts — never column-align Korean text with ASCII space counts; the widths will not match rendering |\n\nThe **font pipeline** (download, subsetting, theme token wiring) lives in the co-deck variant's `design` and `theme-authoring` skills — this suite holds the selection knowledge, co-deck holds the tooling. Do not duplicate font tooling here.\n\n### Shared-ideograph scripts (zh \u002F ja)\n\nChinese, Japanese, and Korean share Han ideographs but render them with **regional glyph standards**. A font localized for one region shows the wrong regional style for another (stroke shapes differ visibly). Match the font's locale to the content locale (`zh-CN` content gets a CN-standard font), and never assume one CJK font covers all three locales acceptably for native readers.\n\n### Mixed-script line height\n\nLatin and Hangul\u002FHan glyphs have different natural heights; mixed-script lines need explicit line-height (about 1.5 for Korean body text) rather than the tighter Latin default, or the Korean reads cramped.\n\n## HWP Documents\n\nHWP\u002FHWPX authoring and conversion tooling is provided by the co-work `hwp-document-processing` skill — the full pipeline (read, generate, fill, patch, lint, compare + old-vs-new amendment comparison table, render\u002Fexport, HWPX→HWP5 reverse conversion) runs through the `scripts\u002Fhwp\u002F` adapter. This suite keeps only the layout concerns: HWP content brought into this workspace still converts to UTF-8 at the boundary, regardless of which tool converts (see Legacy Korean code pages above).\n\n## Boundary\n\n- Locale IDs, collation, timezones: `i18n-locale-config`.\n- Per-locale value formatting (dates, numbers, currency): `i18n-formatting`.\n- Translating a specific file (hash sync, diff preview): the `translate` skill.\n\n\n## Context\n\nSee [docs\u002Fco-work.context.md](..\u002Fdocs\u002Fco-work.context.md) for project context and the document-production lifecycle.\n\n## When to Use\n\n- When a co-work task touches legal or legacy Korean character encodings, RTL\u002FBiDi rendering, or script-specific font selection.\n\n## Execution Steps\n\n1. **Receive dispatch** from PM with task parameters and document anchors.\n2. **Execute** the skill procedure against the artifacts named in the task scope.\n3. **Report** results to the dispatching agent with evidence links.\n\n## Output Format\n\nStructured markdown report delivered to the dispatching agent, citing document anchors where applicable.\n\n## Related Skills\n\n- Owner agent: `i18n-specialist`\n- Common skill: `i18n-layout` (templates\u002Fcommon\u002Fskills\u002Fi18n-layout\u002FSKILL.md, v1.1.1) - this co-work copy overrides only line 92.\n","## Purpose\n\nDefines how text is encoded, ordered, and rendered across scripts. Locale configuration (the `i18n-locale-config` skill) decides *what* a locale is; formatting (the `i18n-formatting` skill) decides *how values are written*; this skill decides *how text physically lays out*: bytes, direction, and glyphs.\n\n## Character Encoding\n\n**UTF-8 is the only default.** Every file this workspace produces — source, docs, JSON, CSV — is UTF-8 unless a declared external interface demands otherwise.\n\n### Legacy Korean code pages (CP949 \u002F EUC-KR)\n\n- Windows Korean legacy content is often CP949 (a superset of EUC-KR). Opening it as UTF-8 produces mojibake; opening UTF-8 as CP949 silently double-encodes.\n- When consuming legacy Korean files, detect the code page first, convert once to UTF-8, and never round-trip back. Conversion tools may fail on characters that exist in CP949 but not EUC-KR — convert with the CP949 mapping.\n- Windows terminals default to a legacy code page; garbled Korean in console output is a terminal-encoding symptom, not a data corruption. Fix the terminal (UTF-8 code page) before touching the data.\n\n### BOM pitfalls\n\n- A UTF-8 BOM is an invisible byte sequence (`EF BB BF`) at the file head. It breaks shebang lines, JSON parsers that expect `{` as the first byte, and any content-hash or byte-diff check.\n- **Tools can materialize a BOM unintentionally**: writing the six ASCII characters that spell a BOM escape as literal text causes some editors and file APIs to decode it into a real BOM byte. After any edit involving BOM-related escapes, verify the file head with byte-level inspection, not a text viewer.\n- If a BOM must be removed, rewrite the file's first bytes programmatically — text-editor deletion can leave the invisible residue behind.\n\n### Line endings\n\n- Repositories store LF; Windows checkouts may see CRLF. Both are fine — **mixed endings within one file are not**: they break byte-level verification and make diffs noisy.\n- Keep each file uniform. When a byte-exact check exists for a file, match the ending that check expects.\n\n## RTL and BiDi\n\nArabic (`ar`) is right-to-left — constitution §4.1 requires `dir=\"rtl\"` on the root element (or `direction: rtl` in CSS) when `ar` is the active locale.\n\n### Logical vs visual ordering\n\n- **Store and exchange text in logical order** — the order a reader types and reads it. Never store visually-reordered text; reversal is the renderer's job (the Unicode bidi algorithm), not the data model's.\n- Manually reversing an RTL string breaks searching, cursor movement, and every downstream consumer. If a pipeline outputs reversed Arabic, the bug is in that pipeline.\n\n### Embedding LTR runs inside RTL text\n\nNumbers, code identifiers, and URLs inside Arabic sentences are LTR islands:\n\n- In HTML, wrap them with `\u003Cbdi>` or apply `unicode-bidi: isolate` so the bidi algorithm contains them.\n- In plain text, use the directional marks (RLM\u002FLRM) at run boundaries — sparingly; stray marks are invisible characters that pollute diffs and search.\n- Directional icons and progress affordances mirror in RTL layouts; logos, media playback controls, and clocks do not.\n\n## Script-Specific Fonts\n\n### Hangul (Korean)\n\nHangul fonts are heavy: the script has 11,172 precomposed syllable blocks, so full fonts reach multiple megabytes. This drives every practical rule:\n\n| Context | Guidance |\n|---------|----------|\n| Decks \u002F UI (per co-deck practice) | Sans-serif faces **Pretendard** and **NanumSquareNeo** are the house choices for Korean presentation material |\n| Web | Serve **Noto Sans KR** \u002F **Noto Serif KR** with unicode-range subsetting (split woff2 chunks); never ship one monolithic Korean font |\n| System fallbacks | Windows ships a default Korean sans (Malgun Gothic); macOS ships its own — declare both after the web font in the stack, then a generic sans-serif |\n| Monospace \u002F tables | Hangul is double-width in monospace contexts — never column-align Korean text with ASCII space counts; the widths will not match rendering |\n\nThe **font pipeline** (download, subsetting, theme token wiring) lives in the co-deck variant's `design` and `theme-authoring` skills — this suite holds the selection knowledge, co-deck holds the tooling. Do not duplicate font tooling here.\n\n### Shared-ideograph scripts (zh \u002F ja)\n\nChinese, Japanese, and Korean share Han ideographs but render them with **regional glyph standards**. A font localized for one region shows the wrong regional style for another (stroke shapes differ visibly). Match the font's locale to the content locale (`zh-CN` content gets a CN-standard font), and never assume one CJK font covers all three locales acceptably for native readers.\n\n### Mixed-script line height\n\nLatin and Hangul\u002FHan glyphs have different natural heights; mixed-script lines need explicit line-height (about 1.5 for Korean body text) rather than the tighter Latin default, or the Korean reads cramped.\n\n## HWP Documents\n\nHWP\u002FHWPX authoring and conversion tooling is provided by the co-work `hwp-document-processing` skill — the full pipeline (read, generate, fill, patch, lint, compare + old-vs-new amendment comparison table, render\u002Fexport, HWPX→HWP5 reverse conversion) runs through the `scripts\u002Fhwp\u002F` adapter. This suite keeps only the layout concerns: HWP content brought into this workspace still converts to UTF-8 at the boundary, regardless of which tool converts (see Legacy Korean code pages above).\n\n## Boundary\n\n- Locale IDs, collation, timezones: `i18n-locale-config`.\n- Per-locale value formatting (dates, numbers, currency): `i18n-formatting`.\n- Translating a specific file (hash sync, diff preview): the `translate` skill.\n\n\n## Context\n\nSee [docs\u002Fco-work.context.md](..\u002Fdocs\u002Fco-work.context.md) for project context and the document-production lifecycle.\n\n## When to Use\n\n- When a co-work task touches legal or legacy Korean character encodings, RTL\u002FBiDi rendering, or script-specific font selection.\n\n## Execution Steps\n\n1. **Receive dispatch** from PM with task parameters and document anchors.\n2. **Execute** the skill procedure against the artifacts named in the task scope.\n3. **Report** results to the dispatching agent with evidence links.\n\n## Output Format\n\nStructured markdown report delivered to the dispatching agent, citing document anchors where applicable.\n\n## Related Skills\n\n- Owner agent: `i18n-specialist`\n- Common skill: `i18n-layout` (templates\u002Fcommon\u002Fskills\u002Fi18n-layout\u002FSKILL.md, v1.1.1) - this co-work copy overrides only line 92.\n",{"name":5,"owner":23,"scope":24,"status":25,"version":26,"metadata":27,"description":36,"last_reviewed":37,"prerequisites":38},"i18n-specialist","co-work","active","1.1.2",{"type":28,"triggers":29},"process",[30,31,32,33,34,35],"character encoding","RTL","bidi","font selection","CRLF","BOM","Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL\u002Fbidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF\u002FBOM issues surface.\n",1794528000000,"none","main","698b6e0be38a5c8467796c232d1b844f6b49867e","templates\u002Fco-work\u002F.codex\u002Fskills\u002Fi18n-layout",9,"https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards","https:\u002F\u002Fgithub.com\u002F5throck","Experienced in digital transformation, enterprise IT, startup acceleration, and business strategy. Focused on building practical systems that connect technolo","2026-11-14 21:22:34",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add 5throck\u002Fai-workspace-standards --skill i18n-layout",{"tool":53,"command":54},"bunx","bunx skills add 5throck\u002Fai-workspace-standards --skill i18n-layout",{"tool":56,"command":57},"pnpm","pnpm dlx skills add 5throck\u002Fai-workspace-standards --skill i18n-layout","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.codex\u002Fskills\u002Fi18n-layout\u002FSKILL.md",true,[],[62,67,72,77,82,87],{"skillNo":63,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7BBJDYHJMGTJYSC37JVWY8S","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":68,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M7BBJ9XHAAS1AVGKZZ841VBZ","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.hermes\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":73,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M7BBJ5C3X8TKFKG5R9P9P49W","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.gemini\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":78,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7BBHX91BW2Q2R276MRX5AW3","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.claude\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":83,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M7BBHQWGXPSFRWN1PRC2NMMV","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.agents\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":93},"01M73HG1JK5J3A3AMG6WNH8V6E","discovery","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftests\u002Fprocedures-fixtures\u002Ftemplates\u002Fco-fixt\u002Fskills\u002Fdiscovery\u002FSKILL.md",[],[],"2026-11-11 15:11:14"]