{"summary":"Como resolver, em textos em chinês e inglês, as quebras de linha dos títulos, os números que tremem, o texto truncado, os detalhes do chinês e o tamanho das traduções.","notes":"<p>Na primeira tela de um site, a segunda linha do título fica com uma palavra só; numa contagem regressiva, o texto ao lado se mexe a cada salto; ao trocar para o alemão, o rótulo de um botão é espremido em duas linhas. São problemas de quebra de linha e de largura dos caracteres, e a maioria se resolve com algumas regras de CSS. Os casos mais comuns são estes:</p>\n        <ol>\n        <li><strong>Quebras de linha</strong>: títulos usam <code>text-wrap: balance</code>, para que as linhas tenham tamanho parecido e a última não fique com uma ou duas palavras; o texto corrido usa <code>text-wrap: pretty</code>, para não sobrar uma palavra sozinha no fim do parágrafo; rótulos de botão usam <code>white-space: nowrap</code> e ficam sempre em uma linha.</li>\n        <li><strong>Números</strong>: em números que mudam, como cronômetros, preços e contadores, <code>font-variant-numeric: tabular-nums</code> dá a mesma largura a todos os algarismos. Sem isso, ao passar de 11 para 10, o “1” é mais estreito que o “0” e o texto seguinte se desloca.</li>\n        <li><strong>Truncamento</strong>: para mostrar reticências num texto longo, além de <code>text-overflow: ellipsis</code> é preciso pôr <code>min-width: 0</code> no elemento dentro do layout flexível. A largura mínima de um filho flex é, por padrão, a largura do conteúdo; sem essa regra, o texto alarga o contêiner e as reticências não aparecem.</li>\n        <li><strong>Texto em chinês</strong>: <code>text-align: justify</code> justifica o texto, e com a largura da linha igual a um número inteiro de caracteres a margem direita fica alinhada; <code>text-autospace: normal</code> põe automaticamente um espaço entre o chinês e o texto latino ou os números; <code>text-spacing-trim: trim-start</code> remove o meio espaço em branco de um parêntese de abertura no início da linha.</li>\n        <li><strong>Títulos em chinês e regras de início e fim de linha</strong>: nos títulos, o BudouX marca os pontos de quebra entre palavras e, junto com <code>word-break: keep-all</code>, o texto quebra por palavras, nunca no meio de uma. As regras de início e fim de linha ficam por conta do navegador, e remove-se <code>line-break: anywhere</code>, que as desativa.</li>\n        <li><strong>Vários idiomas</strong>: o mesmo espaço precisa acomodar traduções de tamanhos diferentes; as palavras em alemão costumam ser mais longas que em inglês, e um botão que em inglês cabe exatamente em uma linha pode não caber em alemão. Ao traduzir, peça ao agente que leve em conta o layout da página e escolha uma tradução de tamanho adequado, sem quebrar uma palavra em duas linhas nem deixar espaço vazio demais.</li>\n        </ol>\n        <p>O prompt que acompanha esta dica escreve essas regras nos estilos globais, herdados por todas as páginas, e só ajusta a quebra de linha, o espaçamento, o alinhamento e o truncamento do texto, sem mudar os textos, as fontes nem as cores; no fim, lista os arquivos alterados e compara o antes e o depois nas suas páginas.</p>","prompt":"Polish the typography in my product with a set of CSS switches. Change only how text wraps, spaces, aligns and truncates. No copy, font, colour or layout changes beyond what each rule says.\n\n0. Start from what exists\n- Put the rules in the global text styles (base CSS, typography tokens, Tailwind config or shared text components) so every page inherits them. Add per-component rules only where a component overrides the base.\n- Every rule below is progressive enhancement: browsers that don't know a property ignore it. Add no polyfills.\n- Scope the Chinese rules with :lang(zh), and make sure the lang attribute is set on the html element or on the element itself, so English text keeps its own rules.\n\n1. Headings break into even lines\n- On h1 to h3, card titles and hero lines: text-wrap: balance;\n- Lines come out about the same length, so a heading never ends on one lonely word. Short text only: Chrome balances up to 6 lines.\n\n2. No lone word at the end of a paragraph\n- On paragraphs, descriptions and list items: text-wrap: pretty;\n- Also join pairs that must not split with a non-breaking space (U+00A0): an em dash and the name after it, a number and its unit.\n\n3. Numbers that change keep their width\n- On anything that updates in place or sits in a column (counters, prices, timers, stats, table cells): font-variant-numeric: tabular-nums;\n- The font must have tabular figures (the tnum feature); check that the width actually stops changing. Leave running text proportional.\n\n4. Button labels stay on one line\n- On buttons and other labels in flex rows: white-space: nowrap; (flex-shrink: 0 works too)\n- A crowded row must not squeeze a label onto two lines.\n\n5. Long text truncates instead of spilling out\n- A flex item won't shrink below its content, so text inside it can't truncate. On the flex item: min-width: 0;\n- On the text itself: overflow: hidden; white-space: nowrap; text-overflow: ellipsis;\n- When the text really is cut (scrollWidth > clientWidth), show the full text in a tooltip on hover.\n\n6. Chinese body text: justified, on a whole number of characters\n- On Chinese paragraphs only: text-align: justify;\n- Set the measure to a whole number of characters (for example max-width: 26em at the paragraph's font size), so a justified line only stretches to absorb Latin words and squeezed punctuation.\n- Not for narrow columns (under about 15 characters), short text, captions, buttons or mostly-English text: the gaps get uneven.\n\n7. Space between Chinese and Latin text or numbers\n- On Chinese text: text-autospace: normal;\n- The browser adds a thin gap between Han characters and Latin letters or digits. Don't also hand-type spaces in copy or translation files. Skip code, inputs and monospaced text.\n\n8. No half-width gap before an opening bracket at a line start\n- On Chinese UI text without a first-line indent: text-spacing-trim: trim-start;\n- An opening 「 “ （ at the start of a line drops its blank half and lines up with the text above. Long-form text with a two-character indent should use space-first instead. Chrome only for now.\n\n9. Chinese headings break between words\n- Chinese has no spaces, so a heading can split a word across lines. Mark the break points between words with BudouX (its Simplified or Traditional Chinese model), inserting a wbr element at each one, at build time for static copy or at render time for dynamic copy. Then: word-break: keep-all; overflow-wrap: anywhere; text-wrap: balance;\n- Never use keep-all on Chinese without break points: the heading becomes one unbreakable word. Don't use Intl.Segmenter for this (it splits common words wrongly), and don't apply it to body text.\n\n10. Line-start and line-end rules (避头尾)\n- Browsers already keep punctuation off the start of a line and squeeze line-end punctuation. Don't rebuild this.\n- Find and remove any line-break: anywhere used to stop overflow: it turns these rules off. Use overflow-wrap: anywhere instead.\n- Text drawn on canvas or SVG, or wrapped by hand in JS, gets none of this: apply the rules there yourself.\n\n11. When done\n- List every file and selector you changed.\n- List every line-break: anywhere and word-break: break-all you removed or kept, and why.\n- Show before and after on my own pages: a wrapped heading, a paragraph ending, a changing number, a truncated label and a mixed Chinese-English paragraph.","skill":"/skills/kubai-type-switches/SKILL.md","skillText":"# 中英文排版的CSS设置\n\n《999 个小技巧，让你 Vibe 的产品更有质感》第 007 期 · @kubai087\n\n在用户的项目里按下面的要求改造。要求以用户的口吻写成：文中的 I、me、my 指用户；写着要先问的地方，先停下来问用户再继续。\n\n## 改造要求\n\nPolish the typography in my product with a set of CSS switches. Change only how text wraps, spaces, aligns and truncates. No copy, font, colour or layout changes beyond what each rule says.\n\n0. Start from what exists\n- Put the rules in the global text styles (base CSS, typography tokens, Tailwind config or shared text components) so every page inherits them. Add per-component rules only where a component overrides the base.\n- Every rule below is progressive enhancement: browsers that don't know a property ignore it. Add no polyfills.\n- Scope the Chinese rules with :lang(zh), and make sure the lang attribute is set on the html element or on the element itself, so English text keeps its own rules.\n\n1. Headings break into even lines\n- On h1 to h3, card titles and hero lines: text-wrap: balance;\n- Lines come out about the same length, so a heading never ends on one lonely word. Short text only: Chrome balances up to 6 lines.\n\n2. No lone word at the end of a paragraph\n- On paragraphs, descriptions and list items: text-wrap: pretty;\n- Also join pairs that must not split with a non-breaking space (U+00A0): an em dash and the name after it, a number and its unit.\n\n3. Numbers that change keep their width\n- On anything that updates in place or sits in a column (counters, prices, timers, stats, table cells): font-variant-numeric: tabular-nums;\n- The font must have tabular figures (the tnum feature); check that the width actually stops changing. Leave running text proportional.\n\n4. Button labels stay on one line\n- On buttons and other labels in flex rows: white-space: nowrap; (flex-shrink: 0 works too)\n- A crowded row must not squeeze a label onto two lines.\n\n5. Long text truncates instead of spilling out\n- A flex item won't shrink below its content, so text inside it can't truncate. On the flex item: min-width: 0;\n- On the text itself: overflow: hidden; white-space: nowrap; text-overflow: ellipsis;\n- When the text really is cut (scrollWidth > clientWidth), show the full text in a tooltip on hover.\n\n6. Chinese body text: justified, on a whole number of characters\n- On Chinese paragraphs only: text-align: justify;\n- Set the measure to a whole number of characters (for example max-width: 26em at the paragraph's font size), so a justified line only stretches to absorb Latin words and squeezed punctuation.\n- Not for narrow columns (under about 15 characters), short text, captions, buttons or mostly-English text: the gaps get uneven.\n\n7. Space between Chinese and Latin text or numbers\n- On Chinese text: text-autospace: normal;\n- The browser adds a thin gap between Han characters and Latin letters or digits. Don't also hand-type spaces in copy or translation files. Skip code, inputs and monospaced text.\n\n8. No half-width gap before an opening bracket at a line start\n- On Chinese UI text without a first-line indent: text-spacing-trim: trim-start;\n- An opening 「 “ （ at the start of a line drops its blank half and lines up with the text above. Long-form text with a two-character indent should use space-first instead. Chrome only for now.\n\n9. Chinese headings break between words\n- Chinese has no spaces, so a heading can split a word across lines. Mark the break points between words with BudouX (its Simplified or Traditional Chinese model), inserting a wbr element at each one, at build time for static copy or at render time for dynamic copy. Then: word-break: keep-all; overflow-wrap: anywhere; text-wrap: balance;\n- Never use keep-all on Chinese without break points: the heading becomes one unbreakable word. Don't use Intl.Segmenter for this (it splits common words wrongly), and don't apply it to body text.\n\n10. Line-start and line-end rules (避头尾)\n- Browsers already keep punctuation off the start of a line and squeeze line-end punctuation. Don't rebuild this.\n- Find and remove any line-break: anywhere used to stop overflow: it turns these rules off. Use overflow-wrap: anywhere instead.\n- Text drawn on canvas or SVG, or wrapped by hand in JS, gets none of this: apply the rules there yourself.\n\n11. When done\n- List every file and selector you changed.\n- List every line-break: anywhere and word-break: break-all you removed or kept, and why.\n- Show before and after on my own pages: a wrapped heading, a paragraph ending, a changing number, a truncated label and a mixed Chinese-English paragraph.\n"}