[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73GDMDJCB066FDCXV2NZ7MD":3,"skill-same:01M73GDMDJCB066FDCXV2NZ7MD":60},{"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":38,"commitSha":39,"skillDirectory":40,"forksCount":41,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":6,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M73GDMDJCB066FDCXV2NZ7MD","i18n-formatting",null,"Locale-specific formatting rules: date\u002Ftime notation, number and currency formatting, units of measure, Korean-scale numerals, and print paper sizes. Use when: writing dates or numbers for a specific locale, formatting currency for a market, choosing metric or imperial units, applying Korean large-number scales, or picking a paper size.","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\u002Fcommon\u002F.agents\u002Fskills\u002Fi18n-formatting\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: i18n-formatting\ndescription: >\n  Locale-specific formatting rules: date\u002Ftime notation, number and\n  currency formatting, units of measure, Korean-scale numerals, and\n  print paper sizes. Use when: writing dates or numbers for a specific\n  locale, formatting currency for a market, choosing metric or imperial\n  units, applying Korean large-number scales, or picking a paper size.\nversion: 1.0.1\nowner: i18n-specialist\nstatus: active\nlast_reviewed: 2026-08-24\nscope: common\nmetadata:\n  type: process\n  triggers:\n    - date format\n    - number format\n    - currency format\n    - unit conversion\n    - paper size\n    - korean numerals\n---\n\n## Purpose\n\nDefines how dates, times, numbers, currency, units, large-number scales, and paper sizes are written per locale. Formatting is invisible when right and credibility-damaging when wrong: a swapped date separator or a mis-scaled figure reads as a foreign document even to a reader who cannot name the rule that was broken.\n\n## Dates and Times\n\n**Interchange format**: ISO 8601 (`YYYY-MM-DD` \u002F `YYYY-MM-DDTHH:mm:ssZ`) for anything stored, exported, or exchanged between systems. Convert to locale display only at render time.\n\n**Display formats per locale** (the same date, 2026-08-24):\n\n| Locale | Rendering | Convention |\n|--------|-----------|------------|\n| `en-US` | Aug 24, 2026 | Month name, day, year; comma-separated |\n| `en-GB` | 24 Aug 2026 | Day first, no comma before year |\n| `ko` | 2026. 8. 24. | Year. month. day. with dot separators and trailing dot |\n| `ja` | 2026\u002F08\u002F24 | Slash separators, zero-padded |\n| `de` | 24.08.2026 | Day. month. year., dot separators |\n| `fr` | 24\u002F08\u002F2026 | Slash separators, day first |\n\nRules:\n\n1. **Never guess from a bare numeric date** — `08\u002F24\u002F2026` vs `24\u002F08\u002F2026` is a locale question. When the locale is unknown, use ISO 8601.\n2. **12-hour vs 24-hour**: `en-US` uses 12-hour with AM\u002FPM; `ko`, `ja`, `de`, `fr` default to 24-hour. Confirm per locale rather than per language (`en-GB` is 24-hour).\n3. Use `Intl.DateTimeFormat` with an explicit locale rather than hand-formatting.\n\n## Numbers\n\nDecimal and grouping separators are locale pairs — flipping one without the other corrupts the value.\n\n| Locale | Rendering of 1234.56 | Separators |\n|--------|----------------------|------------|\n| `en-US` | 1,234.56 | comma groups, dot decimal |\n| `ko` | 1,234.56 | comma groups, dot decimal |\n| `de` | 1.234,56 | dot groups, comma decimal |\n| `fr` | 1 234,56 | space groups, comma decimal |\n| `ja` | 1,234.56 | comma groups, dot decimal |\n\nRules:\n\n1. A German reader parses `1.234` as one thousand two hundred thirty-four, not 1.234 — the dot is a group separator.\n2. Never concatenate a formatted number into a string for another locale; use `Intl.NumberFormat` per target locale.\n3. In tables shared across locales, state the convention in the table note or use ISO-style unformatted digits.\n\n## Currency\n\n| Rule | Guidance |\n|------|----------|\n| Interchange | ISO 4217 codes (`USD`, `KRW`, `EUR`, `CHF`) — never symbols, never localized names |\n| Display | Locale convention decides symbol vs code and position |\n| Symbols | `$` (USD), `W` colloquially for KRW in English text (the won symbol itself in Korean text), EUR uses `EUR` or the euro sign per locale |\n| Position | `en-US`: `$1,234.56` (symbol first); `de`: `1.234,56 USD` (code after, non-breaking space); `fr`: `1 234,56 EUR` |\n\nRules:\n\n1. **Never convert amounts silently** — formatting changes presentation, not value. Currency conversion is a data decision, not a formatting one.\n2. Korean won has no minor unit in practice — `1,234,567 KRW`, never `.00`.\n3. Use `Intl.NumberFormat` with `style: \"currency\"` and an explicit locale; it applies symbol, position, and grouping together.\n\n## Units of Measure\n\n- **Default: metric (SI)** for all engineering, scientific, and most non-US deliverables.\n- **Imperial\u002FUS customary** applies when the audience or domain expects it: US-facing consumer material (feet, inches, pounds, Fahrenheit), some trade documentation for US partners.\n- When both audiences read one document: metric first, imperial in parentheses on first use — `30 cm (11.8 in)` — then metric alone.\n- Temperatures: `C` for metric audiences, `F` for US; never list one without the scale letter.\n- Unit conversion is arithmetic on values — keep the source unit authoritative and convert only for display, stating the conversion basis for regulated contexts.\n\n## Korean-Scale Numerals\n\nKorean counts large numbers in steps of **10,000**, not 1,000 — the man-eok-jo scale. This guidance formalizes existing co-news prose practice.\n\n| Scale unit | Power | Western equivalent | Example |\n|-----------|-------|--------------------|---------|\n| man | 10^4 | ten thousand | 3 man = 30,000 |\n| eok | 10^8 (man squared) | hundred million | 1.2 eok = 1,200,000,000 |\n| jo | 10^12 (eok × man) | trillion (short scale) | 7 jo = 7,000,000,000,000 |\n\nRules:\n\n1. **Grouping**: Korean prose groups digits by four (man steps), Western numerals by three (thousand steps). `5 eok 6,000 man` = 5,600,000,000 — do not re-group the digits without re-stating the scale word.\n2. Decimal fractions attach to the largest scale: 1.2 eok, 3.4 man — two decimal places is the news convention for eok-scale figures.\n3. When translating Korean financial prose to English, keep the exact value: state the Western equivalent (1.2 eok = 1.2 billion) rather than converting to \"1,200 million\".\n4. Won amounts: state the scale unit and the currency — \"3 man won\" (30,000 KRW) in romanized prose; the scale word never travels without its currency context.\n\n## Print Paper Sizes\n\n- **A4 (210 × 297 mm)**: default in metric-system countries including Korea, Japan, China, and Europe. Use A4 for all deliverables unless the print market dictates otherwise.\n- **US Letter (8.5 × 11 in \u002F 216 × 279 mm)**: US, Canada (mixed with A4), Mexico, and Philippines markets.\n- Choose by **where the document will be printed**, not by its language: an English deck printed in Seoul is still A4.\n- PDF export settings must match the chosen size; a Letter-sized PDF printed on A4 stock scales down and breaks margins.\n- This rule absorbs long-standing co-deck and co-export practice: deck templates default per target print market, export documentation per destination country's standard.\n\n## Boundary\n\n- Choosing the locale itself, collation, timezones: `i18n-locale-config`.\n- Encoding, fonts, RTL layout mechanics: `i18n-layout`.\n- Translating a specific file (hash sync, diff preview): the `translate` skill.\n","## Purpose\n\nDefines how dates, times, numbers, currency, units, large-number scales, and paper sizes are written per locale. Formatting is invisible when right and credibility-damaging when wrong: a swapped date separator or a mis-scaled figure reads as a foreign document even to a reader who cannot name the rule that was broken.\n\n## Dates and Times\n\n**Interchange format**: ISO 8601 (`YYYY-MM-DD` \u002F `YYYY-MM-DDTHH:mm:ssZ`) for anything stored, exported, or exchanged between systems. Convert to locale display only at render time.\n\n**Display formats per locale** (the same date, 2026-08-24):\n\n| Locale | Rendering | Convention |\n|--------|-----------|------------|\n| `en-US` | Aug 24, 2026 | Month name, day, year; comma-separated |\n| `en-GB` | 24 Aug 2026 | Day first, no comma before year |\n| `ko` | 2026. 8. 24. | Year. month. day. with dot separators and trailing dot |\n| `ja` | 2026\u002F08\u002F24 | Slash separators, zero-padded |\n| `de` | 24.08.2026 | Day. month. year., dot separators |\n| `fr` | 24\u002F08\u002F2026 | Slash separators, day first |\n\nRules:\n\n1. **Never guess from a bare numeric date** — `08\u002F24\u002F2026` vs `24\u002F08\u002F2026` is a locale question. When the locale is unknown, use ISO 8601.\n2. **12-hour vs 24-hour**: `en-US` uses 12-hour with AM\u002FPM; `ko`, `ja`, `de`, `fr` default to 24-hour. Confirm per locale rather than per language (`en-GB` is 24-hour).\n3. Use `Intl.DateTimeFormat` with an explicit locale rather than hand-formatting.\n\n## Numbers\n\nDecimal and grouping separators are locale pairs — flipping one without the other corrupts the value.\n\n| Locale | Rendering of 1234.56 | Separators |\n|--------|----------------------|------------|\n| `en-US` | 1,234.56 | comma groups, dot decimal |\n| `ko` | 1,234.56 | comma groups, dot decimal |\n| `de` | 1.234,56 | dot groups, comma decimal |\n| `fr` | 1 234,56 | space groups, comma decimal |\n| `ja` | 1,234.56 | comma groups, dot decimal |\n\nRules:\n\n1. A German reader parses `1.234` as one thousand two hundred thirty-four, not 1.234 — the dot is a group separator.\n2. Never concatenate a formatted number into a string for another locale; use `Intl.NumberFormat` per target locale.\n3. In tables shared across locales, state the convention in the table note or use ISO-style unformatted digits.\n\n## Currency\n\n| Rule | Guidance |\n|------|----------|\n| Interchange | ISO 4217 codes (`USD`, `KRW`, `EUR`, `CHF`) — never symbols, never localized names |\n| Display | Locale convention decides symbol vs code and position |\n| Symbols | `$` (USD), `W` colloquially for KRW in English text (the won symbol itself in Korean text), EUR uses `EUR` or the euro sign per locale |\n| Position | `en-US`: `$1,234.56` (symbol first); `de`: `1.234,56 USD` (code after, non-breaking space); `fr`: `1 234,56 EUR` |\n\nRules:\n\n1. **Never convert amounts silently** — formatting changes presentation, not value. Currency conversion is a data decision, not a formatting one.\n2. Korean won has no minor unit in practice — `1,234,567 KRW`, never `.00`.\n3. Use `Intl.NumberFormat` with `style: \"currency\"` and an explicit locale; it applies symbol, position, and grouping together.\n\n## Units of Measure\n\n- **Default: metric (SI)** for all engineering, scientific, and most non-US deliverables.\n- **Imperial\u002FUS customary** applies when the audience or domain expects it: US-facing consumer material (feet, inches, pounds, Fahrenheit), some trade documentation for US partners.\n- When both audiences read one document: metric first, imperial in parentheses on first use — `30 cm (11.8 in)` — then metric alone.\n- Temperatures: `C` for metric audiences, `F` for US; never list one without the scale letter.\n- Unit conversion is arithmetic on values — keep the source unit authoritative and convert only for display, stating the conversion basis for regulated contexts.\n\n## Korean-Scale Numerals\n\nKorean counts large numbers in steps of **10,000**, not 1,000 — the man-eok-jo scale. This guidance formalizes existing co-news prose practice.\n\n| Scale unit | Power | Western equivalent | Example |\n|-----------|-------|--------------------|---------|\n| man | 10^4 | ten thousand | 3 man = 30,000 |\n| eok | 10^8 (man squared) | hundred million | 1.2 eok = 1,200,000,000 |\n| jo | 10^12 (eok × man) | trillion (short scale) | 7 jo = 7,000,000,000,000 |\n\nRules:\n\n1. **Grouping**: Korean prose groups digits by four (man steps), Western numerals by three (thousand steps). `5 eok 6,000 man` = 5,600,000,000 — do not re-group the digits without re-stating the scale word.\n2. Decimal fractions attach to the largest scale: 1.2 eok, 3.4 man — two decimal places is the news convention for eok-scale figures.\n3. When translating Korean financial prose to English, keep the exact value: state the Western equivalent (1.2 eok = 1.2 billion) rather than converting to \"1,200 million\".\n4. Won amounts: state the scale unit and the currency — \"3 man won\" (30,000 KRW) in romanized prose; the scale word never travels without its currency context.\n\n## Print Paper Sizes\n\n- **A4 (210 × 297 mm)**: default in metric-system countries including Korea, Japan, China, and Europe. Use A4 for all deliverables unless the print market dictates otherwise.\n- **US Letter (8.5 × 11 in \u002F 216 × 279 mm)**: US, Canada (mixed with A4), Mexico, and Philippines markets.\n- Choose by **where the document will be printed**, not by its language: an English deck printed in Seoul is still A4.\n- PDF export settings must match the chosen size; a Letter-sized PDF printed on A4 stock scales down and breaks margins.\n- This rule absorbs long-standing co-deck and co-export practice: deck templates default per target print market, export documentation per destination country's standard.\n\n## Boundary\n\n- Choosing the locale itself, collation, timezones: `i18n-locale-config`.\n- Encoding, fonts, RTL layout mechanics: `i18n-layout`.\n- Translating a specific file (hash sync, diff preview): the `translate` skill.\n",{"name":5,"owner":23,"scope":24,"status":25,"version":26,"metadata":27,"description":36,"last_reviewed":37},"i18n-specialist","common","active","1.0.1",{"type":28,"triggers":29},"process",[30,31,32,33,34,35],"date format","number format","currency format","unit conversion","paper size","korean numerals","Locale-specific formatting rules: date\u002Ftime notation, number and currency formatting, units of measure, Korean-scale numerals, and print paper sizes. Use when: writing dates or numbers for a specific locale, formatting currency for a market, choosing metric or imperial units, applying Korean large-number scales, or picking a paper size.\n",1787529600000,"main","b57e612781a79b0e3e60878294ce59c86cc68e5d","templates\u002Fcommon\u002F.agents\u002Fskills\u002Fi18n-formatting",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":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add 5throck\u002Fai-workspace-standards --skill i18n-formatting",{"tool":52,"command":53},"bunx","bunx skills add 5throck\u002Fai-workspace-standards --skill i18n-formatting",{"tool":55,"command":56},"pnpm","pnpm dlx skills add 5throck\u002Fai-workspace-standards --skill i18n-formatting","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fcommon\u002F.agents\u002Fskills\u002Fi18n-formatting\u002FSKILL.md",true,[],[61,69,74,79,84,89],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":68},"01M7BBJDYHJMGTJYSC37JVWY8S","i18n-layout","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.","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":70,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":68},"01M7BBJ9XHAAS1AVGKZZ841VBZ","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.hermes\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":75,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":68},"01M7BBJ5C3X8TKFKG5R9P9P49W","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.gemini\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":80,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":68},"01M7BBJ1B52X0QMJ2QVBMPJB37","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.codex\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":85,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":68},"01M7BBHX91BW2Q2R276MRX5AW3","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.claude\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":90,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":68},"01M7BBHQWGXPSFRWN1PRC2NMMV","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.agents\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[]]