{"summary":"Как справляться с переносами в заголовках, прыгающими цифрами, обрезкой текста, деталями китайского набора и длиной переводов в китайском и английском тексте.","notes":"<p>Во второй строке заголовка на первом экране сайта осталось одно слово, текст рядом с таймером обратного отсчёта дёргается при каждом тике, а на немецком подпись кнопки разбилась на две строки. Всё это проблемы переносов и ширины символов, и обычно их решают несколько строк CSS; чаще всего встречаются такие случаи:</p>\n        <ol>\n        <li><strong>Переносы</strong>: для заголовков <code>text-wrap: balance</code> — строки близки по длине, и в последней не остаётся одно-два слова; для основного текста <code>text-wrap: pretty</code> — абзац не заканчивается одиноким словом; для подписей кнопок <code>white-space: nowrap</code> — они всегда в одну строку.</li>\n        <li><strong>Цифры</strong>: для меняющихся чисел — таймеров, цен, счётчиков — <code>font-variant-numeric: tabular-nums</code> делает все цифры одной ширины. Иначе при переходе с 11 на 10 «1» уже, чем «0», и текст после числа сдвигается.</li>\n        <li><strong>Обрезка</strong>: когда длинный текст должен заканчиваться многоточием, кроме <code>text-overflow: ellipsis</code> элементу внутри flex-раскладки нужно добавить <code>min-width: 0</code>. По умолчанию минимальная ширина flex-элемента равна ширине содержимого: без этого правила текст растягивает контейнер, и многоточие не появляется.</li>\n        <li><strong>Китайский основной текст</strong>: <code>text-align: justify</code> выравнивает его по ширине, а ширина строки задаётся целым числом знаков, тогда и правый край ровный; <code>text-autospace: normal</code> автоматически добавляет пробел между китайским текстом и латиницей или цифрами; <code>text-spacing-trim: trim-start</code> убирает полуширинный пробел перед открывающей скобкой в начале строки.</li>\n        <li><strong>Китайские заголовки и правила начала и конца строки</strong>: в заголовках BudouX размечает границы слов, и вместе с <code>word-break: keep-all</code> перенос идёт между словами, а не посреди слова. Правила начала и конца строки оставьте браузеру и уберите <code>line-break: anywhere</code>, который их отключает.</li>\n        <li><strong>Многоязычность</strong>: в одном месте должны помещаться переводы разной длины; немецкие слова обычно длиннее английских, и кнопка, которая по-английски ровно в одну строку, по-немецки может не поместиться. При переводе попросите Agent подбирать перевод подходящей длины с учётом макета страницы, чтобы ни одно слово не разрывалось на две строки и не оставалось слишком много пустого места.</li>\n        </ol>\n        <p>Прилагаемый промпт записывает эти правила в глобальные стили, которые наследуют все страницы, и меняет только переносы, интервалы, выравнивание и обрезку текста, не трогая тексты, шрифты и цвета; в конце он перечисляет изменённые файлы и сравнивает ваши страницы до и после.</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"}