[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EW7XBBC1PJE7WZFHC7ER1K":3,"skill-same:01M7EW7XBBC1PJE7WZFHC7ER1K":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7EW7XBBC1PJE7WZFHC7ER1K","translation-pro",null,"Handle professional translation — machine translation workflows, localization, quality assurance, and multilingual comms.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-translation-pro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: translation-pro\ndescription: Handle professional translation — machine translation workflows, localization, quality assurance, and multilingual comms.\ncategory: enterprise-communication\n---\n\n## Overview\n\nProfessional translation spans: quick machine translation for internal use, polished localization for customer-facing content, and real-time interpretation for meetings. This skill covers choosing the right approach per content type, machine-translation post-editing workflows, localization beyond words, and quality assurance.\n\n\nProfessional translation and localization adapt content for global audiences: beyond word conversion to cultural resonance.\nMastery covers translation workflows, machine translation post-editing, localization engineering, and quality assurance across languages.\n## When to use\n\n- Translating product UI or documentation\n- Localizing marketing content\n- Setting up multilingual support\n- Running multilingual meetings\n- Building MT post-editing workflows\n- Ensuring translation quality\n\n- Localizing products for new markets\n- Translating marketing campaigns\n- Managing multilingual content operations\n- Implementing machine translation workflows\n- Translating user-generated content\n## Core concepts\n\n**Appropriateness tiers.** Raw MT (internal understanding, gist), MT + light post-edit (internal docs, support macros), MT + full post-edit (help centers, UI), human translation (marketing, legal, brand content), transcreation (slogans, campaigns — rewritten for culture, not translated). Match investment to visibility and risk.\n\n**Localization vs. translation.** Translation converts words; localization adapts: date\u002Fnumber\u002Fcurrency formats, cultural references, imagery, colors, legal requirements, and UX (text expansion — German runs ~30% longer than English; design for it). True localization feels native.\n\n**MT post-editing.** Workflow: MT draft → human editor fixes errors and awkwardness → QA check. Provide editors with: glossaries (approved terms), style guides per language, and context (screenshots for UI strings — translators can't guess from isolated strings).\n\n**Glossaries and TMs.** Term bases (approved translations for key terms — brand names, product terms) and translation memories (reuse of past translations) ensure consistency and cut costs. Maintain them as living assets; inconsistent terminology confuses users and looks unprofessional.\n\n**Quality assurance.** Back-translation (for critical content), in-country review (native speakers checking naturalness), linguistic QA (spelling, grammar, consistency), and functional QA (UI fits, links work, no encoding issues). Sample-based QA for volume; full review for high-stakes content.\n\n**Real-time.** Live captions\u002Ftranslation in meetings, interpretation for important calls (consecutive vs. simultaneous), and multilingual chat support (MT-assisted agents with human oversight). Set expectations: real-time MT is gist-level, not publication-level.\n\n\n**Translation vs. localization.** Translation converts words; localization adapts meaning, imagery, formats, and cultural references.\nMarketing content needs transcreation (creative rewriting); UI needs functional localization; legal needs certified precision.\nMatch approach to content type — one method does not fit all.\n**Machine translation + post-editing (MTPE).** Raw MT for gisting → light post-editing (accuracy) → full post-editing (publishable quality).\nMTPE cuts costs 30–50% for suitable content (technical, repetitive).\nCreative and brand content still needs human translation — MTPE produces adequate, not excellent.\n**CAT tools and TMs.** Translation memory (reuse past translations), terminology bases (consistent terms), and QA checks.\nTMs compound value — leverage grows with every project.\nInvest in terminology management; inconsistent terms confuse globally.\n## Practical workflow\n\n1. **Classify content.** Tier each content type (UI, docs, marketing, legal, support) to its translation approach. This drives budget and workflow.\n2. **Build assets.** Glossaries per language, style guides, translation memories, and context packages (screenshots, descriptions). Upfront investment pays back in consistency forever.\n3. **Set up workflows.** Source content → tier-appropriate translation → review → QA → publish. Integrate with content pipelines (docs, product releases) so translation isn't a last-minute scramble.\n4. **Post-edit effectively.** Train editors on: when to fix vs. rewrite, terminology adherence, and flagging MT systematic errors (feedback improves engines). Track edit distance — high edits mean the engine or source needs work.\n5. **QA.** Linguistic checks, in-country review for launches, functional testing of localized UI, and back-translation for legal\u002Fmedical critical content.\n6. **Maintain.** Update TMs\u002Fglossaries with every project, review quality metrics (edit rates, in-country feedback, support tickets about confusion), and refresh stale translations when source content changes.\n\n**Source writing for translation:** short sentences, no idioms\u002Fslang, consistent terminology, one idea per sentence, and context notes for ambiguous terms. Good source text halves translation effort.\n\n\n**Localization workflow:** content freeze → extraction → translation\u002FMTPE → linguistic QA → in-context review → functional testing → publish.\nBuild localization into development (i18n) from the start — retrofitting is 10x harder.\n**Quality framework:** accuracy, fluency, terminology, style, and locale conventions.\nSample-based QA (10–20%) for routine content; 100% for critical.\nTrack quality scores per vendor; manage the supply chain actively.\n## Common pitfalls\n\n- **Raw MT for customer content.** Publishing unedited machine output. Embarrassing errors erode trust — post-edit customer-facing text.\n- **No context for translators.** Isolated UI strings translated blind. Provide screenshots and descriptions.\n- **Ignoring text expansion.** German\u002FFrench overflowing buttons designed for English. Design with 30–40% expansion room.\n- **Inconsistent terminology.** Five translations for the same product term. Maintain and enforce glossaries.\n- **Translating idioms literally.** \"Break a leg\" becomes medical advice. Flag idioms for transcreation.\n- **One-and-done.** Translating once, never updating when source changes. Stale translations mislead.\n- **Skipping in-country review.** Translations that are technically correct but culturally tone-deaf. Native review for launches.\n- **Translating without context.** Strings without screenshots or descriptions. Context-free translation produces errors — provide visual context always.\n- **Ignoring text expansion.** German runs 30% longer than English; UI breaks. Design flexible layouts; test in longest languages.\n- **One translator per language.** No redundancy or review. Every language needs primary + reviewer minimum.\n- **Machine-only for brand content.** Raw MT on marketing copy. Brand voice needs humans — MTPE minimum for customer-facing content.\n- **Ignoring right-to-left.** Layouts breaking in Arabic\u002FHebrew. Design RTL from the start — retrofitting is expensive.\n","## Overview\n\nProfessional translation spans: quick machine translation for internal use, polished localization for customer-facing content, and real-time interpretation for meetings. This skill covers choosing the right approach per content type, machine-translation post-editing workflows, localization beyond words, and quality assurance.\n\n\nProfessional translation and localization adapt content for global audiences: beyond word conversion to cultural resonance.\nMastery covers translation workflows, machine translation post-editing, localization engineering, and quality assurance across languages.\n## When to use\n\n- Translating product UI or documentation\n- Localizing marketing content\n- Setting up multilingual support\n- Running multilingual meetings\n- Building MT post-editing workflows\n- Ensuring translation quality\n\n- Localizing products for new markets\n- Translating marketing campaigns\n- Managing multilingual content operations\n- Implementing machine translation workflows\n- Translating user-generated content\n## Core concepts\n\n**Appropriateness tiers.** Raw MT (internal understanding, gist), MT + light post-edit (internal docs, support macros), MT + full post-edit (help centers, UI), human translation (marketing, legal, brand content), transcreation (slogans, campaigns — rewritten for culture, not translated). Match investment to visibility and risk.\n\n**Localization vs. translation.** Translation converts words; localization adapts: date\u002Fnumber\u002Fcurrency formats, cultural references, imagery, colors, legal requirements, and UX (text expansion — German runs ~30% longer than English; design for it). True localization feels native.\n\n**MT post-editing.** Workflow: MT draft → human editor fixes errors and awkwardness → QA check. Provide editors with: glossaries (approved terms), style guides per language, and context (screenshots for UI strings — translators can't guess from isolated strings).\n\n**Glossaries and TMs.** Term bases (approved translations for key terms — brand names, product terms) and translation memories (reuse of past translations) ensure consistency and cut costs. Maintain them as living assets; inconsistent terminology confuses users and looks unprofessional.\n\n**Quality assurance.** Back-translation (for critical content), in-country review (native speakers checking naturalness), linguistic QA (spelling, grammar, consistency), and functional QA (UI fits, links work, no encoding issues). Sample-based QA for volume; full review for high-stakes content.\n\n**Real-time.** Live captions\u002Ftranslation in meetings, interpretation for important calls (consecutive vs. simultaneous), and multilingual chat support (MT-assisted agents with human oversight). Set expectations: real-time MT is gist-level, not publication-level.\n\n\n**Translation vs. localization.** Translation converts words; localization adapts meaning, imagery, formats, and cultural references.\nMarketing content needs transcreation (creative rewriting); UI needs functional localization; legal needs certified precision.\nMatch approach to content type — one method does not fit all.\n**Machine translation + post-editing (MTPE).** Raw MT for gisting → light post-editing (accuracy) → full post-editing (publishable quality).\nMTPE cuts costs 30–50% for suitable content (technical, repetitive).\nCreative and brand content still needs human translation — MTPE produces adequate, not excellent.\n**CAT tools and TMs.** Translation memory (reuse past translations), terminology bases (consistent terms), and QA checks.\nTMs compound value — leverage grows with every project.\nInvest in terminology management; inconsistent terms confuse globally.\n## Practical workflow\n\n1. **Classify content.** Tier each content type (UI, docs, marketing, legal, support) to its translation approach. This drives budget and workflow.\n2. **Build assets.** Glossaries per language, style guides, translation memories, and context packages (screenshots, descriptions). Upfront investment pays back in consistency forever.\n3. **Set up workflows.** Source content → tier-appropriate translation → review → QA → publish. Integrate with content pipelines (docs, product releases) so translation isn't a last-minute scramble.\n4. **Post-edit effectively.** Train editors on: when to fix vs. rewrite, terminology adherence, and flagging MT systematic errors (feedback improves engines). Track edit distance — high edits mean the engine or source needs work.\n5. **QA.** Linguistic checks, in-country review for launches, functional testing of localized UI, and back-translation for legal\u002Fmedical critical content.\n6. **Maintain.** Update TMs\u002Fglossaries with every project, review quality metrics (edit rates, in-country feedback, support tickets about confusion), and refresh stale translations when source content changes.\n\n**Source writing for translation:** short sentences, no idioms\u002Fslang, consistent terminology, one idea per sentence, and context notes for ambiguous terms. Good source text halves translation effort.\n\n\n**Localization workflow:** content freeze → extraction → translation\u002FMTPE → linguistic QA → in-context review → functional testing → publish.\nBuild localization into development (i18n) from the start — retrofitting is 10x harder.\n**Quality framework:** accuracy, fluency, terminology, style, and locale conventions.\nSample-based QA (10–20%) for routine content; 100% for critical.\nTrack quality scores per vendor; manage the supply chain actively.\n## Common pitfalls\n\n- **Raw MT for customer content.** Publishing unedited machine output. Embarrassing errors erode trust — post-edit customer-facing text.\n- **No context for translators.** Isolated UI strings translated blind. Provide screenshots and descriptions.\n- **Ignoring text expansion.** German\u002FFrench overflowing buttons designed for English. Design with 30–40% expansion room.\n- **Inconsistent terminology.** Five translations for the same product term. Maintain and enforce glossaries.\n- **Translating idioms literally.** \"Break a leg\" becomes medical advice. Flag idioms for transcreation.\n- **One-and-done.** Translating once, never updating when source changes. Stale translations mislead.\n- **Skipping in-country review.** Translations that are technically correct but culturally tone-deaf. Native review for launches.\n- **Translating without context.** Strings without screenshots or descriptions. Context-free translation produces errors — provide visual context always.\n- **Ignoring text expansion.** German runs 30% longer than English; UI breaks. Design flexible layouts; test in longest languages.\n- **One translator per language.** No redundancy or review. Every language needs primary + reviewer minimum.\n- **Machine-only for brand content.** Raw MT on marketing copy. Brand voice needs humans — MTPE minimum for customer-facing content.\n- **Ignoring right-to-left.** Layouts breaking in Arabic\u002FHebrew. Design RTL from the start — retrofitting is expensive.\n",{"name":5,"category":24,"description":7},"enterprise-communication","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-translation-pro",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill translation-pro",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill translation-pro",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill translation-pro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-translation-pro\u002FSKILL.md",true,[],[48,55,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]