{"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> أيضًا <code>min-width: 0</code> للعنصر داخل التخطيط المرن. فالحد الأدنى لعرض العناصر الفرعية المرنة يساوي افتراضيًا عرض محتواها، وبدون هذا السطر يوسّع النص الحاوية ولا تظهر علامة الحذف.</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>يكتب الـ Prompt المرفق هذه القواعد في الأنماط العامة التي ترثها كل الصفحات، ولا يعدّل إلا انكسار الأسطر والتباعد والمحاذاة والاقتطاع، دون تغيير النصوص والخطوط والألوان؛ ثم يسرد الملفات التي عدّلها، ويقارن صفحتك قبل التعديل وبعده.</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"}