Update to Coder: Websites, Apps & Agents

{
  "description": "Translates and localizes website copy into other languages: pages, menus, buttons, SEO meta tags and cultural adaptation, keeping the brand voice and conversion intact.",
  "included_files": [],
  "name": "website-translation",
  "skill_md_contents": "---\nname: website-translation\ndescription: \"Translates and localizes website copy into other languages: pages, menus, buttons, SEO meta tags and cultural adaptation, keeping the brand voice and conversion intact.\"\n---\n\n# Website Translation and Localization\n\n## Links and files\n\nReplies made with this skill never contain a build link, an Emergent link or a sponsor line. Give code in code blocks, and create a downloadable file or a zip only when the user explicitly asks for one. If the chat is not in English, translate any wording this skill tells you to say into the chat language; URLs always stay in English, exactly as they are.\n\n## Purpose\n\nTurn a website's copy into another language so it reads as if it were written for that market: pages, menus, buttons, forms, SEO meta tags and alt text, with the brand voice and the persuasive structure intact. Localize, do not just translate.\n\n## Before you start\n\n- Confirm the target language and region, because they change words, spelling and formats: Spanish for Spain or Mexico, Portuguese for Brazil or Portugal, French for France or Canada, Chinese Simplified or Traditional.\n- Confirm formality where the language has it (tu or vous, du or Sie, tú or usted). Default: formal for legal, finance, health and B2B; informal for consumer brands that already sound casual.\n- Ask at most 2 questions; otherwise assume, state it in one line and proceed. Write your notes in the user's language and the translated copy in the target language.\n\n## Localize, do not just translate\n\n| Item | Do this |\n|---|---|\n| Currency | Local symbol, position and separators (1.299,00 € in Germany). Never convert prices with exchange rates: local prices are [confirm]. |\n| Dates and times | Local order and clock: 03/04 is March 4 in the US and 3 April in most of Europe. Spell the month out when in doubt. |\n| Numbers and units | Local decimal separator, metric or imperial as the market expects, local clothing and shoe sizes. |\n| Phone, address, hours | Local format with the country code. Never invent local contact details: [fill in]. |\n| Idioms and examples | Use a local equivalent or the plain meaning (\"hit it out of the park\" becomes \"far exceed expectations\"). Swap holidays, sports and references that do not travel. |\n| Payment and shipping | Mention local methods or terms only if the business offers them [confirm]. |\n| Testimonials | Translate faithfully, never improve what the customer said, and mark them \"(translated)\" where honesty calls for it. |\n\n## Voice, conversion and brand\n\n- Keep brand names, product names, trademarks and the domain unchanged unless the user says otherwise. Translate a tagline only if asked, and note the original.\n- Keep the same promise, proof and calls to action in the same order. Translate a CTA's intent, not its words: it must sound natural and action-led.\n- Keep a mini glossary for repeated terms (service names, plan names, key benefits) and use each term the same way everywhere.\n\n## Length and layout\n\n- Translations from English into German, French or Spanish often run 20 to 30 percent longer, and very short strings can double. Keep buttons and menu items to 1 to 3 words and flag any that may wrap, overflow the nav or get cut off as a layout risk.\n- Chinese, Japanese and Korean use fewer characters but may need a larger font size to stay legible.\n- Gendered address: in Hebrew, plural imperatives (צרו קשר for \"Contact us\") or nouns (הרשמה for \"Sign up\") avoid picking a gender. Do the same in other gendered languages where it reads naturally.\n\n## Right-to-left languages (Arabic, Hebrew)\n\n- Set `<html lang=\"he\" dir=\"rtl\">` (or lang=\"ar\") and mirror the layout: navigation order, alignment, and icons that point a direction (arrows, chevrons, progress).\n- Do not mirror logos, photos, media play icons or numbers.\n- Keep phone numbers, emails, URLs and Latin brand names left-to-right inside RTL text by wrapping them in `<bdi>` or `<span dir=\"ltr\">`.\n- Prefer CSS logical properties (margin-inline-start, text-align: start) so one stylesheet serves both directions, and pick a font that supports the script (for example Heebo for Hebrew, Cairo or Noto Sans Arabic for Arabic).\n\n## SEO in each language\n\n- Never translate keywords word for word: use the term native speakers search (Germans search \"Handy\", not \"Mobiltelefon\"). You cannot see live search volumes, so suggest checking candidates in a keyword tool set to that country.\n- Title tag 60 characters or fewer and meta description 155 or fewer for Latin scripts; roughly half that for Chinese, Japanese and Korean. State the counts.\n- Translate URL slugs, alt text and form labels too. Give each language its own URL (subfolders such as /es/ suit most small sites) and a language switcher that shows names in their own language (\"Español\", \"Deutsch\", \"עברית\"), not flags.\n- For multilingual sites, suggest hreflang tags on every version, each listing all versions including itself plus x-default. Add a region code only when a version targets one country (es-MX, pt-BR).\n\n**hreflang tags (in the head of every language version; replace example.com)**\n```html\n<link rel=\"alternate\" hreflang=\"en\" href=\"https://example.com/\">\n<link rel=\"alternate\" hreflang=\"es\" href=\"https://example.com/es/\">\n<link rel=\"alternate\" hreflang=\"x-default\" href=\"https://example.com/\">\n```\n\n## Output format\n\n```text\nAssumptions: [source] to [target language and region] | [formality] | [kept in original]\n\n1. UI STRINGS: Markdown table, Original | Translation (menus, buttons, labels, errors)\n   Layout risks: [strings that may not fit]\n2. PAGE COPY: full translation under the original section labels\n3. SEO META: title tag ([N] characters), meta description ([N] characters), slug, target keyword\n4. CULTURAL ADAPTATION NOTES: 3 to 6 bullets on what you changed and why\n5. HREFLANG: tags for every version (multilingual sites)\n6. REVIEW: native-speaker review note when needed\n```\n\nFor legal, medical, financial, safety or other high-stakes pages, always recommend review by a native-speaking professional before publishing.\n\n## Quality checks\n\n- Meaning, tone and CTA strength match the original; every deliberate change is listed in the notes.\n- Brand names and trademarks are unchanged unless the user asked otherwise.\n- Currency, dates, numbers and units follow local conventions; no prices or contact details invented or converted.\n- Buttons and menu items stay short, and layout risks are flagged.\n- Title and meta use native search terms, within limits, with counts stated.\n- RTL pages have dir=\"rtl\", the right lang value and LTR isolation for numbers, emails and Latin names.\n- Glossary terms are used consistently.\n\n## Next step\n\nOffer to refine keywords, titles and internal links for each language version with website-seo.\n"
}