{"summary":"Wiki 和說明中心的導覽列、目錄、文末引導、頁尾和手機上的章節切換，分別該如何安排。","notes":"<p>產品變複雜、官網要寫大量 SEO 文章時，一套可靠的 Wiki 既能解答使用者的疑問，也能帶來搜尋流量。最常見的問題是手機上找不到目錄、讀完文章不知道該去哪裡，版面上要處理以下五處：</p>\n        <ol>\n        <li><strong>行動版章節列</strong>：手機大多是直板機，螢幕窄，放不下側邊目錄。在底部常駐一個章節列，點開後以全螢幕選單列出所有章節，一列一項，方便點擊，不必捲回頂部。</li>\n        <li><strong>目錄</strong>：章節多、超出一個畫面時，目錄使用獨立高度，和內文分開捲動，超出的部分在上下截斷。截斷的邊緣加上漸層遮罩，提示上下還有內容，再搭配一個置中的箭頭按鈕，方便點擊捲動。</li>\n        <li><strong>文末引導</strong>：在解答問題的文章下方放社群和社群媒體帳號的入口，無論讀者是人還是 AI，都能帶來轉換，等於為轉換目標免費投放一則情境廣告。卡片樣式貼近內文元件，看起來像文章的一部分。</li>\n        <li><strong>頁尾</strong>：用好看的背景圖把頁尾撐到半個畫面以上，吸引讀者滑到底並停留。頁尾裡要放真正有用的資訊，幫讀者解決問題，否則只會惹人反感。</li>\n        <li><strong>導覽列</strong>：放 Logo（返回官網）、重要頁面的下拉選單和核心 CTA 按鈕，捲動時固定在頂部。Safari 等瀏覽器會依導覽列的顏色為網址列著色，背景色要和品牌協調。</li>\n        </ol>\n        <p>附帶的提示詞會找到文件頁共用的版面，只調整導覽列、目錄、大綱和文末區域的位置、捲動與響應式行為，內容、文案、顏色和字型不變；改完後在頁面頂部、中間、末尾和手機寬度下各截一張圖供你檢查。</p>","prompt":"Polish the layout of my docs or help center pages: the header, the page list, the outline and the end of each article. Keep the content, copy, colours and fonts. Change only how these parts sit, scroll and respond.\n\n0. Start from what exists\n- Find the shared docs layout, the site header, the page list (sidebar), the outline (table of contents) and the footer. Change those, so every page inherits the result.\n- Use CSS and a little plain JS. Add no scroll or animation libraries.\n\n1. Think of the page as three layers\n- The article and the footer scroll with the page.\n- The page list and the outline are position: sticky. They stop where they start, so they never jump when scrolling begins, and the end of the layout pushes them up at the bottom.\n- The header becomes position: fixed only after the page's opening (banner or hero) has left the screen. Before that it belongs to the page and scrolls away with it.\n\n2. Header: it scrolls away, then comes back floating\n- At the top it is clear, with no background.\n- Once the reader has scrolled and the banner's bottom edge is at or above the top of the screen (getBoundingClientRect().bottom <= 0), show it as a floating bar: position: fixed; a translucent white background; backdrop-filter: blur(18px); a soft shadow.\n- It enters in 320ms ease-out, from translateY(-24px) with blur(8px) and opacity 0. It leaves in 120ms when the reader scrolls back up to the banner. If the reader scrolls down again during the exit, cancel it and keep the bar.\n- Give headings a scroll-margin-top so anchor links never land under the bar.\n\n3. Page list: it scrolls on its own, and shows where there is more\n- Hide its scrollbar and let it scroll by itself.\n- Fade an edge only while more of the list waits beyond it. Toggle data-more-above and data-more-below on scroll and resize, and drive a mask-image: linear-gradient(...) with them: about 40px at the top and 56px at the bottom, each with a short fully clear strip at the very edge, so a half-cut row never shows as a faint line.\n- Add a small round arrow on each edge that has more. A click scrolls the list by 60% of its visible height, smoothly. Arrows are for the mouse only (tabindex=\"-1\", aria-hidden=\"true\"); keyboard focus already scrolls the list.\n- On load, bring the current page into view. Keep the list's scroll position in sessionStorage, so moving to another page does not reset it.\n- If there is a search box, let \"/\" focus it.\n\n4. Outline: mark the section being read\n- The current section is the last heading above a line 20% down the viewport.\n- Mark its link with aria-current=\"location\" and style that: border-left-color and text in the accent colour.\n- Update it on scroll, at most once per animation frame.\n\n5. End of the article: help first, then the next page\n- If the reader is still stuck, a \"Still need help?\" card with one or two real channels (the issue tracker, the community, a contact).\n- Then previous and next links, with each page's title. The first page links back to the home page.\n- Then the footer.\n\n6. Narrow screens\n- Hide the outline on tablets and the page list on phones. Put both in one bar fixed at the bottom: the page list on its left half, the outline on its right half.\n- The right half shows the name of the section being read, updated by the same 20% line, and truncated with an ellipsis when it is long.\n- A tap on either half opens its list as a sheet from the bottom edge (a dialog opened with showModal()), sliding up 24px as it fades in, with no dimming behind it. Mark the current entry and scroll it into view (scrollIntoView({ block: \"center\" })).\n- A tap on an entry, the close button, outside the sheet or Esc closes it; a section link then scrolls to its heading.\n- Make the tap targets one size up from the desktop list.\n\n7. Motion\n- Under prefers-reduced-motion: reduce, turn off smooth scrolling and the header's enter and exit animations.\n\n8. When done\n- List every file and selector you changed.\n- Check four states on my own pages: the top of a page, the middle, the end, and a phone-width window.\n- Show a screenshot of each.","skill":"/skills/kubai-wiki-layout/SKILL.md","skillText":"# 兼顾PC和移动端的Wiki布局\n\n《999 个小技巧，让你 Vibe 的产品更有质感》第 008 期 · @kubai087\n\n在用户的项目里按下面的要求改造。要求以用户的口吻写成：文中的 I、me、my 指用户；写着要先问的地方，先停下来问用户再继续。\n\n## 改造要求\n\nPolish the layout of my docs or help center pages: the header, the page list, the outline and the end of each article. Keep the content, copy, colours and fonts. Change only how these parts sit, scroll and respond.\n\n0. Start from what exists\n- Find the shared docs layout, the site header, the page list (sidebar), the outline (table of contents) and the footer. Change those, so every page inherits the result.\n- Use CSS and a little plain JS. Add no scroll or animation libraries.\n\n1. Think of the page as three layers\n- The article and the footer scroll with the page.\n- The page list and the outline are position: sticky. They stop where they start, so they never jump when scrolling begins, and the end of the layout pushes them up at the bottom.\n- The header becomes position: fixed only after the page's opening (banner or hero) has left the screen. Before that it belongs to the page and scrolls away with it.\n\n2. Header: it scrolls away, then comes back floating\n- At the top it is clear, with no background.\n- Once the reader has scrolled and the banner's bottom edge is at or above the top of the screen (getBoundingClientRect().bottom <= 0), show it as a floating bar: position: fixed; a translucent white background; backdrop-filter: blur(18px); a soft shadow.\n- It enters in 320ms ease-out, from translateY(-24px) with blur(8px) and opacity 0. It leaves in 120ms when the reader scrolls back up to the banner. If the reader scrolls down again during the exit, cancel it and keep the bar.\n- Give headings a scroll-margin-top so anchor links never land under the bar.\n\n3. Page list: it scrolls on its own, and shows where there is more\n- Hide its scrollbar and let it scroll by itself.\n- Fade an edge only while more of the list waits beyond it. Toggle data-more-above and data-more-below on scroll and resize, and drive a mask-image: linear-gradient(...) with them: about 40px at the top and 56px at the bottom, each with a short fully clear strip at the very edge, so a half-cut row never shows as a faint line.\n- Add a small round arrow on each edge that has more. A click scrolls the list by 60% of its visible height, smoothly. Arrows are for the mouse only (tabindex=\"-1\", aria-hidden=\"true\"); keyboard focus already scrolls the list.\n- On load, bring the current page into view. Keep the list's scroll position in sessionStorage, so moving to another page does not reset it.\n- If there is a search box, let \"/\" focus it.\n\n4. Outline: mark the section being read\n- The current section is the last heading above a line 20% down the viewport.\n- Mark its link with aria-current=\"location\" and style that: border-left-color and text in the accent colour.\n- Update it on scroll, at most once per animation frame.\n\n5. End of the article: help first, then the next page\n- If the reader is still stuck, a \"Still need help?\" card with one or two real channels (the issue tracker, the community, a contact).\n- Then previous and next links, with each page's title. The first page links back to the home page.\n- Then the footer.\n\n6. Narrow screens\n- Hide the outline on tablets and the page list on phones. Put both in one bar fixed at the bottom: the page list on its left half, the outline on its right half.\n- The right half shows the name of the section being read, updated by the same 20% line, and truncated with an ellipsis when it is long.\n- A tap on either half opens its list as a sheet from the bottom edge (a dialog opened with showModal()), sliding up 24px as it fades in, with no dimming behind it. Mark the current entry and scroll it into view (scrollIntoView({ block: \"center\" })).\n- A tap on an entry, the close button, outside the sheet or Esc closes it; a section link then scrolls to its heading.\n- Make the tap targets one size up from the desktop list.\n\n7. Motion\n- Under prefers-reduced-motion: reduce, turn off smooth scrolling and the header's enter and exit animations.\n\n8. When done\n- List every file and selector you changed.\n- Check four states on my own pages: the top of a page, the middle, the end, and a phone-width window.\n- Show a screenshot of each.\n"}