{
  "language": {
    "id": "zh-hant",
    "tag": "zh-Hant",
    "name": "繁體中文"
  },
  "note": "如需修正翻譯，請下載本語言的文字，修改後寄至 i@kubai.design。",
  "contact": "i@kubai.design",
  "format": "Each entry gives the English (\"en\") and this language (\"text\"). Change only \"text\", keep {placeholders}, code and HTML tags as they are, and send the file back.",
  "interface": {
    "colon": {
      "en": ": ",
      "text": "："
    },
    "all": {
      "en": "All",
      "text": "全部"
    },
    "saved": {
      "en": "Saved",
      "text": "我的收藏"
    },
    "filterLabel": {
      "en": "Filter by category",
      "text": "依類別篩選"
    },
    "savedNone": {
      "en": "No saved tips yet",
      "text": "還沒有收藏的技巧"
    },
    "savedSignIn": {
      "en": "Sign in to see the tips you saved",
      "text": "登入後即可查看你收藏的技巧"
    },
    "marksTitle": {
      "en": "(n) => `${n} ${n === 1 ? \"highlight\" : \"highlights\"}`",
      "text": "(n) => `螢光標記 ${n} 處`"
    },
    "marksExport": {
      "en": "Export as Markdown",
      "text": "匯出為 Markdown"
    },
    "ellipsis": {
      "en": "…",
      "text": "……"
    },
    "marksExported": {
      "en": "Highlights exported",
      "text": "已匯出螢光標記"
    },
    "marksFile": {
      "en": "My highlights · Vibe Design Tips",
      "text": "我的螢光標記 · Vibe Design Tips"
    },
    "signInClosed": {
      "en": "Sign-in is not open yet",
      "text": "登入功能尚未開放"
    },
    "signIn": {
      "en": "Sign in",
      "text": "登入"
    },
    "save": {
      "en": "Save",
      "text": "收藏"
    },
    "unsave": {
      "en": "Remove from saved",
      "text": "取消收藏"
    },
    "savedState": {
      "en": "Saved",
      "text": "已收藏"
    },
    "copy": {
      "en": "Copy",
      "text": "複製"
    },
    "copied": {
      "en": "Copied",
      "text": "已複製"
    },
    "promptNote": {
      "en": "Paste it into an agent such as Claude Code or Cursor",
      "text": "複製後傳給 Claude Code、Cursor 等 Agent 即可"
    },
    "install": {
      "en": "Copy install prompt",
      "text": "複製安裝提示詞"
    },
    "installTitle": {
      "en": "Give this prompt to your agent: it installs the Skill, and can update it later",
      "text": "傳給你的 Agent 即可安裝，之後也能更新"
    },
    "installCopied": {
      "en": "Copied. Give it to your agent to install",
      "text": "已複製，傳給你的 Agent 即可安裝"
    },
    "installPrompt": {
      "en": "(name, guide, mirror) => [\n\t\t`Please install the ${name} Skill for me, from Vibe Design Tips, so it works in every project and can be updated later.`,\n\t\t\"\",\n\t\t`Follow the steps in ${guide} and install ${name}.`,\n\t\t`If GitHub cannot be reached, use ${mirror} instead.`,\n\t\t\"\",\n\t\t\"If it is already installed, follow the update steps there. Then tell me the version and where you installed it.\"\n\t].join(\"\\n\")",
      "text": "(name, guide, mirror) => [\n\t\t\t`請幫我安裝 ${name} 這個 Skill（來自 Vibe Design Tips），讓它在所有專案中都能使用，之後也能更新。`,\n\t\t\t\"\",\n\t\t\t`請依照 ${guide} 中的步驟操作，安裝 ${name}。`,\n\t\t\t`如果無法開啟 GitHub，請改用 ${mirror} 。`,\n\t\t\t\"\",\n\t\t\t\"如果已經安裝過，請依照其中的更新步驟操作。完成後告訴我版本號和安裝位置。\"\n\t\t].join(\"\\n\")"
    },
    "copyFailed": {
      "en": "Copy failed",
      "text": "複製失敗"
    },
    "demo": {
      "en": "(name) => `${name} demo`",
      "text": "(name) => `${name} 示範`"
    },
    "reset": {
      "en": "Reset",
      "text": "重設"
    },
    "loadFailed": {
      "en": [
        "Could not load this tip. ",
        "Reload the page",
        " to try again."
      ],
      "text": [
        "無法載入這則技巧，請",
        "重新載入頁面",
        "後再試一次。"
      ]
    },
    "viewOnX": {
      "en": "View the post on X",
      "text": "在 X 上查看原始貼文"
    },
    "privacy": {
      "en": "Privacy",
      "text": "隱私權政策"
    },
    "close": {
      "en": "Close",
      "text": "關閉"
    },
    "themeToggle": {
      "en": "Dark mode",
      "text": "深色模式"
    },
    "themeTip": {
      "en": "Dark mode",
      "text": "深色模式"
    },
    "themeTipDark": {
      "en": "Light mode",
      "text": "淺色模式"
    },
    "autoplayToggle": {
      "en": "Autoplay videos",
      "text": "自動播放影片"
    },
    "autoplayTip": {
      "en": "Pause autoplay",
      "text": "暫停自動播放"
    },
    "autoplayTipOff": {
      "en": "Autoplay videos",
      "text": "自動播放影片"
    },
    "langSwitch": {
      "en": "Language",
      "text": "語言"
    },
    "sideCollapse": {
      "en": "Collapse sidebar",
      "text": "收合側邊欄"
    },
    "sideExpand": {
      "en": "Expand sidebar",
      "text": "展開側邊欄"
    },
    "menu": {
      "en": "Menu",
      "text": "選單"
    },
    "community": {
      "en": "Join the community",
      "text": "加入社群"
    },
    "projects": {
      "en": "Related work",
      "text": "相關作品"
    },
    "projectPrev": {
      "en": "Previous project",
      "text": "上一個作品"
    },
    "projectNext": {
      "en": "Next project",
      "text": "下一個作品"
    },
    "readingTools": {
      "en": "Reading tools",
      "text": "閱讀工具"
    },
    "textSize": {
      "en": "Text size",
      "text": "字級"
    },
    "focus": {
      "en": "Focus mode",
      "text": "專注模式"
    },
    "exitFocus": {
      "en": "Show the demo",
      "text": "顯示示範"
    },
    "prev": {
      "en": "Previous",
      "text": "上一期"
    },
    "next": {
      "en": "Next",
      "text": "下一期"
    },
    "moreTips": {
      "en": "Previous and next tips",
      "text": "上一期和下一期"
    },
    "seriesStats": {
      "en": "(views, likes, bookmarks) => `The series on X: ${views} views, ${likes} likes, ${bookmarks} bookmarks`",
      "text": "(views, likes, bookmarks) => `系列在 X 上的數據：合計 ${views} 次瀏覽、${likes} 個喜歡、${bookmarks} 個書籤`"
    },
    "reads": {
      "en": "reads",
      "text": "瀏覽"
    },
    "likesSaves": {
      "en": "likes & saves",
      "text": "喜歡與收藏"
    },
    "follow": {
      "en": "Follow @kubai087 on X",
      "text": "在 X 上追蹤 @kubai087"
    },
    "readsAcross": {
      "en": "(n) => `Reads across ${n} posts`",
      "text": "(n) => `${n} 篇貼文合計瀏覽`"
    },
    "likesCount": {
      "en": [
        "",
        " likes"
      ],
      "text": [
        "",
        " 個喜歡"
      ]
    },
    "savesCount": {
      "en": [
        "",
        " saves"
      ],
      "text": [
        "",
        " 個收藏"
      ]
    },
    "improve": {
      "en": "Improve translation",
      "text": "改進翻譯"
    },
    "improveNote": {
      "en": "To suggest corrections, download the text of this language, edit it, and send the file to {email}.",
      "text": "如需修正翻譯，請下載本語言的文字，修改後寄至 {email}。"
    },
    "improveDone": {
      "en": "Download complete. Please send your corrections to i@kubai.design.",
      "text": "已下載。修改後請寄至 i@kubai.design。"
    }
  },
  "reader": {
    "size": {
      "en": "Text size",
      "text": "字級"
    },
    "sizes": {
      "en": [
        "Default",
        "Large",
        "Larger"
      ],
      "text": [
        "標準",
        "大",
        "特大"
      ]
    },
    "marks": {
      "en": "Selected text",
      "text": "選取的文字"
    },
    "highlight": {
      "en": "Highlight",
      "text": "螢光標記"
    },
    "unhighlight": {
      "en": "Remove highlight",
      "text": "取消螢光標記"
    },
    "marked": {
      "en": "Highlighted and saved. Find your highlights under Saved",
      "text": "已加上螢光標記並收藏，可在「我的收藏」中查看所有標記"
    },
    "unmarked": {
      "en": "Highlight removed",
      "text": "已取消螢光標記"
    },
    "copy": {
      "en": "Copy",
      "text": "複製"
    },
    "quote": {
      "en": "Quote",
      "text": "引用"
    },
    "copied": {
      "en": "Copied",
      "text": "已複製"
    },
    "quoted": {
      "en": "Quote copied",
      "text": "已複製引用"
    },
    "copyFailed": {
      "en": "Copy failed",
      "text": "複製失敗"
    },
    "colon": {
      "en": ": ",
      "text": "："
    },
    "quoteText": {
      "en": "(words, title, url) => `“${words}”\\n— ${title}\\n${url}`",
      "text": "(words, title, url) => `「${words}」\\n—— ${title}\\n${url}`"
    }
  },
  "account": {
    "saved": {
      "en": "Saved",
      "text": "已收藏"
    },
    "unsaved": {
      "en": "Removed from saved",
      "text": "已取消收藏"
    },
    "save": {
      "en": "Save",
      "text": "收藏"
    },
    "savedState": {
      "en": "Saved",
      "text": "已收藏"
    },
    "unsave": {
      "en": "Remove from saved",
      "text": "取消收藏"
    },
    "tooMany": {
      "en": "Too many requests. Try again in a moment.",
      "text": "操作過於頻繁，請稍後再試"
    },
    "saveFailed": {
      "en": "Could not save. Try again in a moment.",
      "text": "無法收藏，請稍後再試"
    },
    "going": {
      "en": "(p) => `Going to ${p}…`",
      "text": "(p) => `正在前往 ${p}…`"
    },
    "signedOut": {
      "en": "Signed out",
      "text": "已登出"
    },
    "account": {
      "en": "(name) => `Account: ${name}`",
      "text": "(name) => `帳號：${name}`"
    },
    "signIn": {
      "en": "Sign in",
      "text": "登入"
    },
    "signInTitle": {
      "en": "Sign in to vibedesign.tips",
      "text": "登入 vibedesign.tips"
    },
    "signInLeads": {
      "en": {
        "save": "Signing in saves this tip.",
        "mark": "Signing in keeps this highlight and saves this tip.",
        "install": "Sign in to copy the install prompt.",
        "saved": "Sign in to see the tips you saved."
      },
      "text": {
        "save": "登入後會自動收藏這期技巧。",
        "mark": "登入後會保留這段螢光標記，並收藏這期技巧。",
        "install": "登入後即可複製安裝提示詞。",
        "saved": "登入後即可查看你收藏的技巧。"
      }
    },
    "expiredTitle": {
      "en": "Your sign-in has expired",
      "text": "登入已過期"
    },
    "expiredLeads": {
      "en": {
        "save": "Please sign in again. This tip will then be saved.",
        "bundle": "Please sign in again to keep downloading the Skill.",
        "archive": "Please sign in again to keep downloading the full package.",
        "install": "Please sign in again to copy the install prompt.",
        "rename": "Please sign in again to edit your name."
      },
      "text": {
        "save": "請重新登入，登入後會自動收藏這期技巧。",
        "bundle": "請重新登入，登入後即可繼續下載 Skill。",
        "archive": "請重新登入，登入後即可繼續下載完整內容。",
        "install": "請重新登入，登入後即可複製安裝提示詞。",
        "rename": "請重新登入，登入後即可修改名稱。"
      }
    },
    "signInWith": {
      "en": "(p) => `Sign in with ${p}`",
      "text": "(p) => `使用 ${p} 登入`"
    },
    "lastUsed": {
      "en": "Last used",
      "text": "上次使用"
    },
    "recommended": {
      "en": "Recommended",
      "text": "推薦"
    },
    "inAppNote": {
      "en": "(github) => `Google sign-in continues in your browser. If it doesn’t open, choose “Open in browser” from this app’s ··· menu${github ? ', or sign in with GitHub' : ''}.`",
      "text": "(github) => `Google 登入會在系統瀏覽器中繼續。如果沒有開啟，請在本應用程式的 ··· 選單中選擇「在瀏覽器中開啟」${github ? '，或改用 GitHub 登入' : ''}。`"
    },
    "openingBrowser": {
      "en": "Opening your browser…",
      "text": "正在開啟瀏覽器…"
    },
    "browserNotOpened": {
      "en": "Could not open your browser",
      "text": "無法開啟瀏覽器"
    },
    "member": {
      "en": "(n) => `Early member No. ${n}`",
      "text": "(n) => `第 ${n} 位早期使用者`"
    },
    "plateTitle": {
      "en": "Early member plate",
      "text": "早期使用者紀念銘牌"
    },
    "plateNote": {
      "en": "(max, n) => `A keepsake for the first ${max} people to support vibedesign.tips. You are No. ${n}.`",
      "text": "(max, n) => `送給前 ${max} 位支持 vibedesign.tips 的使用者。你是第 ${n} 位。`"
    },
    "plateOpen": {
      "en": "Click to see the member list",
      "text": "點選查看名單"
    },
    "membersOpen": {
      "en": "See the member list",
      "text": "查看早期使用者名單"
    },
    "membersTitle": {
      "en": [
        "The first ",
        " members"
      ],
      "text": [
        "前 ",
        " 位早期使用者"
      ]
    },
    "membersLead": {
      "en": "(count, max) => (count >= max ? `All ${max} places are taken` : `${count} taken, ${max - count} left`)",
      "text": "(count, max) => (count >= max ? `${max} 個名額已滿` : `已有 ${count} 位，還剩 ${max - count} 個名額`)"
    },
    "membersYou": {
      "en": "(n) => `You are No. ${n}`",
      "text": "(n) => `你是第 ${n} 位`"
    },
    "membersSelf": {
      "en": "You",
      "text": "你"
    },
    "membersShow": {
      "en": "Show me on the list",
      "text": "在名單上顯示我"
    },
    "membersShown": {
      "en": "You are on the list",
      "text": "已在名單上顯示"
    },
    "membersHidden": {
      "en": "You are off the list",
      "text": "已從名單上隱藏"
    },
    "membersPrivate": {
      "en": "Only you can see this",
      "text": "未公開，僅你可見"
    },
    "membersJoin": {
      "en": "Sign in to take a place",
      "text": "登入以取得名額"
    },
    "membersAnonymous": {
      "en": "Anonymous kind soul",
      "text": "不願具名的熱心網友"
    },
    "membersFailed": {
      "en": "Could not load the list. Try again in a moment.",
      "text": "無法載入名單，請稍後再試"
    },
    "getAll": {
      "en": "Get all tips",
      "text": "取得全部技巧"
    },
    "getAllTitle": {
      "en": "Sign in to vibedesign.tips",
      "text": "登入 vibedesign.tips"
    },
    "perks": {
      "en": [
        [
          "download",
          "Download every tip in one go"
        ],
        [
          "save",
          "Save the tips you like and highlight what matters"
        ],
        [
          "badge",
          "Join early and get an exclusive badge"
        ]
      ],
      "text": [
        [
          "download",
          "一鍵下載所有技巧"
        ],
        [
          "save",
          "收藏實用的技巧，標記重點內容"
        ],
        [
          "badge",
          "成為早期使用者，獲得專屬徽章"
        ]
      ]
    },
    "consent": {
      "en": [
        "Free, keeps only your name and avatar. Signing in accepts the ",
        "Privacy Policy",
        "."
      ],
      "text": [
        "免費，僅儲存名稱和大頭貼。登入即表示同意",
        "《隱私權政策》",
        "。"
      ]
    },
    "separate": {
      "en": "Accounts from different sign-in methods don’t share saves",
      "text": "不同登入方式的帳號彼此獨立，收藏不會互通"
    },
    "accountMenu": {
      "en": "Account",
      "text": "帳號"
    },
    "providerAccount": {
      "en": "(p) => `Signed in with ${p}`",
      "text": "(p) => `已透過 ${p} 登入`"
    },
    "mySaved": {
      "en": "Saved",
      "text": "我的收藏"
    },
    "signOut": {
      "en": "Sign out",
      "text": "登出"
    },
    "editName": {
      "en": "Edit name",
      "text": "修改名稱"
    },
    "nameField": {
      "en": "Name",
      "text": "名稱"
    },
    "nameSaved": {
      "en": "Name updated",
      "text": "名稱已更新"
    },
    "nameInvalid": {
      "en": "(max) => `Use 1 to ${max} characters`",
      "text": "(max) => `名稱須為 1–${max} 個字元`"
    },
    "nameFailed": {
      "en": "Could not change the name. Try again in a moment.",
      "text": "無法修改名稱，請稍後再試"
    },
    "closed": {
      "en": "Sign-in is not open yet",
      "text": "登入功能尚未開放"
    },
    "savedSignIn": {
      "en": "Sign in to see the tips you saved",
      "text": "登入後即可查看你收藏的技巧"
    },
    "savedCount": {
      "en": "(n) => `${n} saved ${n === 1 ? 'tip' : 'tips'}`",
      "text": "(n) => `已收藏 ${n} 個`"
    },
    "seeAll": {
      "en": "See all",
      "text": "查看全部"
    },
    "loginError": {
      "en": "Sign-in did not work. Please try again.",
      "text": "登入失敗，請再試一次"
    },
    "loginCancelled": {
      "en": "Sign-in cancelled",
      "text": "已取消登入"
    },
    "loginLimited": {
      "en": "Too many sign-ins. Try again in a moment.",
      "text": "登入過於頻繁，請稍後再試"
    },
    "loginBusy": {
      "en": "Sign-in with X has reached its limit for now. Please sign in another way.",
      "text": "X 登入暫時達到使用上限，請改用其他登入方式"
    },
    "loginSaved": {
      "en": "Signed in, and this tip is saved",
      "text": "已登入，並收藏了這期技巧"
    },
    "signedIn": {
      "en": "(name) => `Signed in as ${name}`",
      "text": "(name) => `已登入：${name}`"
    },
    "colon": {
      "en": ": ",
      "text": "："
    },
    "downloads": {
      "en": "Download everything",
      "text": "打包下載"
    },
    "downloading": {
      "en": "Preparing…",
      "text": "準備中…"
    },
    "downloadFailed": {
      "en": "Could not download. Try again in a moment.",
      "text": "無法下載，請稍後再試"
    },
    "skillTile": {
      "en": "Skill",
      "text": "Skill"
    },
    "skillTileNote": {
      "en": "Everything",
      "text": "所有內容"
    },
    "skillZip": {
      "en": "Or download the Skill as a ZIP",
      "text": "或下載 Skill 的 ZIP 檔案"
    },
    "skillVersion": {
      "en": "(v) => `Version ${v}`",
      "text": "(v) => `版本 ${v}`"
    },
    "changelog": {
      "en": "Changelog",
      "text": "更新紀錄"
    },
    "changelogTitle": {
      "en": "Skill changelog",
      "text": "Skill 更新紀錄"
    },
    "changelogLead": {
      "en": "Every release of the Skill that holds everything. Each tip’s own Skill is on its page.",
      "text": "收錄所有內容的 Skill 每次發布的變更。單期的 Skill 請在各期貼文中下載。"
    },
    "changelogAdded": {
      "en": "Added",
      "text": "新增"
    },
    "changelogUpdated": {
      "en": "Updated",
      "text": "更新"
    },
    "installCopied": {
      "en": "Install prompt copied. Give it to your agent",
      "text": "已複製安裝提示詞，傳給你的 Agent 即可"
    },
    "installPrompt": {
      "en": "(guide, mirror) => [\n        'Please install the kubai-design-tips Skill for me (every design tip from Vibe Design Tips), so it works in every project and can be updated later.',\n        '',\n        `Follow the steps in ${guide}`,\n        `If GitHub cannot be reached, use ${mirror} instead.`,\n        '',\n        'If it is already installed, follow the update steps there. Then tell me the version and where you installed it.',\n      ].join('\\n')",
      "text": "(guide, mirror) => [\n    '請幫我安裝 kubai-design-tips 這個 Skill（Vibe Design Tips 的所有設計技巧），讓它在所有專案中都能使用，之後也能更新。',\n    '',\n    `請依照 ${guide} 中的步驟操作。`,\n    `如果無法開啟 GitHub，請改用 ${mirror} 。`,\n    '',\n    '如果已經安裝過，請依照其中的更新步驟操作。完成後告訴我版本號和安裝位置。',\n  ].join('\\n')"
    },
    "copyFailed": {
      "en": "Could not copy. Try again in a moment.",
      "text": "無法複製，請稍後再試"
    },
    "skillStarted": {
      "en": "Download started",
      "text": "已開始下載"
    },
    "archiveTile": {
      "en": "Full package",
      "text": "完整內容"
    },
    "archiveTileNote": {
      "en": "Videos and posts",
      "text": "影片和貼文"
    },
    "archiveNew": {
      "en": "(n) => `Or only the ${n} ${n === 1 ? 'tip' : 'tips'} added or updated since your last download`",
      "text": "(n) => `或只下載上次之後新增或更新的 ${n} 期`"
    },
    "archiveUpToDate": {
      "en": "You already have every tip in the full package",
      "text": "完整包裡的內容你都已經下載過了"
    },
    "archiveStarted": {
      "en": "(size) => `Downloading the full package (${size}). Each tip has its video and its text in Chinese and English.`",
      "text": "(size) => `已開始下載完整內容（${size}），每期包含影片和中英文貼文`"
    },
    "close": {
      "en": "Close",
      "text": "關閉"
    },
    "community": {
      "en": "Join the community",
      "text": "加入社群"
    },
    "communityKind": {
      "en": "Paid community",
      "text": "付費社群"
    },
    "communityTitle": {
      "en": [
        "Join Vibe Design ",
        ""
      ],
      "text": [
        "加入 Vibe Design ",
        ""
      ]
    },
    "communityLead": {
      "en": "Good design friends, waiting for you to come and chat",
      "text": "一群用心做設計的朋友，等你來聊聊"
    },
    "communityFree": {
      "en": "Every tutorial on this site is free for good, with careful updates to come. The community offers no extra lessons, but joining lets you:",
      "text": "本站所有教學永久免費，持續高品質更新；社群裡不會提供額外課程，但加入後你可以："
    },
    "communityPerks": {
      "en": [
        [
          "support",
          "Keep the free tips coming, and give me a little boost ✨"
        ],
        [
          "ask",
          "Ask Kubai anytime for free icon and product design advice"
        ],
        [
          "share",
          "More everyday design knowledge and resources"
        ],
        [
          "talk",
          "Meet great people building products, content and design"
        ],
        [
          "treat",
          "Buy Shubing the cat a can of treats 🐱"
        ]
      ],
      "text": [
        [
          "support",
          "支持免費教學持續更新，給我加點動力 ✨"
        ],
        [
          "ask",
          "隨時向枯白提問，獲得免費 icon/產品設計建議"
        ],
        [
          "share",
          "獲得更多日常設計知識/素材分享"
        ],
        [
          "talk",
          "認識一起做產品/內容/設計的優秀夥伴"
        ],
        [
          "treat",
          "為薯餅小貓買一個罐罐 🐱"
        ]
      ]
    },
    "communityCat": {
      "en": [
        "Hi! I’m ",
        "Shubing",
        ". Thanks for the treats~"
      ],
      "text": [
        "你好！我是",
        "薯餅",
        "，謝謝你的罐罐～"
      ]
    },
    "communityCurrency": {
      "en": "CN¥",
      "text": "CN¥"
    },
    "communityEarly": {
      "en": "Early bird",
      "text": "早鳥價"
    },
    "communityWas": {
      "en": "Regular price ",
      "text": "原價 "
    },
    "communityEnds": {
      "en": "(date) => `Ends ${date}`",
      "text": "(date) => `${date}截止`"
    },
    "communityDaysLeft": {
      "en": "(n) => `${n} ${n === 1 ? 'day' : 'days'} left`",
      "text": "(n) => `還剩 ${n} 天`"
    },
    "communityLastDay": {
      "en": "Ends today",
      "text": "今天截止"
    },
    "communityOnce": {
      "en": "Pay once, yours to keep",
      "text": "一次付費，永久有效"
    },
    "communityScan": {
      "en": "Scan with WeChat to add me",
      "text": "用 WeChat 掃描 QR 碼加我好友"
    },
    "communityHow": {
      "en": "Add Kubai on WeChat, send the payment once accepted, and you’ll be invited to the group",
      "text": "用 WeChat 掃描並加入枯白，通過好友申請後轉帳，收到款項後會邀請你加入群組"
    },
    "communityHowTouch": {
      "en": "Press and hold to save the code, then open it from your photos in WeChat’s Scan to add Kubai. Once accepted, send the payment and you’ll be invited to the group",
      "text": "長按儲存 QR 碼，在 WeChat 的「掃一掃」中從相簿選取圖片加入枯白，通過好友申請後轉帳，收到款項後會邀請你加入群組"
    },
    "communityQr": {
      "en": "WeChat QR code",
      "text": "WeChat QR 碼"
    }
  },
  "tags": {
    "motion": {
      "en": "Motion",
      "text": "動態"
    },
    "interaction": {
      "en": "Interaction",
      "text": "互動"
    },
    "components": {
      "en": "Components",
      "text": "元件"
    },
    "type": {
      "en": "Type & Layout",
      "text": "排版與版面"
    },
    "effects": {
      "en": "Effects",
      "text": "視覺效果"
    }
  },
  "stats": {
    "views": {
      "en": "views",
      "text": "瀏覽"
    },
    "likes": {
      "en": "likes",
      "text": "喜歡"
    },
    "bookmarks": {
      "en": "bookmarks",
      "text": "書籤"
    },
    "replies": {
      "en": "replies",
      "text": "回覆"
    },
    "source": {
      "en": "Post on X",
      "text": "X 原始貼文"
    }
  },
  "titles": {
    "021-ring-cards": {
      "en": "Ring cards with depth and a fluid gradient",
      "text": "景深環形卡片與流體漸層"
    },
    "020-choice-controls": {
      "en": "Diagnosing and fixing choice controls",
      "text": "選擇控制項的診斷與改造"
    },
    "019-scroll-cards": {
      "en": "Five card interactions driven by scrolling",
      "text": "捲動驅動的五種卡片互動"
    },
    "018-holo-card": {
      "en": "Holographic cards that tilt and turn over",
      "text": "會傾斜和翻面的雷射卡片"
    },
    "017-loading-states": {
      "en": "Diagnosing and fixing loading states",
      "text": "載入狀態的診斷與改造"
    },
    "016-toast-or-notification": {
      "en": "Toasts or notifications: how to choose",
      "text": "Toast 與通知的選擇與改造"
    },
    "015-ui-continuity": {
      "en": "Diagnosing and fixing UI continuity",
      "text": "介面連續性的診斷與改造"
    },
    "014-card-delete": {
      "en": "Four ways for a deleted card to disappear",
      "text": "卡片刪除的四種消失效果"
    },
    "013-shockwave-glow": {
      "en": "A shockwave halo",
      "text": "衝擊波光環效果"
    },
    "012-message-bubbles": {
      "en": "Material and motion for message bubbles",
      "text": "訊息氣泡的材質與動態"
    },
    "011-easing-curves": {
      "en": "Choosing easing curves by situation",
      "text": "依情境選擇緩動曲線"
    },
    "010-liquid-glass": {
      "en": "Liquid glass",
      "text": "液態玻璃材質"
    },
    "009-overlays": {
      "en": "Rules for choosing an overlay",
      "text": "浮層元件的選用規則"
    },
    "008-wiki-layout": {
      "en": "A wiki layout for desktop and mobile",
      "text": "兼顧電腦和行動裝置的 Wiki 版面"
    },
    "007-type-switches": {
      "en": "CSS for mixed Chinese and English type",
      "text": "中英文排版的 CSS 設定"
    },
    "006-book-cards": {
      "en": "Cards that open like a book on hover",
      "text": "懸停時像書一樣翻開的卡片"
    },
    "005-drag-ripple": {
      "en": "Drag to reorder, with items making way",
      "text": "帶避讓動態的拖曳排序"
    },
    "004-continuous-corners": {
      "en": "Nested corners and continuous corners",
      "text": "遞進式圓角與連續曲率圓角"
    },
    "003-ascii-dither": {
      "en": "ASCII and dither effects",
      "text": "ASCII 與像素抖色效果"
    },
    "002-cascade-menu": {
      "en": "Safe areas and delays for cascading menus",
      "text": "階層式選單的安全區域與延遲"
    },
    "001-skeuomorphic-buttons": {
      "en": "Skeuomorphic buttons that press in",
      "text": "有按壓回饋的擬物按鈕"
    }
  },
  "tips": {
    "001-skeuomorphic-buttons": {
      "en": {
        "summary": "Tactile skeuomorphic buttons: five variants, five material layers, and lighting that changes on hover and press. For dashboards and tools.",
        "notes": "<p>A flat button usually just turns slightly darker when pressed, which is barely visible during a quick click. A skeuomorphic button sinks when pressed, with its position, gradient and shadows changing together, so the user can tell the press registered. The key points are these five:</p>\n        <ol>\n        <li><strong>Five variants</strong>: For dashboards, editors and settings pages with many buttons and few colors, where primary and secondary can only be told apart by light, shade and material. From strongest to weakest: primary is a dark slate key, secondary a raised white key, tertiary a light gray key, ghost has no face at rest, and text is just a label with a thin underline. Use only one primary per area.</li>\n        <li><strong>Five material layers</strong>: The three filled variants are built from the same five layers: a gradient face 6–8% lighter at the top, a 1px border one step darker than the bottom of the gradient, a white highlight along the top, a dark line along the bottom, and a two-layer shadow made of a contact shadow and a soft drop shadow. The variants differ only in their values, so define the five layers as one set of tokens and let each variant assign its own.</li>\n        <li><strong>Hover and press</strong>: On hover the face gets one step lighter and the drop shadow grows. On press the button moves down 1px, the gradient flips, the drop shadow tightens until it almost touches the surface, and the top highlight becomes an inner shadow. The rest and pressed states need the same number of inset shadow layers, with transparent shadows filling any gap, for the shadows to change smoothly.</li>\n        <li><strong>Light and color</strong>: The light source is fixed straight above, so the highlight is always at the top and the dark line always at the bottom, and the whole set looks as if it sits in the same space. Use only neutral grays, no brand colors, and separate the variants by light and shade; no gloss, outer glow or large blurs either.</li>\n        <li><strong>Scale with the label</strong>: Height, padding, radius, border, and the offset and blur of every shadow layer are all written as multiples of the unit u = label size / 14. With a 14px label u = 1px and the button is 40px tall; with a 16px label u ≈ 1.14px, the button is about 45.7px tall, and the shadows grow in the same proportion.</li>\n        </ol>\n        <h2>Parameters</h2>\n        <dl class=\"params\">\n        <dt>Size</dt><dd>Label 14px; height 40px; radius 10px; horizontal padding 18px</dd>\n        <dt>Pressed</dt><dd>Moves down 1px; drop shadow collapses to 0 1px 1px</dd>\n        <dt>Timing</dt><dd>Transform 120ms; shadows 140ms; colors 160ms</dd>\n        </dl>\n        <p>The included prompt restyles the project’s existing button component first, keeping its API and accessibility settings; it creates a new one only if the project has no button component.</p>"
      },
      "text": {
        "summary": "一組有點擊手感的擬物按鈕：五個層級、五層材質，以及懸停和按下時的光影變化，適合後台和工具類產品。",
        "notes": "<p>扁平按鈕按下時通常只是顏色稍微變深，快速點擊時幾乎看不出來；擬物按鈕按下時會下沉，位置、漸層和陰影同時變化，使用者能確認這一下按到了。要點有以下五條：</p>\n        <ol>\n        <li><strong>五個層級</strong>：適合按鈕多、顏色少的後台、編輯器和設定頁，主次只能靠明暗和材質區分。由強到弱為 primary 深石板色按鍵、secondary 凸起的白色按鍵、tertiary 淺灰按鍵、ghost 平時沒有底色、text 只有文字和細底線；同一區域只放一個 primary。</li>\n        <li><strong>五層材質</strong>：有底色的三個層級都由同樣的五層構成：頂部淺 6–8% 的漸層面，比漸層底部深一階的 1px 邊框，頂部一道白色亮光，底部一道暗線，以及貼地陰影加柔和投影兩層。層級之間只有數值不同，五層定義成一組 token，由各層級分別賦值。</li>\n        <li><strong>懸停與按下</strong>：懸停時按鍵面亮一階，投影變大。按下時下移 1px，漸層上下翻轉，投影收到幾乎貼地，頂部亮光變成一道內陰影。靜止和按下的內陰影層數要相同，不足的以透明陰影補齊，陰影才會平順過渡。</li>\n        <li><strong>光源與顏色</strong>：光源固定在正上方，亮光總在頂部、暗線總在底部，整組按鈕看起來在同一個空間裡。只用中性灰，不用品牌色，層級靠明暗區分；也不用鏡面亮光、外光暈和大範圍模糊。</li>\n        <li><strong>依字級縮放</strong>：高度、內距、圓角、邊框和每層陰影的偏移、模糊，都寫成單位 u = 字級 / 14 的倍數。14px 文字時 u = 1px，按鈕高 40px；16px 文字時 u ≈ 1.14px，按鈕高約 45.7px，陰影依相同比例放大。</li>\n        </ol>\n        <h2>參數</h2>\n        <dl class=\"params\">\n        <dt>尺寸</dt><dd>文字 14px；高 40px；圓角 10px；左右內距 18px</dd>\n        <dt>按下</dt><dd>下移 1px；投影收為 0 1px 1px</dd>\n        <dt>時長</dt><dd>位移 120ms；陰影 140ms；顏色 160ms</dd>\n        </dl>\n        <p>附帶的提示詞會優先改造專案中現有的按鈕元件，保留原有的 API 和無障礙設定；專案中沒有按鈕元件時，才新建一個。</p>"
      }
    },
    "002-cascade-menu": {
      "en": {
        "summary": "A safe triangle and three delays for cascading menus, so a diagonal move toward a submenu does not switch or close it by mistake.",
        "notes": "<p>On its way diagonally from a parent menu to a submenu, the pointer inevitably crosses the rows below. A plain menu switches to whichever row the pointer crosses, the submenu disappears, and the user has to go back and open it again. Four rules solve this:</p>\n        <ol>\n        <li><strong>Safe triangle</strong>: Used while a submenu is open and the pointer is moving toward it. Take the pointer’s previous position as one corner and connect it to the top and bottom corners of the submenu’s near side to form a triangle. While the pointer is inside, the rows it crosses do not highlight or open their own submenus; only when it leaves the triangle does the menu switch to the current row.</li>\n        <li><strong>Switch delay</strong>: If the pointer rests on a row inside the triangle, the user wants that row. After it stays there for more than 1.2 seconds, the menu switches to that row, so the submenu does not stay unchanged for too long.</li>\n        <li><strong>Open delay</strong>: For a pointer sweeping quickly down a menu. A submenu opens only after 220ms of hover and is canceled if the pointer leaves earlier, so a string of submenus does not open one after another; a tap on a touchscreen takes effect immediately.</li>\n        <li><strong>Close delay</strong>: For a pointer that slips slightly past the menu’s edge. The menu closes only 360ms after the pointer leaves, and stays as it is if the pointer comes back in time; a click outside the menu closes it immediately.</li>\n        </ol>\n        <p>Also, row highlighting is controlled by component state, not CSS <code>:hover</code>; otherwise the rows crossed inside the triangle still light up even when the menu does not switch.</p>\n        <p>The included prompt adds these rules to the project’s existing menu component, keeping its API and keyboard support; it creates a new one only if the project has no menu component.</p>"
      },
      "text": {
        "summary": "階層式選單的安全三角區和三種延遲，讓指標斜向移往子選單時，子選單不會誤切換或突然關閉。",
        "notes": "<p>指標從父選單斜向移往子選單時，難免經過下面幾列。一般選單經過哪一列就切換到哪一列，子選單隨之消失，使用者只好退回去重新開啟。解決辦法有以下四條：</p>\n        <ol>\n        <li><strong>安全三角區</strong>：用於子選單已開啟、指標正朝它移動的時候。以指標上一刻的位置為頂點，連到子選單靠近一側的上下兩個角，圍成一個三角形；指標在三角形內，經過的列不反白，也不開啟自己的子選單，離開三角形才切換到目前這一列。</li>\n        <li><strong>切換延遲</strong>：指標停在三角形裡的某一列上，代表使用者想選這一列。停留超過 1.2 秒，選單就切換到這一列，子選單不會遲遲不變。</li>\n        <li><strong>開啟延遲</strong>：用於指標快速劃過一列選單的情況。懸停 220ms 後才開啟子選單，提前離開就取消，不會接連開啟一串子選單；觸控螢幕上點擊則立即生效。</li>\n        <li><strong>關閉延遲</strong>：用於指標稍稍移出選單邊緣的情況。離開選單 360ms 後才關閉，及時移回就維持原樣；點擊選單外的地方則立即關閉。</li>\n        </ol>\n        <p>另外，列的反白由元件狀態控制，不用 CSS 的 <code>:hover</code>，否則即使選單沒有切換，三角區裡經過的列仍會亮起。</p>\n        <p>附帶的提示詞會把這套規則加入專案現有的選單元件，保留原有的 API 和鍵盤操作；專案中沒有選單元件時，才新建一個。</p>"
      }
    },
    "003-ascii-dither": {
      "en": {
        "summary": "ASCII and Dither effects for images and videos on login pages, websites or cards, with a strength you can adjust at any time.",
        "notes": "<p>ASCII and Dither redraw an image as characters or a pixel texture by brightness, keeping its light and dark structure and dropping the photo’s detail. Every parameter can be adjusted, so the same image can serve as the main visual or recede into the background as a texture. The key points are these five:</p>\n        <ol>\n        <li><strong>ASCII</strong>: Suits a terminal or code look, such as the login page of a developer tool. The image is cut into a grid, and each cell is replaced by a character according to its brightness, from “.” to “@” as it gets denser; size is the font size, spacing is how dense the grid is, and sampling strength is the contrast.</li>\n        <li><strong>Dither</strong>: Suits the look of halftone print or pixel grain. The image is cut into pixel blocks, and a 4×4 Bayer matrix serves as the thresholds that reduce each color to a few levels, which blend into intermediate tones from a distance; size is the pixel block, spacing is the scale of the texture, and the higher the sampling strength, the fewer the color levels and the heavier the grain.</li>\n        <li><strong>Mask</strong>: Applies to both effects. A vertical gradient laid over the image pushes it back, so the effect reads more as texture than as noise; when the effect gets in the way of the text on top, raise the mask first.</li>\n        <li><strong>Sample tones</strong>: ASCII only. It decides whether characters are drawn in the shadows or the highlights; choose by the tones where the subject sits. In a city at night the subject is the lights, so sample the highlights; for a dark product photo on white, sample the shadows.</li>\n        <li><strong>Color</strong>: Keep the original colors, or pick one of five palettes. The image’s light and dark are first mapped onto that palette before the effect is generated, so different images keep a consistent style.</li>\n        </ol>\n        <h2>Parameters</h2>\n        <dl class=\"params\">\n        <dt>ASCII</dt><dd>Mask 90; sample tones Shadows; sampling strength 100; size 37; spacing 0</dd>\n        <dt>Dither</dt><dd>Mask 88; sampling strength 100; size 15; spacing 0</dd>\n        </dl>\n        <p>The included prompt first confirms which image or video to process, then generates the effect for it and adds a panel beside it for adjusting the parameters live.</p>"
      },
      "text": {
        "summary": "為登入頁、官網或卡片中的圖片和影片加上 ASCII 與 Dither 效果，效果強弱可以隨時調整。",
        "notes": "<p>ASCII 和 Dither 依亮度把圖片重新畫成字元或像素紋理，保留明暗結構，去掉照片的細節；參數都可以調整，同一張圖既能當主視覺，也能退到背景裡當紋理。要點有以下五條：</p>\n        <ol>\n        <li><strong>ASCII</strong>：適合終端機、程式碼一類的質感，例如開發者工具的登入頁。把畫面切成網格，每格依亮度換成一個字元，從「.」到「@」越來越密；大小是字級，間距是格子疏密，取樣強度是明暗對比。</li>\n        <li><strong>Dither</strong>：適合印刷網點或像素顆粒的質感。把畫面切成像素塊，以 4×4 的 Bayer 矩陣作為閾值，把每種顏色壓成幾階，遠看混成中間的灰階；大小是像素塊，間距是紋理的尺度，取樣強度越高，顏色階數越少，顆粒感越重。</li>\n        <li><strong>遮罩</strong>：兩種效果都適用。在畫面上疊一層垂直漸層，讓畫面退後，效果更像紋理而不是雜訊；效果干擾到上層文字時，先調高遮罩。</li>\n        <li><strong>取樣區域</strong>：只用於 ASCII，決定字元畫在暗部還是亮部，依畫面主體所在的明暗選擇。城市夜景的主體是燈光，取樣亮部；白底上的深色產品照片，取樣暗部。</li>\n        <li><strong>色調</strong>：可以保留原色，也可以從五組配色中選一組，先把圖片的明暗對應到這組顏色上，再產生效果，讓不同圖片的風格保持一致。</li>\n        </ol>\n        <h2>參數</h2>\n        <dl class=\"params\">\n        <dt>ASCII</dt><dd>遮罩 90；取樣暗部；取樣強度 100；大小 37；間距 0</dd>\n        <dt>Dither</dt><dd>遮罩 88；取樣強度 100；大小 15；間距 0</dd>\n        </dl>\n        <p>附帶的提示詞會先確認要處理哪張圖片或哪段影片，再為它產生效果，並在旁邊加上一個可以即時調整的參數面板。</p>"
      }
    },
    "004-continuous-corners": {
      "en": {
        "summary": "How to work out nested corner radii level by level, and when to switch to continuous corners, so corners on cards and forms look neater.",
        "notes": "<p>Take a card with a 16px radius and 8px padding: if the button inside also has a 16px radius, the gap between the two borders is wider at the corner than along the straight edges, and the button does not look like it fits the card. Where a larger radius meets a straight edge, a crease also shows. Four rules:</p>\n        <ol>\n        <li><strong>Even inset</strong>: For places with an inner and an outer layer of rounded corners, such as forms, nested cards and dialogs. Calculate every layer as “inner radius = outer radius − padding”, so the inner and outer corners share a center and the gap at the corner matches the gap along the straight edges. With a card radius of 16 and padding of 8, the button inside gets a radius of 8.</li>\n        <li><strong>Several levels</strong>: With three or more levels, calculate from the outside in, one level at a time. For a dialog with radius 32 and padding 16, the panels and buttons inside get 16; a tag inset by another 8 inside a panel gets 8. Elements at the same level share one radius, and no radius goes below 4.</li>\n        <li><strong>Pills and circles</strong>: Pill-shaped and circular elements nested in a container are left out of the calculation and always stay fully round.</li>\n        <li><strong>Continuous corners</strong>: For large radii where a crease shows at the join, or when you want something close to the look of iOS corners. A plain rounded corner changes curvature abruptly where it meets the straight edge; a continuous corner (superellipse) increases the curvature gradually, for a smoother transition. Write it as <code>border-radius: 32px; corner-shape: superellipse(1.25);</code></li>\n        </ol>\n        <p>Also, <code>corner-shape</code> is currently supported only in Chrome and Edge 139 and later; Safari and Firefox fall back to plain rounded corners on their own, with nothing extra to handle.</p>\n        <p>The included prompt recalculates the radii of the interface you specify, from the outside in; if the project has radius tokens, it changes the tokens directly.</p>"
      },
      "text": {
        "summary": "巢狀圓角如何逐層計算，以及什麼時候改用連續曲率圓角，讓卡片和表單的轉角更規整。",
        "notes": "<p>一張圓角 16px、內距 8px 的卡片，裡面的按鈕也用 16px 圓角，轉角處兩條邊框的間距就會比直邊處寬，按鈕看起來沒有貼合卡片；較大的圓角接直邊的地方，還會有一道折痕。做法有以下四條：</p>\n        <ol>\n        <li><strong>等距內縮</strong>：用於表單、巢狀卡片、對話框這類有內外兩層圓角的地方。每一層都依「內圓角 = 外圓角 − 間距」計算，內外共用一個圓心，轉角處的間距才會和直邊處相同。卡片圓角 16、內距 8，裡面的按鈕圓角就是 8。</li>\n        <li><strong>多層巢狀</strong>：三層以上時，由外往內逐層計算。對話框圓角 32、內距 16，內部面板和按鈕為 16；面板裡再內縮 8 放一個標籤，標籤為 8。同一層級的元素共用一個圓角，最小不低於 4。</li>\n        <li><strong>膠囊和圓形</strong>：巢狀在容器裡的膠囊形和圓形元素不參與計算，始終保持完整的圓形。</li>\n        <li><strong>連續曲率圓角</strong>：用於圓角較大、連接處看得出折痕，或想要接近 iOS 圓角觀感的情況。一般圓角在接直邊處曲率突然變化，連續曲率圓角（超橢圓）讓曲率逐漸增大，過渡更順。寫法是 <code>border-radius: 32px; corner-shape: superellipse(1.25);</code></li>\n        </ol>\n        <p>另外，<code>corner-shape</code> 目前只有 Chrome 和 Edge 139 以上版本支援；Safari 和 Firefox 會自動改用一般圓角，不需要額外處理。</p>\n        <p>附帶的提示詞會由外往內重新計算你指定介面的圓角；專案中有圓角 token 時，直接修改 token。</p>"
      }
    },
    "005-drag-ripple": {
      "en": {
        "summary": "The cursor, drop line and the way nearby items make room in drag to reorder, for lists, kanban boards and horizontal rows.",
        "notes": "<p>In many drag-to-reorder lists the other items stay still during the drag and the list rearranges abruptly on release, so the user can only check which two items it landed between afterward. These five rules let the user see the result before releasing:</p>\n        <ol>\n        <li><strong>Cursor</strong>: Set it on every draggable element. Show a hand on hover and a grabbing hand while dragging, so the user knows the element can be dragged before pressing.</li>\n        <li><strong>Dragged item</strong>: Follows the pointer while staying clear of the drop point, so it does not cover the drop line. In a horizontal row it lifts upward; in a vertical list it moves to one side and shrinks to about 90%. Its original slot closes up.</li>\n        <li><strong>Drop line</strong>: Marks the drop point. It is a very faint thin line at about 15% of the text color, vertical in a row and horizontal in a list. It grows from the middle out to both ends when it appears, slides over when the drop point changes, and is not shown at the item’s original position.</li>\n        <li><strong>Making way</strong>: The items on both sides of the drop line move outward, and the closer they are, the further and earlier they move: offset = 10px × 0.7ⁿ, delay = 24ms × n, where n is the number of items between an item and the drop line, 0 for the ones right next to it. Icons start from 10px, cards from 8px.</li>\n        <li><strong>Drop and cancel</strong>: On release, the item moves into the gap and the other items spring to their new positions; pressing Esc or releasing outside the list cancels, and every item returns to where it was.</li>\n        </ol>\n        <p>Also, move items only with transform, without changing the layout; reordering must also be possible from the keyboard; with “Reduce motion” on, keep only the drop line.</p>\n        <h2>Parameters</h2>\n        <dl class=\"params\">\n        <dt>Offset</dt><dd>Icons 10px; cards 8px; × 0.7 for each item further out</dd>\n        <dt>Delay</dt><dd>+24ms for each item further out</dd>\n        <dt>Spring</dt><dd>Barely overshoots; settles in about 0.25s</dd>\n        <dt>Drop line</dt><dd>About 15% of the text color</dd>\n        </dl>\n        <p>The included prompt reuses the project’s existing drag logic and adds these effects to the lists, rows and docks you specify.</p>"
      },
      "text": {
        "summary": "拖曳排序的游標、落點插入線和兩側元素的避讓動態，適用於清單、看板和橫向排列。",
        "notes": "<p>很多拖曳排序在拖動時其他元素不動，放開後清單才突然重排，落在了哪兩項之間，只能放開後再檢查。下面五條讓使用者在放開前就看到結果：</p>\n        <ol>\n        <li><strong>游標</strong>：所有可拖曳的元素都要設定。懸停時顯示手形，拖動時顯示抓取手形，使用者按下之前就知道它可以拖曳。</li>\n        <li><strong>拖曳中的元素</strong>：跟隨指標，同時避開落點，不擋住插入線。橫向排列中向上浮起；縱向清單中移到一側，並縮小到約 90%。它原來的位置隨之合攏。</li>\n        <li><strong>插入線</strong>：用來標出落點，是一條很淡的細線，顏色約為文字顏色的 15%；橫排時垂直，清單中水平；出現時從中間向兩端展開，落點改變時平移過去，元素原來的位置上不顯示。</li>\n        <li><strong>避讓</strong>：插入線兩側的元素向外讓開，離得越近，讓得越多、動得越早：位移 = 10px × 0.7ⁿ，延遲 = 24ms × n，n 是與插入線相隔的元素數，緊鄰的為 0。圖示從 10px 起，卡片從 8px 起。</li>\n        <li><strong>放下與取消</strong>：放開後，元素進入空位，其他元素以彈簧動態移到新位置；按 Esc 或在清單外放開視為取消，所有元素回到原位。</li>\n        </ol>\n        <p>另外，只用 transform 移動元素，不改變版面；排序也要能用鍵盤完成；開啟「減少動態效果」時，只保留插入線。</p>\n        <h2>參數</h2>\n        <dl class=\"params\">\n        <dt>位移</dt><dd>圖示 10px；卡片 8px；每往外一個元素乘以 0.7</dd>\n        <dt>延遲</dt><dd>每往外一個元素增加 24ms</dd>\n        <dt>彈簧</dt><dd>幾乎沒有回彈；約 0.25s 停止</dd>\n        <dt>插入線</dt><dd>約為文字顏色的 15%</dd>\n        </dl>\n        <p>附帶的提示詞會沿用專案現有的拖曳邏輯，把這套效果加到你指定的清單、列和 Dock 上。</p>"
      }
    },
    "006-book-cards": {
      "en": {
        "summary": "Cards that open like a book: ordinary cards at rest that open slightly on hover to show the pages inside, in three styles.",
        "notes": "<p>In AI-generated products, cards are the element most likely to look alike. A book card keeps its usual look at rest and, on hover or focus, opens slightly like a small book to show a few pages inside. The key points are these four:</p>\n        <ol>\n        <li><strong>Structure</strong>: Suits cards that stand for content, such as documents, knowledge-base articles, templates and portfolio items; a card like “Settings” that is only an entry point has no pages inside and does not fit. The card is a stack of a cover, 4 pages and a back board that opens around its left edge; at rest all layers line up exactly.</li>\n        <li><strong>Timing</strong>: The cover opens the most, and each layer further in opens less and later: angle = 42° × 0.7ⁿ, delay = 28ms × n. The layers come to about 42°, 29°, 21° and 14°; when the pointer leaves, they close in reverse order, innermost page first.</li>\n        <li><strong>Light and shading</strong>: Light comes from above, and the shadow falls below the card. The shadow is two solid shapes that stretch downward and soften as the card opens; each page casts a shadow on the next until the two separate. Do not use <code>box-shadow</code>: it is a hollow ring, and its outline shows once the cover opens.</li>\n        <li><strong>Three styles</strong>: Default keeps the product’s existing card style and suits ordinary product cards; Skeuomorphic looks like a hardcover book on a gallery wall, with a book-cloth texture and a warm gray shadow; Minimal looks like a set of technical documents, with a flat light cover and thin line illustrations.</li>\n        </ol>\n        <p>Also, opening affects only the card itself: its size and position stay the same, and the surrounding cards and layout do not move.</p>\n        <h2>Parameters</h2>\n        <dl class=\"params\">\n        <dt>Angle</dt><dd>Cover 42°; × 0.7 for each layer further in</dd>\n        <dt>Delay</dt><dd>+28ms for each layer further in</dd>\n        <dt>Pages</dt><dd>4; hinged on the left edge</dd>\n        </dl>\n        <p>The included prompt first confirms the style, number of pages and opening direction, then restyles the project’s existing cards.</p>"
      },
      "text": {
        "summary": "像書一樣翻開的卡片：平時和一般卡片一樣，懸停時翻開一點、露出內頁，有三種風格可選。",
        "notes": "<p>AI 產生的產品裡，卡片最容易彼此雷同。翻書卡片平時維持原樣，懸停或聚焦時像一本小書一樣翻開一點，露出裡面的幾頁。要點有以下四條：</p>\n        <ol>\n        <li><strong>結構</strong>：適合代表內容的卡片，例如文件、知識庫、範本和作品集的項目；「設定」這類只是入口的卡片沒有內頁，並不適合。卡片由封面、4 頁內頁和封底疊成，繞左側翻開；靜止時各層完全重合。</li>\n        <li><strong>時序</strong>：封面翻得最多，越往內翻得越少、動得越晚：角度 = 42° × 0.7ⁿ，延遲 = 28ms × n。各層依序約為 42°、29°、21°、14°；指標移開時倒序合上，最內側一頁先合。</li>\n        <li><strong>光影</strong>：光從上方來，陰影落在卡片下方。陰影是兩層實心形狀，翻開時向下拉長、變柔和；前一頁為後一頁投下陰影，直到兩頁分開。不用 <code>box-shadow</code>，它是空心的一圈，封面翻開後會露出輪廓。</li>\n        <li><strong>三種風格</strong>：Default 沿用產品原有的卡片樣式，適合一般產品卡片；Skeuomorphic 像畫廊牆上的精裝書，帶書布紋理和偏暖的灰色投影；Minimal 像一套技術文件，平塗淺色封面搭配細線圖示。</li>\n        </ol>\n        <p>另外，翻開只作用於卡片本身：卡片的尺寸和位置不變，周圍的卡片和版面也不移動。</p>\n        <h2>參數</h2>\n        <dl class=\"params\">\n        <dt>角度</dt><dd>封面 42°；每往內一層乘以 0.7</dd>\n        <dt>延遲</dt><dd>每往內一層增加 28ms</dd>\n        <dt>內頁</dt><dd>4 頁；以左側邊緣為軸</dd>\n        </dl>\n        <p>附帶的提示詞會先確認風格、頁數和翻開方向，再改造專案中現有的卡片。</p>"
      }
    },
    "007-type-switches": {
      "en": {
        "summary": "How to handle heading line breaks, shifting numbers, truncation, Chinese details and translation length in Chinese and English type.",
        "notes": "<p>The second line of a homepage headline holds a single word, the text next to a countdown shifts left and right with every tick, and a button label is squeezed onto two lines after switching to German. These problems come from line breaking and character widths, and most can be fixed with a few lines of CSS. The common ones fall into these groups:</p>\n        <ol>\n        <li><strong>Line breaks</strong>: Use <code>text-wrap: balance</code> on headings so the lines are about the same length and the last line never holds just one or two words; use <code>text-wrap: pretty</code> on body text so a paragraph does not end with a lone word; use <code>white-space: nowrap</code> on button labels so they always stay on one line.</li>\n        <li><strong>Numbers</strong>: For numbers that change, such as timers, prices and counts, use <code>font-variant-numeric: tabular-nums</code> so every digit has the same width. Otherwise, when 11 changes to 10, the “1” is narrower than the “0” and the text after it moves.</li>\n        <li><strong>Truncation</strong>: When long text needs an ellipsis, add <code>min-width: 0</code> to the element in a flex layout as well as <code>text-overflow: ellipsis</code>. A flex item’s minimum width defaults to its content width, so without this rule the text stretches the container and the ellipsis never appears.</li>\n        <li><strong>Chinese body text</strong>: Justify it with <code>text-align: justify</code> and set the line length to a whole number of characters, so the right edge is even; <code>text-autospace: normal</code> automatically adds space between Chinese and Latin letters or numbers; <code>text-spacing-trim: trim-start</code> removes the half-width blank before an opening bracket at the start of a line.</li>\n        <li><strong>Chinese headings and line-start and line-end rules</strong>: Mark the word boundaries in headings with BudouX and add <code>word-break: keep-all</code>, so lines break between words, never in the middle of one. Leave the line-start and line-end rules to the browser, and remove <code>line-break: anywhere</code>, which turns them off.</li>\n        <li><strong>Multiple languages</strong>: The same spot has to fit translations of different lengths. German words are usually longer than English ones, so a button that just fits on one line in English may not fit in German. When translating, have the agent choose translations whose length suits the page layout, so that no word is split across two lines and no excess blank space is left.</li>\n        </ol>\n        <p>The included prompt writes these rules into the global styles for every page to inherit, adjusting only line breaks, spacing, alignment and truncation, without changing copy, fonts or colors; afterward it lists the changed files and compares your pages before and after.</p>"
      },
      "text": {
        "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>附帶的提示詞會把這些規則寫入全域樣式，由所有頁面繼承，只調整文字的換行、間距、對齊和截斷，不改文案、字型和顏色；改完後列出改動的檔案，並在你的頁面上對照改動前後。</p>"
      }
    },
    "008-wiki-layout": {
      "en": {
        "summary": "How to arrange the navigation bar, page list, end-of-article links, footer and mobile section switching in a wiki or help center.",
        "notes": "<p>When a product grows complex and its website needs many SEO articles, a reliable wiki can answer users’ questions and also bring in search traffic. The most common problems are that the page list cannot be found on a phone and that readers do not know where to go after an article. The layout needs to handle these five places:</p>\n        <ol>\n        <li><strong>Mobile section bar</strong>: Most phones are non-folding, with screens too narrow for a sidebar page list. Keep a section bar fixed at the bottom; tapping it opens a full-screen menu listing every section, one per row, easy to tap, with no need to scroll back to the top.</li>\n        <li><strong>Page list</strong>: When there are many sections and the list runs longer than one screen, give it its own height so it scrolls separately from the article, and cut off the overflow at the top and bottom. Add a gradient mask to the cut edges to show there is more above or below, plus a centered arrow button for scrolling with a click.</li>\n        <li><strong>End-of-article links</strong>: Below articles that answer questions, add links to the community and social media accounts. Whether the reader is a person or an AI, this brings conversions, like a free contextual ad for the conversion goal. Style the cards close to the article’s own components so they look like part of the article.</li>\n        <li><strong>Footer</strong>: Use an attractive background image to make the footer more than half a screen tall, drawing readers to scroll to the end and stay. Put genuinely useful information in the footer that helps readers solve their problems; otherwise it only puts them off.</li>\n        <li><strong>Navigation bar</strong>: Holds the logo (linking back to the main website), dropdown menus for key pages and the main CTA button, and sticks to the top on scroll. Safari and other browsers tint the address bar with the navigation bar’s color, so its background color should fit the brand.</li>\n        </ol>\n        <p>The included prompt finds the layout shared by the docs pages and adjusts only the position, scrolling and responsive behavior of the navigation bar, page list, outline and end-of-article area, leaving content, copy, colors and fonts unchanged; afterward it takes screenshots at the top, middle and end of a page and at phone width for you to check.</p>"
      },
      "text": {
        "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>"
      }
    },
    "009-overlays": {
      "en": {
        "summary": "When to use a tooltip, cursor tip, popconfirm, dialog, drawer or separate page.",
        "notes": "<p>Many dashboard products use dialogs everywhere: for the explanation behind a question mark, the confirmation before archiving, the edit form; each time, the user has to deal with the dialog before going on. A tooltip barely interrupts the user, while a dialog covers the whole page. The common overlays are these:</p>\n        <ol>\n        <li><strong>Tooltip</strong>: Adds text to whatever the pointer is on, often for truncated long text, such as a long file name in a table. It disappears when the pointer leaves, so it holds text only; for buttons or links, use a popover that opens on click instead.</li>\n        <li><strong>Cursor tip</strong>: Gives information continuously across a whole area, often in charts and fairly self-contained elements. It appears only when the pointer enters and moves with the pointer, such as showing the date and value of the data point under the pointer on a line chart.</li>\n        <li><strong>Popconfirm</strong>: For most actions that cannot be undone, such as deleting a comment. The confirmation appears next to the button, so the user does not have to look away; the path is short and it does not get in the way.</li>\n        <li><strong>Dialog</strong>: For confirmations with a big impact, bulk actions, or anything the user must stop and think about, such as permanently deleting a whole project; also for short forms that do not need other information on the page, such as renaming a file.</li>\n        <li><strong>Drawer</strong>: For longer forms, or forms that need the page content for reference while filling them in, such as editing a customer’s details next to the customer list. A drawer slides in from the side, so the main page stays visible, and it makes better use of the horizontal space on wide screens.</li>\n        <li><strong>Separate page</strong>: When the form is itself the main task, such as the full setup for a new project, make it a separate page with its own URL and a way back.</li>\n        </ol>\n        <p>Also, actions that can be undone, such as archiving, need no confirmation: do them right away and leave an “Undo” option. On phones, tooltips and cursor tips both show on tap instead.</p>\n        <p>The included prompt first finds every overlay in the product, decides which kind each one should use, and lists them in a table for you to decide; once you confirm, it changes only the parts you agreed to and keeps the visual style as it is.</p>"
      },
      "text": {
        "summary": "提示框、跟隨提示、就地確認、對話框、抽屜和獨立頁面，分別適合什麼情境。",
        "notes": "<p>很多後台產品處處用對話框：問號的說明、封存前的確認、編輯表單，每次都要先處理對話框才能繼續。提示框幾乎不打斷使用者，對話框則會遮住整個頁面，常見的浮層有以下幾種：</p>\n        <ol>\n        <li><strong>提示框（Tooltip）</strong>：為指標所指的內容補充文字，常見於被截斷的長文字，例如表格中的長檔名。指標移開就消失，所以只放文字；要放按鈕或連結，改用點擊開啟的氣泡（Popover）。</li>\n        <li><strong>跟隨提示（Cursor tip）</strong>：在一整塊區域內持續提供資訊，常見於圖表和相對獨立的元素。指標移入才出現，並跟著指標移動，例如在折線圖上顯示所指資料點的日期和數值。</li>\n        <li><strong>就地確認（Popconfirm）</strong>：用於大多數無法復原的操作，例如刪除一則留言。確認框出現在按鈕旁，使用者不用移開視線，路徑短，也不受打擾。</li>\n        <li><strong>對話框（Dialog）</strong>：用於影響大、批次操作或必須讓使用者停下來考慮的確認，例如永久刪除整個專案；也用於較短、不需要參照頁面其他資訊的表單，例如重新命名檔案。</li>\n        <li><strong>抽屜（Drawer）</strong>：用於較長的表單，或填寫時需要對照頁面內容，例如在客戶清單旁編輯某位客戶的資料。抽屜從側邊滑出，主頁面仍然可見，也更能善用寬螢幕的橫向空間。</li>\n        <li><strong>獨立頁面</strong>：表單本身就是主要任務時，例如新建專案時的完整設定，做成獨立頁面，有自己的網址和返回路徑。</li>\n        </ol>\n        <p>另外，可以復原的操作，例如封存，不需要確認：直接執行，再留一個「復原」入口。到了手機上，提示框和跟隨提示都改成點擊顯示。</p>\n        <p>附帶的提示詞會先找出產品中所有的浮層，逐一判斷該用哪一種，列成表格由你決定；確認後只修改你同意的部分，視覺樣式維持不變。</p>"
      }
    },
    "010-liquid-glass": {
      "en": {
        "summary": "The six layers of liquid glass, and how to adapt the tint and text color to the background, for cards and players over images or video.",
        "notes": "<p>Ordinary frosted glass has only a translucent background and blur, so text is hard to read over a busy background and the glass turns grayish on dark ones. Liquid glass adds refraction at the rim and a tint that changes with the background, so it looks thick and the text always stays clear. The material came out of building Lumno and is made of six stacked layers, from bottom to top:</p>\n        <ol>\n        <li><strong>Shadow</strong>: Gives the card a sense of volume.</li>\n        <li><strong>Blur and brightening</strong>: Blurs the background while raising its saturation and brightness, so the glass looks clearer. Light glass: saturation 180%, brightness 1.06; dark glass: saturation 160%, brightness 0.8.</li>\n        <li><strong>Rim refraction</strong>: An SVG displacement map shifts the background in a band around the rim inward, more the closer it is to the edge, while the middle stays flat; red light bends a little more than blue, creating a color split. Rim width 44px, color split ±15%.</li>\n        <li><strong>Tint</strong>: A layer of translucent color whose opacity adjusts automatically to how busy the background is: the busier the background, the stronger the tint and the easier the text is to read. Light glass uses white at 6%–22%, dark glass 16%–38%.</li>\n        <li><strong>Rim light</strong>: One line at the top left and one at the bottom right, plus one more inset further in, to make the whole piece look thicker.</li>\n        <li><strong>Ink</strong>: Text uses multiply on light glass and a brightening overlay on dark glass, so it picks up a little of the background’s color.</li>\n        </ol>\n        <p>Also, the material reads several sample points on the background and works out their average brightness; below 0.5 it switches to light automatically. Liquid glass suits covers, videos, wallpapers and other images with rich variation in brightness or color; on a solid background it looks almost the same as an ordinary translucent block. When checking the text, look at both the brightest and the darkest parts of the background.</p>\n        <h2>Parameters</h2>\n        <dl class=\"params\">\n        <dt>Light</dt><dd>Tint white 6%–22%; blur 2px; saturation 180%; brightness 1.06</dd>\n        <dt>Dark</dt><dd>Tint rgb(20 20 24) 16%–38%; blur 2px; saturation 160%; brightness 0.8</dd>\n        <dt>Refraction</dt><dd>Rim width 44px; shift at the edge 1.1 × rim width; color split ±15%</dd>\n        </dl>\n        <p>I have also released this material as an open-source playground, <a href=\"https://www.kubai.design/glasswork/\">Glasswork</a>: the tint, blur, rim refraction, rim light and text color can each be adjusted from a panel and checked over different wallpapers, photos and videos, and the result can be copied as CSS.</p>\n        <p>The included prompt first lists the cards, players and search boxes in the product that sit on images, video or busy backgrounds, and says which become glass and which stay as they are; it then writes the material into color tokens, with one set of tint strengths each for light and dark mode, and keeps the layout unchanged.</p>"
      },
      "text": {
        "summary": "液態玻璃材質的六層做法，以及如何隨背景明暗調整著色和文字顏色，適合放在圖片或影片上的卡片和播放器。",
        "notes": "<p>一般的毛玻璃只有半透明背景和模糊，背景複雜時文字難以閱讀，在深色背景上還會發灰；液態玻璃加上了邊緣折射和隨背景變化的著色，看起來有厚度，文字也始終清楚。這套材質是開發 Lumno 時研究出來的，由六層疊成，由下往上依序是：</p>\n        <ol>\n        <li><strong>投影</strong>：表現卡片的體積感。</li>\n        <li><strong>模糊與提亮</strong>：模糊背景，同時提高背景的飽和度和亮度，讓玻璃更通透。淺色玻璃飽和度 180%、亮度 1.06；深色玻璃飽和度 160%、亮度 0.8。</li>\n        <li><strong>邊緣折射</strong>：用 SVG 位移貼圖把邊緣一圈的背景向內偏移，越靠近邊緣偏移越大，中間保持平整；紅光比藍光多偏折一點，形成色散。邊寬 44px，色散 ±15%。</li>\n        <li><strong>著色</strong>：一層半透明顏色，透明度依背景的複雜程度自動調整，背景越複雜，著色越濃，文字越容易看清楚。淺色玻璃用白色 6%–22%，深色玻璃 16%–38%。</li>\n        <li><strong>邊緣光</strong>：左上、右下各一道，再往內縮一些加一道，讓整體更有厚度。</li>\n        <li><strong>文字著色</strong>：淺色玻璃上用色彩增值，深色玻璃上用覆蓋提亮，文字會帶一點背景的顏色。</li>\n        </ol>\n        <p>另外，材質會讀取背景上的多個取樣點，算出平均亮度，低於 0.5 時自動切換為淺色。液態玻璃適合放在封面、影片、桌布這類明暗或色彩變化豐富的畫面上，在純色背景上它和一般的半透明色塊幾乎沒有差別。檢查文字時，背景最亮和最暗的地方都要看。</p>\n        <h2>參數</h2>\n        <dl class=\"params\">\n        <dt>淺色</dt><dd>著色白 6%–22%；模糊 2px；飽和度 180%；亮度 1.06</dd>\n        <dt>深色</dt><dd>著色 rgb(20 20 24) 16%–38%；模糊 2px；飽和度 160%；亮度 0.8</dd>\n        <dt>折射</dt><dd>邊緣寬度 44px；邊緣偏移為邊緣寬度的 1.1 倍；色散 ±15%</dd>\n        </dl>\n        <p>筆者已將這套材質開源為線上工具 <a href=\"https://www.kubai.design/glasswork/\">Glasswork</a>：著色、模糊、邊緣折射、邊緣光和文字顏色都能在面板上逐項調整，並放在不同的桌布、照片和影片上檢視效果，調整完成後可以直接複製 CSS。</p>\n        <p>附帶的提示詞會先列出產品中放在圖片、影片或複雜背景上的卡片、播放器和搜尋框，說明哪些改成玻璃、哪些維持不變；再把材質寫進顏色 token，深淺模式各配一套著色濃度，版面不變。</p>"
      }
    },
    "011-easing-curves": {
      "en": {
        "summary": "Seven common animation easing curves, from Linear to Spring, and the kind of motion each one suits.",
        "notes": "<p>The rhythm of an animation is described by its easing curve: the steeper the curve, the sharper the change in speed and the faster it looks. If a menu popping up, a dialog closing and an indicator sliding all use the default <code>ease</code>, users cannot tell whether an element is appearing, disappearing or changing place. The common curves are these:</p>\n        <ol>\n        <li><strong>Linear</strong>: For things like progress bars and loading that only need to look like they are “running”. Constant speed, abrupt at the start and end, <code>linear</code>.</li>\n        <li><strong>Ease-out and Strong ease-out</strong>: For overlays and modal elements entering, such as toasts, menus, dialogs and drawers, use Ease-out, fast then slow, <code>cubic-bezier(0, 0, .58, 1)</code>. For small elements that settle into place right after a click, such as icons, text and a selected pill, use Strong ease-out, which starts faster and settles longer, <code>cubic-bezier(.22, 1, .36, 1)</code>, for the most immediate response.</li>\n        <li><strong>Ease-in</strong>: For elements leaving, such as a dialog closing or a toast disappearing. Slow then fast, for a clean exit, <code>cubic-bezier(.42, 0, 1, 1)</code>. Do not use it for entrances: the slow start makes the interface look sluggish.</li>\n        <li><strong>Ease-in-out</strong>: For elements changing place within the interface, such as the indicator sliding under tabs, a carousel turning pages or a table of contents scrolling smoothly. Slow at both ends and fastest in the middle, <code>cubic-bezier(.42, 0, .58, 1)</code>.</li>\n        <li><strong>Overshoot</strong>: For small, playful confirmations, such as a check mark, a like or a badge popping up. Goes about 10% past the end and comes back, <code>cubic-bezier(.34, 1.56, .64, 1)</code>. Do not use it on large panels, or the whole block of interface will wobble.</li>\n        <li><strong>Spring</strong>: For settling back after release, such as a drawer springing back, pull to refresh, or an item landing after drag to reorder. It wobbles gently once or twice at the end before coming to rest, more like a real object than Overshoot; the element already has velocity when the user lets go, and a spring can carry that velocity on.</li>\n        </ol>\n        <p>Also, define these curves as motion tokens and use them by role, so the rhythm stays consistent across the whole product.</p>\n        <p>The included prompt first lists every transition and animation in the project, marking the places that still use the default ease or use ease-in for an entrance, and the curve each one should change to; it then adds motion tokens and adjusts the curves and durations one by one.</p>"
      },
      "text": {
        "summary": "七種常用的動畫速度曲線，從 Linear 到 Spring，分別適合什麼樣的動作。",
        "notes": "<p>動畫的節奏用速度曲線描述：曲線越陡，速度變化越劇烈，看起來就越快。選單彈出、對話框關閉、指示條滑動如果都用預設的 <code>ease</code>，使用者分不清元素是在出現、消失還是換位置。常用的曲線有以下幾種：</p>\n        <ol>\n        <li><strong>Linear</strong>：用於進度條、載入這類看起來只是「在跑」的東西。等速運動，起止都很生硬，<code>linear</code>。</li>\n        <li><strong>Ease-out 與 Strong ease-out</strong>：浮層和模態元素的進場，例如 Toast、選單、對話框、抽屜，用先快後慢的 Ease-out，<code>cubic-bezier(0, 0, .58, 1)</code>。點擊後馬上就定位的小元素，例如圖示、文字、選中的膠囊，用起步更快、收尾更長的 Strong ease-out，<code>cubic-bezier(.22, 1, .36, 1)</code>，回應最直接。</li>\n        <li><strong>Ease-in</strong>：用於元素離場，例如對話框關閉、Toast 消失。先慢後快，乾脆地離開，<code>cubic-bezier(.42, 0, 1, 1)</code>。不要用在進場上，起步慢，看起來像介面反應遲鈍。</li>\n        <li><strong>Ease-in-out</strong>：用於在介面內換位置的元素，例如分頁標籤下滑動的指示條、輪播翻頁、目錄平滑捲動。兩端慢、中間最快，<code>cubic-bezier(.42, 0, .58, 1)</code>。</li>\n        <li><strong>Overshoot</strong>：用於小而俏皮的確認，例如勾選、按讚、徽章彈出。衝過終點約 10% 再退回，<code>cubic-bezier(.34, 1.56, .64, 1)</code>。不要用在大面板上，否則整塊介面都會晃動。</li>\n        <li><strong>Spring</strong>：用於放開後的歸位，例如抽屜回彈、下拉重新整理、拖曳排序後的定位。到位後輕晃一兩下再停穩，比 Overshoot 更像真實物體；使用者放開時元素已經帶有速度，彈簧能接著這個速度運動。</li>\n        </ol>\n        <p>另外，把這些曲線定義為動態 token，依角色使用，整個產品的節奏就能保持一致。</p>\n        <p>附帶的提示詞會先列出專案中所有的轉場和動畫，標出仍用預設 ease 或進場用了 ease-in 的地方，以及每處要換成的曲線；再加上動態 token，逐一調整曲線和時長。</p>"
      }
    },
    "012-message-bubbles": {
      "en": {
        "summary": "Six message bubble materials with matching thinking, sending and deleting motion, for products that want to stand out from typical AI chats.",
        "notes": "<p>Typical AI assistant interfaces look almost the same: blue bubbles on the right, gray bubbles on the left, three bouncing dots while waiting. Bubbles appear more than anything else in a conversation, so changing their material and pairing it with matching motion gives the interface a style of its own. This is an exploratory version with six materials:</p>\n        <ol>\n        <li><strong>Cirrus</strong>: Suits light, clean products. A thin frosted glass with no border, with blue sky and white clouds behind it.</li>\n        <li><strong>Pixel</strong>: Has a retro game feel. The bubble is drawn on a pixel grid, its edges change one cell at a time, and it leaves a slight pixel trail as it moves.</li>\n        <li><strong>Aqua</strong>: Nostalgic and lively. The jelly-like look of the old Mac, with a layer of highlight on the surface.</li>\n        <li><strong>Gradient</strong>: Suits products that want to emphasize the brand. As in Telegram, the whole conversation shares one gradient, so bubbles at different heights have different colors.</li>\n        <li><strong>Skeuomorphic</strong>: Warm and tactile. Uses the same recipe as <a href=\"/001-skeuomorphic-buttons/\">001 Skeuomorphic buttons</a>.</li>\n        <li><strong>Solid</strong>: The basic control group. Easiest to read in long conversations with long reading time, and the lightest on performance.</li>\n        </ol>\n        <p>Also, the motion has to change along with the material, or the styles clash, as with pixel bubbles and a soft fade in and out. The whole conversation moves as one, and each material has its own spring values: on send, a new bubble rises from about 40px below, entering in a way that depends on the material; while the AI writes a long reply, a small dot matrix shows first and expands into a bubble once the reply starts; after a message in the middle is deleted, the messages above move down one after another to fill the gap.</p>\n        <p>The included prompt first asks whether to restyle your existing chat interface or build a standalone demo, and which materials to use; once you confirm, it adjusts the bubble materials and motion together, and asks you item by item before changing the input box, message menu and typing indicator.</p>"
      },
      "text": {
        "summary": "六種訊息氣泡材質，以及與之對應的思考、傳送和刪除動態，適合想和常見 AI 對話介面做出區隔的產品。",
        "notes": "<p>常見的 AI 助理介面幾乎一樣：右側藍色氣泡、左側灰色氣泡，等待時三個跳動的圓點。氣泡在對話中出現得最多，換掉它的材質、搭配對應的動態，介面就有了自己的風格；目前是探索版，有以下六種材質：</p>\n        <ol>\n        <li><strong>Cirrus</strong>：適合輕盈、乾淨的產品。沒有邊框的薄霧面玻璃，背後是藍天白雲。</li>\n        <li><strong>像素</strong>：帶有復古遊戲的味道。氣泡畫在像素格線上，邊緣一格一格變化，移動時帶一點像素殘影。</li>\n        <li><strong>Aqua</strong>：懷舊而活潑。舊款 Mac 的果凍質感，表面有一層亮光。</li>\n        <li><strong>漸層</strong>：適合強調品牌。類似 Telegram 的做法，整段對話共用一張漸層，氣泡所在的高度不同，顏色也不同。</li>\n        <li><strong>擬物</strong>：溫暖、有觸感。和 <a href=\"/zh-hant/001-skeuomorphic-buttons/\">001 擬物按鈕</a>使用同一套配方。</li>\n        <li><strong>純色</strong>：基礎對照組。對話多、閱讀時間長時最好讀，也最省效能。</li>\n        </ol>\n        <p>另外，動態要隨材質一起換，否則風格會衝突，例如像素氣泡配上柔和的淡入淡出。整段對話作為一個整體移動，每種材質使用各自的彈簧參數：傳送時新氣泡從下方約 40px 處升起，進場方式隨材質而變；AI 產生長回覆時先顯示一個小點陣，回覆開始後展開成氣泡；刪除中間一則後，上方的訊息依序向下補位。</p>\n        <p>附帶的提示詞會先問你要改造現有的聊天介面還是做一個獨立展示、使用哪幾種材質；確認後同步調整氣泡材質和動態，輸入框、訊息選單和輸入中提示則會逐項詢問過你才修改。</p>"
      }
    },
    "013-shockwave-glow": {
      "en": {
        "summary": "A shockwave halo that spreads from where it is triggered, with lens distortion and a color split, to play when an AI assistant is called up.",
        "notes": "<p>This effect combines the marquee light around the screen edge in iOS 27.3 with the halo burst the Dia browser plays when it opens its home page: the halo spreads from the trigger point, and the page it passes over bends and splits in color, which gives it a physical feel. The effect is made of these six layers:</p>\n        <ol>\n        <li><strong>Page snapshot</strong>: Turns the current page into an image as the basis for the layers that follow; Chrome’s new HTML-in-Canvas can help with this.</li>\n        <li><strong>Lens bend</strong>: The halo as a whole acts as a lens, stretching on the outside and compressing on the inside, so space looks pushed apart.</li>\n        <li><strong>Channel split</strong>: The red and blue channels shift 8% more and 8% less than the green channel, creating a slight color split where the page is displaced, while text stays sharp.</li>\n        <li><strong>Color rings</strong>: Four color rings blend smoothly and fade out as the halo spreads, setting its color and brightness. In light mode they tint the page; in dark mode they add light to it with a screen blend.</li>\n        <li><strong>Edge refraction</strong>: The halo spreads only within the content area and does not cover the browser’s or app’s toolbar. When it reaches the edge, the content stretches slightly toward the edge as if seen through the bevel of a piece of glass, while the window frame stays as it is.</li>\n        <li><strong>Glints on lines</strong>: As the halo passes, dividers and borders brighten briefly, more faintly in dark mode, so the page’s structure also takes part in the effect.</li>\n        </ol>\n        <p>Also, the halo is eye-catching and suits only infrequent actions such as calling up an AI; on a button that is clicked often it soon gets annoying. With “Reduce motion” on, drop the bend and the color split, and the halo only fades in and out in place.</p>\n        <h2>Parameters</h2>\n        <dl class=\"params\">\n        <dt>Duration</dt><dd>Spreads over 1000ms; fast, then slow</dd>\n        <dt>Color split</dt><dd>Red at 1.08 times; blue at 0.92 times the offset</dd>\n        <dt>Aurora</dt><dd>Blue, violet, pink, peach</dd>\n        <dt>Halo</dt><dd>Orange, yellow</dd>\n        <dt>Frost</dt><dd>Mint</dd>\n        <dt>Spark</dt><dd>Violet, gold</dd>\n        </dl>\n        <p>The included prompt first confirms the trigger, where the halo spreads from, whether to enable the bend and edge refraction, and the palette; once you confirm, it proposes an implementation based on the project’s tech stack.</p>"
      },
      "text": {
        "summary": "一種從觸發位置向外擴散、帶有透鏡扭曲和色散的衝擊波光環，適合在喚起 AI 助理時播放。",
        "notes": "<p>這個效果結合了 iOS 27.3 的螢幕邊緣跑馬燈光效，以及 Dia 瀏覽器開啟首頁時的光環衝擊：光環從觸發位置擴散，經過的頁面隨之扭曲和色散，因此顯得有物理質感。效果由以下六層組成：</p>\n        <ol>\n        <li><strong>頁面快照</strong>：把目前的頁面轉為圖像，作為後面各層計算的基礎，可以借助 Chrome 新增的 HTML-in-Canvas。</li>\n        <li><strong>透鏡扭曲</strong>：光環整體作為一個透鏡，外側拉伸、內側壓縮，表現出空間被推開。</li>\n        <li><strong>通道分離</strong>：紅、藍通道的位移分別比綠色通道多 8%、少 8%，在位移處形成輕微的色散，文字仍然清晰。</li>\n        <li><strong>色環</strong>：四道色環平順過渡，隨擴散逐漸淡出，決定光環的顏色和亮度。淺色模式下為頁面染色，深色模式下用 screen 混合為頁面加光。</li>\n        <li><strong>邊緣折射</strong>：光環只在內容區內擴散，不覆蓋瀏覽器或 App 的工具列。到達邊緣時，內容像透過玻璃的斜邊一樣向邊緣輕微拉伸，視窗邊框保持不變。</li>\n        <li><strong>線條反光</strong>：光環經過時，分隔線和邊框短暫提亮，深色模式下較弱，讓頁面結構也參與到效果之中。</li>\n        </ol>\n        <p>另外，光環很醒目，只適合喚起 AI 這類低頻操作，用在頻繁點擊的按鈕上很快就會讓人厭煩。開啟「減少動態效果」時，去掉扭曲和色散，光環只在原位淡入淡出。</p>\n        <h2>參數</h2>\n        <dl class=\"params\">\n        <dt>時長</dt><dd>擴散 1000ms；先快後慢</dd>\n        <dt>色散</dt><dd>紅色通道為位移的 1.08 倍；藍色通道為 0.92 倍</dd>\n        <dt>Aurora</dt><dd>藍、紫、粉紅、桃色</dd>\n        <dt>Halo</dt><dd>橘、黃</dd>\n        <dt>Frost</dt><dd>薄荷綠</dd>\n        <dt>Spark</dt><dd>紫、金</dd>\n        </dl>\n        <p>附帶的提示詞會先確認觸發條件、擴散位置、是否啟用扭曲和邊緣折射，以及配色；確認後再依專案的技術架構提出實作方案。</p>"
      }
    },
    "014-card-delete": {
      "en": {
        "summary": "Which kind of deletion the Burn, Plume, Blocks and Peel card effects each suit, and how the remaining cards close the gap.",
        "notes": "<p>In lists such as to-dos, a deleted item often vanishes instantly and the item below jumps up at once to fill the gap, before the user can see which one was deleted. The four effects below make the deletion visible, and handle how neighboring cards react and close the gap:</p>\n        <ol>\n        <li><strong>Burn</strong>: Suits thorough, formal deletions. Fire spreads from the delete button, and the paper chars until only an edge of ash remains, with sparks and paper flakes drifting upward; neighboring cards light up on the side facing the fire and warp slightly in the heat.</li>\n        <li><strong>Plume</strong>: Suits gentle or positive actions, such as completing a to-do or archiving a note. A soft flame rises from the bottom of the card and carries it away from the bottom up; neighboring cards light up too and warp slightly.</li>\n        <li><strong>Blocks</strong>: Suits casual contexts. The card breaks into blocks of different sizes that scatter outward, fall to the bottom of the list, bounce once and disappear; neighboring cards take the impact, get pushed away and spring back.</li>\n        <li><strong>Peel</strong>: Suits elements that look like physical objects, such as stickers and sticky notes. The card lifts from the corner nearest the delete button, showing a white die-cut border on its back, and flies off once peeled; neighboring cards are pulled toward the sticker and spring back once it comes off.</li>\n        <li><strong>Closing the gap</strong>: The remaining cards start closing the gap on a spring before the effect ends, changing only their position, not their height, so there is no jump and no pause between the deletion and the gap closing.</li>\n        </ol>\n        <p>Also, before the deletion takes effect, read the card’s position and capture its image; the effect’s first frame must match the real card exactly, rounded corners included, or the card will jump first. When the user undoes, the effect stops at once and the card comes back the way the product already restores items.</p>\n        <h2>Parameters</h2>\n        <dl class=\"params\">\n        <dt>Duration</dt><dd>Burn 2s; Plume 1.4s; Blocks 1.5s; Peel 1.2s</dd>\n        <dt>Closing the gap</dt><dd>Spring 520ms; transforms only</dd>\n        <dt>At once</dt><dd>Up to 3 at a time; beyond that, a fade</dd>\n        </dl>\n        <p>The included prompt first reads the project and confirms the delete entry points, the effects, how neighboring elements react and the colors; once you confirm, it makes the changes to fit the existing tech stack and interface.</p>"
      },
      "text": {
        "summary": "燃燒、火焰、碎塊和撕貼紙四種卡片刪除效果，分別適合什麼樣的刪除，以及剩下的卡片如何補位。",
        "notes": "<p>在待辦這類清單裡，被刪除的項目常常瞬間消失，下方項目立刻跳上來補齊，使用者來不及看清刪掉的是哪一項。下面四種效果讓刪除過程能被看清，並處理了相鄰卡片的反應和補位：</p>\n        <ol>\n        <li><strong>Burn 燃燒</strong>：適合徹底、正式的刪除。火焰從刪除按鈕處開始蔓延，紙面燒焦後只留下一道灰燼邊，火星和紙屑向上飄散；相鄰卡片朝向火焰的一側被照亮，並隨熱浪輕微扭曲。</li>\n        <li><strong>Plume 火焰</strong>：適合溫和或正向的操作，例如完成待辦、封存筆記。一團柔和的火焰從卡片底部升起，把卡片由下而上帶走；相鄰卡片同樣被照亮，並輕微扭曲。</li>\n        <li><strong>Blocks 碎塊</strong>：適合輕鬆的情境。卡片碎裂成大小不一的方塊向外散開，落到清單底部彈跳一次後消失；相鄰卡片受到衝擊，被推開後回彈。</li>\n        <li><strong>Peel 撕貼紙</strong>：適合貼紙、便利貼這類本身像實物的元素。卡片從靠近刪除按鈕的一角被掀起，背面帶一圈白色的模切邊，撕下後飛出；相鄰卡片被拉向貼紙，撕下後回彈。</li>\n        <li><strong>補位</strong>：剩下的卡片在效果結束之前就以彈簧動態開始補齊空位，只改變位置，不改變高度，刪除和補位之間沒有跳動，也沒有空檔。</li>\n        </ol>\n        <p>另外，刪除生效前先讀取卡片位置並擷取畫面，效果的第一個影格要和真實卡片完全一致，包括圓角，否則卡片會先跳一下。使用者復原時，效果立即停止，卡片依產品原有的方式恢復。</p>\n        <h2>參數</h2>\n        <dl class=\"params\">\n        <dt>時長</dt><dd>Burn 2s；Plume 1.4s；Blocks 1.5s；Peel 1.2s</dd>\n        <dt>補位</dt><dd>彈簧 520ms；只使用 transform</dd>\n        <dt>同時進行</dt><dd>最多同時 3 個，超過時改用淡出</dd>\n        </dl>\n        <p>附帶的提示詞會先讀取專案，確認刪除入口、效果、相鄰元素的反應和配色；確認後再依現有的技術架構和介面進行改造。</p>"
      }
    },
    "015-ui-continuity": {
      "en": {
        "summary": "Using seven common iOS cases, how to carry the element you tapped straight into the next state when the interface changes.",
        "notes": "<p>When the user taps the mini player, if the bar simply disappears and the player pops up as a whole page, the user has to look for the cover and buttons all over again on the new page. Continuity means the element you tapped carries straight into the next state, so people always know where they came from and where they are now. The common cases in iOS are these:</p>\n        <ol>\n        <li><strong>Navigation</strong>: When going from a list to the next level, the title of the tapped row carries on as the page title, and the old page title shrinks into the back button; on scroll, the title moves into the top bar.</li>\n        <li><strong>Card and Chart</strong>: When a card opens into its details, such as an article card or a data card. The card expands into the article, the image extends into the header image, and the small bars on the card carry on as the chart’s bars; pulling down retraces the same path back.</li>\n        <li><strong>Player</strong>: When the mini player expands into the full player, the small cover grows straight into its place on the player page, and the title and buttons each move to their new positions instead of disappearing first and fading back in.</li>\n        <li><strong>Search</strong>: When the search field is tapped, it moves to the top, matching items move up as the user types, and the rest fade out.</li>\n        <li><strong>Menu</strong>: When a menu opens from a button, it expands from the button’s position; a new item drops into the first place, and the others move back one after another.</li>\n        <li><strong>Tab Bar</strong>: When switching tabs, the selected pill first stretches, then settles into its new position.</li>\n        </ol>\n        <p>Also, content that exists only in the end state, such as the player’s progress bar and lyrics, fades in after half of the move, not at the same time as the shared elements, so it does not pull the eye away. When collapsing or going back, elements return along the same path.</p>\n        <h2>Parameters</h2>\n        <dl class=\"params\">\n        <dt>Curve</dt><dd>cubic-bezier(.32, .72, 0, 1); fast start, long settle</dd>\n        <dt>Duration</dt><dd>Phones: 450–700ms to open a full screen; 350–500ms for menus and bottom sheets; desktop about two thirds of that</dd>\n        <dt>Fade-in</dt><dd>Content that exists only in the end state fades in after half of the move</dd>\n        </dl>\n        <p>The included prompt first reads the project, finds the places where continuity fits, and proposes a plan ranked by how often each is used and how much it costs to change; once you confirm, it carries out the changes.</p>"
      },
      "text": {
        "summary": "以 iOS 的七個常見情境為例，說明介面切換時，如何讓點到的元素直接過渡到下一個狀態。",
        "notes": "<p>點擊迷你播放列時，如果播放列直接消失、播放頁整頁彈出，使用者就要在新頁面上重新尋找封面和按鈕；連續性是讓點到的元素直接過渡成下一個狀態，讓人始終清楚自己從哪裡來、現在在哪裡。iOS 中常見的情境有以下幾種：</p>\n        <ol>\n        <li><strong>Navigation</strong>：從清單進入下一層頁面時，點到的那一列標題延續為頁面標題，原來的頁面標題收合為返回按鈕；捲動時，標題收進頂部列。</li>\n        <li><strong>Card 與 Chart</strong>：卡片開啟為詳細內容時，例如文章卡片、資料卡片。卡片展開為內文，圖片延展為頁首圖，卡片裡的小長條延續為圖表的長條；下拉時沿原路收回。</li>\n        <li><strong>Player</strong>：迷你播放列展開為播放頁時，小封面直接放大到播放頁上的位置，標題和按鈕也各自移到新位置，不先消失再淡入。</li>\n        <li><strong>Search</strong>：點擊搜尋框時，搜尋框移到頂部，符合的項目隨輸入上移，其餘項目淡出。</li>\n        <li><strong>Menu</strong>：從按鈕開啟選單時，選單從按鈕的原位展開；新增的項目落入第一位，其餘項目依序後移。</li>\n        <li><strong>Tab Bar</strong>：切換分頁標籤時，選中的膠囊先伸展，再落到新的位置。</li>\n        </ol>\n        <p>另外，只在結束狀態出現的內容，例如播放頁的進度條和歌詞，在位移過半後再淡入，不和共用元素同時變化，以免分散視線。收合和返回時，元素沿原路還原。</p>\n        <h2>參數</h2>\n        <dl class=\"params\">\n        <dt>曲線</dt><dd>cubic-bezier(.32, .72, 0, 1)；起步快、收尾長</dd>\n        <dt>時長</dt><dd>手機上展開全螢幕 450–700ms；選單和底部面板 350–500ms；電腦上約為手機的三分之二</dd>\n        <dt>淡入</dt><dd>只在結束狀態出現的內容，在位移過半後淡入</dd>\n        </dl>\n        <p>附帶的提示詞會先讀取專案，找出適合做連續性的地方，依使用頻率和改造成本排序提出方案；確認後再進行改造。</p>"
      }
    },
    "016-toast-or-notification": {
      "en": {
        "summary": "Which messages suit a Toast and which suit a Notification, and when to use neither.",
        "notes": "<p>Toasts and Notifications are both small cards floating over the page, and they are often mixed up: important information disappears after a few seconds, while an ordinary confirmation like “Saved” stays on screen. The common kinds of message are these five:</p>\n        <ol>\n        <li><strong>Status Toast</strong>: Confirms the result of an action that the user only needs to know about, such as copying a link or moving a task. Just an icon and a short line of text, with no buttons; it disappears after 3 seconds.</li>\n        <li><strong>Action Toast</strong>: For actions that can be undone. Run the action right away without asking first; the Toast keeps an Undo button for 5 seconds, with a ring showing the time left, and after an undo it changes in place to “Task restored”.</li>\n        <li><strong>Progress Toast</strong>: For actions that take a while, such as uploading a file. It shows progress first, changes in place into the result when done, and offers a button to view it.</li>\n        <li><strong>Notification</strong>: For information from other people or the system that needs to be seen but not handled right away, such as a mention, a task coming due or a weekly report being generated. It appears in the top right and stays until the user handles or dismisses it; up to three stack up, and they expand into a list on hover.</li>\n        <li><strong>Dialogs and inline messages</strong>: Anything the user must deal with suits neither a Toast nor a Notification. Confirm actions that cannot be undone with a dialog before running them; failures that need handling stay where they occur until resolved, and form errors appear next to their fields.</li>\n        </ol>\n        <h2>Parameters</h2>\n        <dl class=\"params\">\n        <dt>Toast enter</dt><dd>500ms; cubic-bezier(.25, .1, .25, 1); down 10px; clears from an 8px blur</dd>\n        <dt>Sheen</dt><dd>Only when something is done: a status toast entering, progress turning into its result, Undo completed</dd>\n        <dt>Notification enter</dt><dd>Drops from 56px above; 560ms; cubic-bezier(.32, .72, 0, 1)</dd>\n        <dt>Notification stack</dt><dd>Each layer peeks out 12px; at most three layers</dd>\n        </dl>\n        <p>The included prompt first reads the product and decides for each message whether it should use a Toast, a Notification or neither, listing them in a table for you to decide; once you confirm, it can also restyle the Toast and Notification to match the demo.</p>"
      },
      "text": {
        "summary": "Toast 和 Notification 分別適合什麼樣的提示，以及什麼時候兩者都不該用。",
        "notes": "<p>Toast 和 Notification 都是浮在頁面上的小卡片，經常被混用：重要的資訊幾秒後就消失了，「已儲存」這類一般的確認卻一直留在介面上。常見的提示有以下五種：</p>\n        <ol>\n        <li><strong>Status Toast</strong>：用於確認操作的結果，使用者知道即可，例如複製連結、移動任務。只有一個圖示和一句短文字，不帶按鈕，3 秒後自動消失。</li>\n        <li><strong>Action Toast</strong>：用於可以復原的操作。直接執行，不預先確認；Toast 裡保留 5 秒的 Undo 按鈕，以圓環顯示剩餘時間，復原後原地變為「Task restored」。</li>\n        <li><strong>Progress Toast</strong>：用於耗時較長的操作，例如上傳檔案。先顯示進度，完成後原地變為結果，並提供查看按鈕。</li>\n        <li><strong>Notification</strong>：由他人或系統發出、需要看到但不必立刻處理的資訊，例如被人提及、任務到期、週報產生。顯示在右上角，保留到使用者處理或關閉為止；最多疊三層，懸停時展開為清單。</li>\n        <li><strong>對話框與原地提示</strong>：必須由使用者處理的事，Toast 和 Notification 都不適合。無法復原的操作在執行前用對話框確認；需要處理的失敗留在原處直到解決，表單錯誤顯示在對應欄位旁邊。</li>\n        </ol>\n        <h2>參數</h2>\n        <dl class=\"params\">\n        <dt>Toast 進場</dt><dd>500ms；cubic-bezier(.25, .1, .25, 1)；下移 10px；從 8px 模糊變清晰</dd>\n        <dt>掃光</dt><dd>只在事情完成時出現：狀態 Toast 進場、進度轉為結果、復原完成</dd>\n        <dt>通知進場</dt><dd>從上方 56px 處落下；560ms；cubic-bezier(.32, .72, 0, 1)</dd>\n        <dt>通知堆疊</dt><dd>每層露出 12px；最多三層</dd>\n        </dl>\n        <p>附帶的提示詞會先讀取產品，逐條判斷每則提示該用 Toast、Notification 還是都不用，列成表格由你決定；確認後，還可以依展示效果改造 Toast 和 Notification。</p>"
      }
    },
    "017-loading-states": {
      "en": {
        "summary": "Spinner, Skeleton, Progress and optimistic updates: which kind of wait each of these four loading states suits.",
        "notes": "<p>Waiting is unavoidable. How users are told they are waiting affects how they feel and whether their work flows smoothly; sometimes the result should be shown first and then corrected if needed. The common ones are these four:</p>\n        <ol>\n        <li><strong>Spinner</strong>: For a single action that finishes within a few seconds, such as refreshing or syncing. After the press, the button’s own icon spins in place while its label and width stay the same; even if the result comes back at once, it turns at least one full circle and stops on a whole turn, and a Toast reports the result when it ends.</li>\n        <li><strong>Skeleton</strong>: When the page structure is known, such as a feed, a list or a chart. The title and filters appear first, and after 300ms a skeleton shows at the real row height; as content arrives it replaces the skeleton row by row in place, so the page does not jump. Do not put a lone spinning icon in the middle of a blank page.</li>\n        <li><strong>Progress</strong>: For long tasks that can be counted, such as uploading, importing or running diagnostics. A notification card shows the count, a progress bar and the time left, and the page stays usable; when done, the card changes in place into the result and stays until the user handles it.</li>\n        <li><strong>Optimistic</strong>: For actions that will very likely succeed and are easy to roll back, such as checking off a task, liking or renaming. Show the result first and save in the background; if the save fails, the change goes back to where it was, with the reason explained and a retry offered. Strictly speaking this is a strategy rather than a pattern, and it is not used for payments, permanent deletion or content sent to other people.</li>\n        </ol>\n        <p>Also, waits under 300ms get no separate loading state; otherwise it vanishes as soon as it appears and looks like a flicker. Once shown, it stays for at least 500ms. Use only one loading state per wait.</p>\n        <h2>Parameters</h2>\n        <dl class=\"params\">\n        <dt>Threshold</dt><dd>Nothing under 300ms; once shown, at least 500ms</dd>\n        <dt>Button icon</dt><dd>Turns from the press; at least one turn (640ms); ends on a whole turn</dd>\n        <dt>Skeleton</dt><dd>After 300ms; the light band crosses every 1.2s; rows replace it 40ms apart, each fading in over 200ms</dd>\n        <dt>Progress</dt><dd>Shows after about 0.5s; the time left after 1s of data</dd>\n        <dt>Optimistic</dt><dd>Shown at once; when the save fails, the row shakes 6px twice over 360ms</dd>\n        </dl>\n        <p>The included prompt first finds every place in the product where users wait, decides which approach each one should use, and lists them in a table for you to decide; once you confirm, it makes the changes to match the demo.</p>"
      },
      "text": {
        "summary": "Spinner、Skeleton、Progress 和樂觀更新，這四種載入狀態分別適合什麼樣的等待。",
        "notes": "<p>等待無法避免。如何告知使用者正在等待，會影響他們的情緒和操作是否流暢；有時應該先給出結果，再依實際情況更正。常見的有以下四種：</p>\n        <ol>\n        <li><strong>Spinner</strong>：幾秒內能完成的單一操作，例如重新整理、同步。按下後按鈕本身的圖示原地旋轉，文字和寬度不變；即使結果立刻傳回，也至少轉滿一圈並停在整圈，結束後用 Toast 告知結果。</li>\n        <li><strong>Skeleton</strong>：頁面結構已知時，例如動態消息、清單、圖表。標題和篩選先出現，300ms 後依實際列高顯示骨架；內容到達後逐列原地替換，頁面不跳動。不要在空白頁面中間只放一個旋轉圖示。</li>\n        <li><strong>Progress</strong>：可以計數的耗時任務，例如上傳、匯入、診斷。用通知卡片顯示數量、進度條和剩餘時間，頁面照常可用；完成後卡片原地變為結果，保留到使用者處理為止。</li>\n        <li><strong>Optimistic</strong>：大機率成功、也容易退回的操作，例如勾選完成、按讚、重新命名。先顯示結果，在背景儲存；儲存失敗時改動退回原處，說明原因並提供重試。嚴格來說這是一種策略而非模式，不用於付款、永久刪除和傳送給他人的內容。</li>\n        </ol>\n        <p>另外，300ms 以內的等待不顯示單獨的載入狀態，否則剛出現就消失，看起來像閃了一下；出現後至少保持 500ms。一次等待只用一種載入狀態。</p>\n        <h2>參數</h2>\n        <dl class=\"params\">\n        <dt>門檻</dt><dd>300ms 以內不顯示；出現後至少保持 500ms</dd>\n        <dt>按鈕圖示</dt><dd>按下即開始旋轉；至少轉一圈（640ms）；停在整圈</dd>\n        <dt>骨架</dt><dd>300ms 後出現；光帶每 1.2s 掃過一次；內容逐列替換，間隔 40ms，每列淡入 200ms</dd>\n        <dt>進度</dt><dd>約 0.5s 後顯示；取得 1s 的資料後顯示剩餘時間</dd>\n        <dt>樂觀更新</dt><dd>立即顯示；儲存失敗時，該列左右晃動 6px 兩次，共 360ms</dd>\n        </dl>\n        <p>附帶的提示詞會先找出產品中所有需要等待的地方，逐一判斷該用哪種方式，列成表格由你決定；確認後再依展示效果改造。</p>"
      }
    },
    "018-holo-card": {
      "en": {
        "summary": "A 3D holographic card that tilts and turns over, for cards that stand for status or ownership, such as member cards, tickets and badges.",
        "notes": "<p>When a real holographic card turns, color flows across its face. On screen, the pointer position stands in for the angle in your hand: a light spot that follows the pointer sets where the foil, glare and rim light up, and at rest the spot sits at the top left. The key points in building it:</p>\n        <ol>\n        <li><strong>Tilt</strong>: The card tilts toward the pointer, up to 12°, on a spring, and springs back slightly when the pointer leaves; when no one is using it, it keeps a slow 2–3° sway, as if held in a hand.</li>\n        <li><strong>Foil layer</strong>: Sits on top of the card’s base color and is brighter closer to the light spot. Text is printed above the foil layer, so it stays readable at any angle.</li>\n        <li><strong>Finishes</strong>: Six presets in all. Everyday products suit a quiet finish such as Pearl, or a tilt reduced to 6°; save Rainbow and Sparkle for moments worth celebrating, such as upgrading a membership or unlocking a rare achievement.</li>\n        <li><strong>Glare and rim</strong>: The glare spreads softly outward from the light spot; the rim is faint overall and only the part near the light spot is lit, so it comes and goes.</li>\n        <li><strong>Depth</strong>: The artwork on the card is spread across different depths, with offset = depth × sin(angle); as the card turns, the layers shift against each other, giving a real sense of three-dimensional space.</li>\n        <li><strong>Turning over</strong>: On click, the card turns 180° to its back on a spring, lifting slightly as it turns to show a 10px edge; the front content changes at the moment the card is edge-on, so the change cannot be seen.</li>\n        </ol>\n        <p>Also, put only one holographic card on a screen; when everything glows, nothing stands out. With “Reduce motion” on, the card does not tilt or sway, and turning over is not animated.</p>\n        <h2>Parameters</h2>\n        <dl class=\"params\">\n        <dt>Tilt</dt><dd>Up to 12° (6° for a quiet finish); spring stiffness 140, damping 15</dd>\n        <dt>Sway at rest</dt><dd>2 to 3°, slow; the light moves with it</dd>\n        <dt>Turning over</dt><dd>Spring stiffness 70, damping 11; lifts 40px; a 10px edge of 10 layers</dd>\n        <dt>Depth</dt><dd>Picture 90px behind, dial 50px, needle 12px in front</dd>\n        <dt>Rim</dt><dd>1.5px; lit near the light, fading out by 42%</dd>\n        <dt>Finishes</dt><dd>Prism, Rainbow, Pearl, Sparkle, Chrome, Etched</dd>\n        </dl>\n        <p>The included prompt first asks item by item which card to restyle, and about the finish, feel, interaction, depth and background, giving recommended values and a few presets for each; once you confirm, it builds the card with the project’s existing tech stack.</p>"
      },
      "text": {
        "summary": "會傾斜、能翻面的 3D 雷射卡片，適合會員卡、票券、徽章這類代表身分或收藏的卡片。",
        "notes": "<p>真實的雷射卡一轉動，顏色就在卡面上流動；螢幕上以指標位置代替手中的角度，由一個跟隨指標的光點同時決定雷射、反光和亮邊的位置，靜止時光點停在左上方。實作時有以下幾個要點：</p>\n        <ol>\n        <li><strong>傾斜</strong>：卡片朝指標方向傾斜，最大 12°，使用彈簧動畫，指標離開時輕微回彈；無人操作時保持 2–3° 的緩慢晃動，就像拿在手上一樣。</li>\n        <li><strong>雷射層</strong>：疊在卡片底色之上，越靠近光點越亮。文字印在雷射層之上，卡片轉到任何角度都清晰可讀。</li>\n        <li><strong>材質</strong>：共六種預設。日常使用的產品適合 Pearl 這類低調的材質，或把傾斜減到 6°；Rainbow 和 Sparkle 留給值得慶祝的時刻，例如升級會員、解鎖稀有成就。</li>\n        <li><strong>反光與亮邊</strong>：反光以光點為中心柔和地向外擴散；亮邊整體很淡，只有靠近光點的一段被照亮，所以若隱若現。</li>\n        <li><strong>視差層次</strong>：卡面裡的圖案分布在不同深度，位移 = 深度 × sin(角度)；卡片轉動時各層相對錯開，呈現真實的立體空間感。</li>\n        <li><strong>翻面</strong>：點擊後卡片以彈簧動畫翻轉 180° 到背面，翻轉時略微抬起，露出 10px 的厚度；正面內容在卡片側立的瞬間更換，所以看不到。</li>\n        </ol>\n        <p>另外，一個畫面只放一張雷射卡片，所有元素都在發光時就沒有重點了。開啟「減少動態效果」時，卡片不傾斜、不晃動，翻面也不播放動畫。</p>\n        <h2>參數</h2>\n        <dl class=\"params\">\n        <dt>傾斜</dt><dd>最大 12°（較低調的材質用 6°）；彈簧剛度 140，阻尼 15</dd>\n        <dt>靜止晃動</dt><dd>2–3°，緩慢；光點跟著移動</dd>\n        <dt>翻面</dt><dd>彈簧剛度 70，阻尼 11；抬起 40px；厚度 10px，由 10 層疊成</dd>\n        <dt>層次</dt><dd>背景在卡面後方 90px，刻度盤 50px，指針在卡面前方 12px</dd>\n        <dt>亮邊</dt><dd>1.5px；靠近光點處被照亮，到 42% 處完全消失</dd>\n        <dt>材質</dt><dd>Prism、Rainbow、Pearl、Sparkle、Chrome、Etched</dd>\n        </dl>\n        <p>附帶的提示詞會先逐項詢問要改造哪一張卡片，以及材質、手感、互動、層次和背景，每項提供建議參數和幾組預設；確認後再依專案現有的技術架構實作。</p>"
      }
    },
    "019-scroll-cards": {
      "en": {
        "summary": "Five scroll-driven card interactions (stacked cards, card deck, pinned gallery, cover flow, image expand) for product sites and portfolios.",
        "notes": "<p>When scrolling a page, users expect elements to move vertically; these effects turn scrolling into sideways, rotating or irregular motion, which is why they feel fresh. They are all driven directly by the scroll position: stop halfway and the effect stops halfway; scroll back and the effect plays in reverse.</p>\n        <ol>\n        <li><strong>Stacked cards</strong>: Suits three to five parallel items that each take up a screen. Cards stack one on another as the page scrolls, each sticking 16px lower than the one before; each layer of covered cards shrinks by 0.05 and darkens by 12%, and the thin strips showing at the top are the content already seen.</li>\n        <li><strong>Card deck</strong>: Suits a small amount of content shown one item at a time. Every 420px of scrolling, the top card is flung to one side along an arc, alternating left and right and turning up to 16°; the cards below each move up one place.</li>\n        <li><strong>Pinned gallery</strong>: Suits a row of work wider than the screen. The page holds still for a while, and each 1px scrolled down moves the row 1px to the left, with no easing; a counter and a progress bar show how far the reader has got.</li>\n        <li><strong>Cover flow</strong>: Suits content of the same shape that is viewed one item at a time. Every 320px of scrolling, the next cover moves to the middle; the covers on either side shrink, turn up to 30° and darken step by step, drawing the eye to the middle.</li>\n        <li><strong>Image expand</strong>: Suits a main image that leads into the next chapter. The small image grows to fill the screen as the page scrolls, while scaling back from 1.2× to 1×; the title hides behind the mountain (cut out as a separate layer) and rises at a quarter of the speed, creating depth.</li>\n        </ol>\n        <p>Also, use each effect at most once on a page, with ordinary sections in between; do not change the scroll speed or force snapping, and change only transform, opacity and clip-path. With “Reduce motion” on, or when the viewport is shorter than 560px, every effect falls back to an ordinary section.</p>\n        <h2>Parameters</h2>\n        <dl class=\"params\">\n        <dt>Stacked cards</dt><dd>Sticky top 40px + i × 16px; scale 1 − k × 0.05, shade k × 0.12; k rises by 1 every 752px</dd>\n        <dt>Card deck</dt><dd>420px per card; x = side × t² × 1000px, rotate side × t × 16°; 18px and 0.05 per place below</dd>\n        <dt>Pinned gallery</dt><dd>Height 100vh + row overflow (1520px); 1px down = 1px sideways</dd>\n        <dt>Cover flow</dt><dd>320px per cover; 260px apart, 30° turn, scale down to 0.6, shade 0.15 per place</dd>\n        <dt>Image expand</dt><dd>Grows over 900px, holds 300px; frame 584 × 352 to full screen; picture 1.2× to 1×</dd>\n        </dl>\n        <p>The included prompt is for restyling an existing page: it first asks which sections to change, and about length, phones and short screens, reduced motion and the implementation, giving recommended values and a few presets for each; once you confirm, it builds them with the project’s existing tech stack.</p>"
      },
      "text": {
        "summary": "五種由捲動驅動的卡片互動：堆疊卡片、卡組飛出、橫向展廊、封面輪播和圖片展開，適合產品官網和作品集。",
        "notes": "<p>捲動頁面時，使用者預期看到元素直向移動；這幾種效果把捲動轉成橫向、旋轉或不規則的運動，所以顯得新鮮。它們都由捲動位置直接驅動：停在一半，效果就停在一半；往回捲，效果隨之倒著播放。</p>\n        <ol>\n        <li><strong>堆疊卡片</strong>：適合三到五個各佔一個畫面的並列項目。卡片隨捲動逐層疊加，每張固定在頂部的位置比上一張低 16px；被蓋住的卡片每層縮小 0.05、變暗 12%，頂部露出的細條就是看過的內容。</li>\n        <li><strong>卡組飛出</strong>：適合逐一展示的少量內容。每捲動 420px，最上面的卡片沿弧線往一側甩出，左右交替，最多旋轉 16°；下面的卡片依序上移一層。</li>\n        <li><strong>橫向展廊</strong>：適合比螢幕更寬的一列作品。頁面暫時固定，每往下捲 1px，作品列就向左移 1px，不加緩動；計數和進度條顯示看到了哪裡。</li>\n        <li><strong>封面輪播</strong>：適合形狀相同、一次只看一個的內容。每捲動 320px，下一張封面移到中間；兩側封面縮小、最多旋轉 30°、逐層變暗，把視線集中到中間。</li>\n        <li><strong>圖片展開</strong>：適合一張能帶出下一章的主圖。小圖隨捲動鋪滿螢幕，同時從 1.2 倍縮回 1 倍；標題藏在山的後面（山單獨去背成一層），以四分之一的速度升起，形成景深。</li>\n        </ol>\n        <p>另外，每種效果在一個頁面中最多用一次，中間穿插一般段落；不改變捲動速度，不強制吸附，只改 transform、opacity 和 clip-path。開啟「減少動態效果」或視窗高度低於 560px 時，都退回一般段落。</p>\n        <h2>參數</h2>\n        <dl class=\"params\">\n        <dt>堆疊卡片</dt><dd>固定位置 40px + i × 16px；縮放 1 − k × 0.05，變暗 k × 0.12；k 每捲動 752px 增加 1</dd>\n        <dt>卡組飛出</dt><dd>每張 420px；橫移 方向 × t² × 1000px，旋轉 方向 × t × 16°；下方每層低 18px、小 0.05</dd>\n        <dt>橫向展廊</dt><dd>高度 100vh + 作品列超出的寬度（1520px）；往下 1px = 橫向 1px</dd>\n        <dt>封面輪播</dt><dd>每張 320px；間距 260px，旋轉 30°，最小縮放 0.6，每層變暗 0.15</dd>\n        <dt>圖片展開</dt><dd>在 900px 內鋪滿，再停留 300px；畫框 584 × 352 到全螢幕；圖片 1.2 倍到 1 倍</dd>\n        </dl>\n        <p>附帶的提示詞用於改造現有頁面：先問你要改造哪幾段，以及長度、手機與矮螢幕、減少動態效果和實作方式，每項提供建議值和幾組預設；確認後依專案現有的技術架構實作。</p>"
      }
    },
    "020-choice-controls": {
      "en": {
        "summary": "When to use a switch, checkbox, radio button, segmented control, select or dropdown menu.",
        "notes": "<p>These controls look alike and are often mixed up. For example, a settings page has a switch to flip, yet there is also a Save button below it, and the setting does not take effect once the user leaves the page. The differences are explained below in four pairs:</p>\n        <ol>\n        <li><strong>Switches and checkboxes</strong>: The difference is when the change takes effect. A switch takes effect as soon as it is flipped and suits auto-saving contexts such as settings pages, with no Save button next to it; checkboxes are submitted with a form and need a submit button. Represent turning one thing on and off with a single switch, not two radio buttons for “On” and “Off”.</li>\n        <li><strong>Selects and dropdown menus</strong>: A select holds values, and the chosen one shows in the box, such as a language; a dropdown menu holds actions, which run as soon as they are clicked while the button label stays the same, and is often used to tuck away buttons in a toolbar or at the top of a page. The most used action can be the main button, with an icon button beside it opening the rest, such as “Schedule send” and “Save as draft” next to “Send”.</li>\n        <li><strong>Segmented controls and selects</strong>: Both are for picking one. Use a segmented control for 2–5 short options, which can be taken in at a glance; when each option needs a line of explanation, use radio buttons stacked vertically instead. Use a select when there are more options, the text is long, or the options change (names, dates, items users add), so the interface does not jump; for up to hundreds (time zones, countries), add a search box at the top of the list and a clear message for when nothing matches.</li>\n        <li><strong>Radio buttons and checkboxes</strong>: Radio buttons suit single-choice questions where all options should be read, as in a survey; once a choice is made it cannot be cleared, so provide an option such as “Not sure yet”; when several can be picked, use checkboxes. The same goes inside a select: for a single choice, put a check mark after the chosen item instead of drawing a radio circle; for multiple choice, put a checkbox before each item.</li>\n        </ol>\n        <p>Also, the result of every control must be visible right away: turning on desktop notifications immediately shows a notification; after “Export data” runs from a dropdown menu, a Toast reports the result.</p>\n        <h2>Parameters</h2>\n        <dl class=\"params\">\n        <dt>Number of options</dt><dd>2–5 short options: segmented control; 2–5 that each need explaining: radio buttons; 6 or more: select; hundreds: select with search</dd>\n        <dt>Switch</dt><dd>40×24px, 8px corners; 18px thumb; 220ms, cubic-bezier(.32, .72, 0, 1)</dd>\n        <dt>Segmented control</dt><dd>36px tall, 4px padding; 28px thumb, 8px corners; 280ms</dd>\n        <dt>Option list</dt><dd>36px options; 14px corners; opens in 180ms, closes in 120ms</dd>\n        <dt>Radio buttons and checkboxes</dt><dd>18px; radio buttons round, checkboxes with 5px corners</dd>\n        </dl>\n        <p>The included prompt first finds every selection control in the product, decides whether each one is used correctly and what it should change to, and lists them in a table for you to decide; once you confirm, it changes them one by one according to these rules.</p>"
      },
      "text": {
        "summary": "開關、核取方塊、單選按鈕、分段控制項、下拉式清單和下拉式選單，分別適合什麼情境。",
        "notes": "<p>這幾個控制項外觀相近，經常被混用。例如設定頁裡切換了開關，下面卻還有一個儲存按鈕，使用者離開頁面後設定並沒有生效。下面分四組說明區別：</p>\n        <ol>\n        <li><strong>開關與核取方塊</strong>：區別在於何時生效。開關切換後立即生效，適合設定頁這類自動儲存的情境，旁邊不放儲存按鈕；核取方塊隨表單一起送出，需要搭配送出按鈕。一件事的開與關用一個開關表示，不用「開／關」兩個單選按鈕。</li>\n        <li><strong>下拉式清單與下拉式選單</strong>：下拉式清單裡是值，選取後顯示在框中，例如語言；下拉式選單裡是動作，點擊後立即執行，按鈕文字不變，常用於收納工具列或頁面頂部的按鈕。最常用的動作可以做成主按鈕，旁邊用圖示按鈕展開其餘動作，例如「傳送」旁邊的「排程傳送」「儲存為草稿」。</li>\n        <li><strong>分段控制項與下拉式清單</strong>：都用於單選。2–5 個簡短的選項用分段控制項，一目了然；每項需要一行說明時，改用上下排列的單選按鈕。選項更多、文字較長，或者會變化（人名、日期、使用者新增的項目）時用下拉式清單，以免介面跳動；多達幾百個時（時區、國家），在清單頂部加上搜尋框，並做好沒有結果時的提示。</li>\n        <li><strong>單選按鈕與核取方塊</strong>：單選按鈕適合問卷這類需要讀完所有選項的單選題，選取後無法取消，所以要提供「暫不確定」之類的選項；可以選多個時用核取方塊。下拉式清單裡也一樣：單選時在選取項後打勾，不畫單選圓圈；多選時在每項前放核取方塊。</li>\n        </ol>\n        <p>另外，每個控制項的結果都要立刻可見：開啟桌面通知後馬上跳出一則通知；下拉式選單執行「匯出資料」後，用 Toast 告知結果。</p>\n        <h2>參數</h2>\n        <dl class=\"params\">\n        <dt>選項數量</dt><dd>2–5 個短選項用分段控制項；2–5 個、每項需要說明用單選按鈕；6 個以上用下拉式清單；幾百個用附搜尋功能的下拉式清單</dd>\n        <dt>開關</dt><dd>40×24px，圓角 8px；滑塊 18px；切換 220ms，cubic-bezier(.32, .72, 0, 1)</dd>\n        <dt>分段控制項</dt><dd>高 36px，內距 4px；滑塊高 28px，圓角 8px；切換 280ms</dd>\n        <dt>選項清單</dt><dd>選項高 36px；圓角 14px；展開 180ms，收起 120ms</dd>\n        <dt>單選按鈕與核取方塊</dt><dd>18px；單選按鈕為圓形，核取方塊圓角 5px</dd>\n        </dl>\n        <p>附帶的提示詞會先找出產品中所有的選擇控制項，逐一判斷是否用對、應換成哪一種，列成表格由你決定；確認後再依規則逐一改造。</p>"
      }
    },
    "021-ring-cards": {
      "en": {
        "summary": "A set of cards arranged in a ring: seen from inside, their edges pass through glass with a color fringe; seen from outside, they have depth of field; on the cards, a flowing fluid gradient.",
        "notes": "<p>A typical card carousel is just a row of cards sliding left and right. Lay the same row out on a ring and the cards gain distance: from inside, the side cards wrap around the viewer; from outside, the middle is sharp and the farther cards blur. The key points:</p>\n        <ol>\n        <li><strong>Two views</strong>: The cards sit along one arc. With a positive curvature the viewer is inside the ring, with a negative one outside. Change the curvature continuously when switching, and the whole row bends smoothly from one ring into the other.</li>\n        <li><strong>Inside</strong>: Suits content people browse at leisure, like portfolios and galleries. The viewer stands a little behind the ring’s center, perspective 860px; the side cards are closer and larger, and five cards fit on screen.</li>\n        <li><strong>Glass rim</strong>: A 160px band of glass at each side of the frame. The closer to the outer edge, the further toward the middle it samples, so the cards’ top and bottom edges flare out; red shifts more than blue, giving a soft color fringe.</li>\n        <li><strong>Outside and depth of field</strong>: Suits places where people look at one item at a time, like picking a cover. The ring is seen at eye level, perspective 1500px; the middle stays sharp, and the sides and the far side blur and fade. The blur is worked out per pixel, so nothing shimmers as the ring turns.</li>\n        <li><strong>Fluid gradient and turning over</strong>: Each card’s front is a fluid gradient of four colors that flows slowly around a circle and loops seamlessly. Switching to outside turns the cards over one after another, from the middle out, to show the picture on the back.</li>\n        </ol>\n        <p>Also, the cards have no shadow or reflection, which looks dirty on a white page; distance comes only from size, blur and fade. With “Reduce motion” on, the gradients stop flowing and the view switches at once.</p>\n        <h2>Parameters</h2>\n        <dl class=\"params\">\n        <dt>Cards</dt><dd>180 × 300px, 18px apart, 22 in all; ring radius about 693px</dd>\n        <dt>Inside</dt><dd>perspective 860px; glass rim 160px, offset 0.4 × its width, falloff exponent 2.4; dispersion 25%</dd>\n        <dt>Outside</dt><dd>perspective 1500px; blur starts 110px from the center, up to 14px; far side faded 50%</dd>\n        <dt>Fluid</dt><dd>4 colors, 3 layers of noise warped twice; flows 0.2 noise cells per second</dd>\n        <dt>Corners</dt><dd>continuous corners, superellipse(2), 32px</dd>\n        <dt>Switching</dt><dd>view 1100ms; turning over 1800ms, from the middle out</dd>\n        </dl>\n        <p>The included prompt first asks where it goes, what the cards hold, which view it opens in and who sees the settings panel; once confirmed, it builds the effect with the values in the video, plus a slider panel for tuning them live.</p>"
      },
      "text": {
        "summary": "沿圓環排開的一組卡片：從環內看，邊緣經過玻璃並帶有色散；從環外看，有景深；卡片上是流動的流體漸層。",
        "notes": "<p>常見的卡片輪播只是一排卡片左右平移。把同一排卡片沿圓環排開，卡片就有了遠近：從環內看，兩側的卡片朝觀眾包圍過來；從環外看，正中清晰，越遠越模糊。實作時有以下幾個重點：</p>\n        <ol>\n        <li><strong>兩種視角</strong>：卡片沿同一條弧線排開，曲率為正時觀眾在環內，為負時在環外。切換時讓曲率連續變化，整排卡片會從一種圓環平順地彎成另一種。</li>\n        <li><strong>環內</strong>：適合作品集、相簿這類希望讀者沉浸瀏覽的內容。觀眾站在圓環中心稍後的位置，透視距離 860px，兩側卡片更近、更大，一個畫面可見五張。</li>\n        <li><strong>玻璃邊</strong>：畫面左右各一條 160px 的玻璃邊，越靠近外緣，越朝畫面中心取樣，卡片的上下邊因此向外張開；紅光偏移多、藍光偏移少，形成柔和的色散。</li>\n        <li><strong>環外與景深</strong>：適合挑選封面這類一次只看一張的情境。平視整個圓環，透視距離 1500px；正中保持清晰，往兩側和後排逐漸模糊、淡化。模糊逐像素計算，卡片轉動時不會閃爍。</li>\n        <li><strong>流體漸層與翻面</strong>：卡片正面是四種顏色的流體漸層，沿圓周緩慢流動，可以無縫循環。切到環外時，卡片從中間往兩側依序翻面，露出背面的圖片。</li>\n        </ol>\n        <p>另外，卡片不加陰影和倒影，在白底上會顯得髒，遠近只靠大小、模糊和淡化呈現。開啟「減少動態效果」時，漸層停止流動，視角直接切換。</p>\n        <h2>參數</h2>\n        <dl class=\"params\">\n        <dt>卡片</dt><dd>180 × 300px，間距 18px，共 22 張；圓環半徑約 693px</dd>\n        <dt>環內</dt><dd>透視 860px；玻璃邊 160px，偏移為邊寬的 0.4 倍，衰減指數 2.4；色散 25%</dd>\n        <dt>環外</dt><dd>透視 1500px；距中心 110px 外開始模糊，最多 14px；後排淡化 50%</dd>\n        <dt>流體</dt><dd>4 種顏色，3 層雜訊扭曲兩次；每秒流動 0.2 個雜訊單位</dd>\n        <dt>圓角</dt><dd>連續圓角 superellipse(2)，32px</dd>\n        <dt>切換</dt><dd>視角 1100ms；翻面 1800ms，從中間往兩側依序進行</dd>\n        </dl>\n        <p>附帶的提示詞會先詢問放置位置、卡片內容、預設視角和參數面板的顯示方式；確認後依影片中的參數實作，並附上可即時調整的滑桿面板。</p>"
      }
    }
  },
  "privacy": {
    "en": "<h1>Privacy Policy</h1>\n    <p class=\"policy-date\">Last updated and effective: November 18, 2026</p>\n    <p class=\"policy-lead\">Vibe Design Tips (vibedesign.tips, “the site”, “we” or “us”) is a free website of design tips, run by an independent developer. You can read everything on the site without signing in; signing in is needed only to save tips, highlight passages and download Skills. This policy explains what information we collect, how we use and keep it, and the rights you have. Please read it before signing in.</p>\n\n    <h2>1. Information we collect</h2>\n    <h3>1.1 When you sign in</h3>\n    <p>When you sign in with Google, GitHub or X, we ask only to read your public profile, and we store:</p>\n    <ul>\n      <li>Your account identifier: the user ID that Google, GitHub or X provides, used to recognise the same account;</li>\n      <li>Your display name and the address of your profile picture, and, if you sign in with GitHub or X, your username (@handle).</li>\n    </ul>\n    <p>This information is refreshed from your Google, GitHub or X profile each time you sign in.</p>\n    <h3>1.2 When you use the site’s features</h3>\n    <p>Once you are signed in, the following is stored with your account:</p>\n    <ul>\n      <li>the tips you save;</li>\n      <li>the passages you highlight;</li>\n      <li>records of your reader keys: a hash of each key and its last four characters, when it was created, when it was last used, and how many reads it made that day. We do not store the keys themselves.</li>\n    </ul>\n    <h3>1.3 Information we do not collect</h3>\n    <p>We do not read your email address, we do not keep access tokens from Google, GitHub or X (the GitHub token is revoked as soon as your profile has been read), and we never post anything on your behalf. X’s consent screen lists permission to read posts; X requires it together with access to your profile, and the site does not use it.</p>\n\n    <h2>2. How we use information</h2>\n    <p>We use the information above only to:</p>\n    <ul>\n      <li>recognise your account and keep you signed in;</li>\n      <li>provide saving, highlighting and reader keys, and keep them in sync across your devices;</li>\n      <li>show the first 999 accounts (early members) in the site’s public member list, by display name and profile picture and in the order they signed up, unless the member turns this off;</li>\n      <li>prevent abuse and protect the site and your account;</li>\n      <li>count visits so that we can improve the site’s content.</li>\n    </ul>\n    <p>We do not use your information for advertising or profiling.</p>\n\n    <h2>3. Cookies and local storage</h2>\n    <ul>\n      <li>Sign-in cookie: keeps you signed in. It expires after 30 days and is cleared when you sign out;</li>\n      <li>Sign-in marker cookie: contains no personal information and only tells the page that this device may be signed in, so that visitors who are not signed in make no account request;</li>\n      <li>Your browser’s local storage: keeps preferences such as theme, language and the sign-in method you used last. It stays on your device and is not sent to us.</li>\n    </ul>\n    <p>The site uses no advertising or cross-site tracking cookies.</p>\n\n    <h2>4. Third-party services</h2>\n    <p>We rely on the following services to run the site. Each handles information only as far as needed to provide its service:</p>\n    <ul>\n      <li>Cloudflare: hosts the site and its database and handles network requests;</li>\n      <li>Google, GitHub and X: verify your identity when you choose to sign in with them;</li>\n      <li>Umami: counts page views and feature use. It uses no cookies, records only totals, and does not identify anyone.</li>\n    </ul>\n    <p>We do not sell your information or give it to anyone else, except where the law requires it.</p>\n\n    <h2>5. Storage and retention</h2>\n    <ul>\n      <li>Your profile, saves, highlights and reader key records are kept in Cloudflare’s database until you delete your account;</li>\n      <li>Sign-in sessions expire after 30 days;</li>\n      <li>To prevent abuse, sign-ins and API requests are counted per IP address. The counts are used only for rate limits, lapse by the next midnight (UTC) at the latest, and are then deleted.</li>\n    </ul>\n    <p>Cloudflare operates its network in many regions, so your information may be processed outside the country or region where you live.</p>\n\n    <h2>6. Security</h2>\n    <p>All traffic to the site is encrypted with HTTPS. Sign-in session tokens and reader keys are stored only as hashes, so a leak of the database could not be used to sign in or to read. No online service can promise absolute security, however; if a security incident occurs, we will announce it promptly on the site and on X.</p>\n\n    <h2>7. Your rights</h2>\n    <ul>\n      <li>Access: once signed in, you can see your profile, saves and reader keys in the account menu;</li>\n      <li>Correction: your name and picture follow your Google, GitHub or X profile; change them there and sign in again;</li>\n      <li>Deleting content: you can remove saves, delete highlights or revoke reader keys at any time;</li>\n      <li>Member list: if you are an early member, you can leave your name and picture out of the public member list at any time with the switch in the list, which opens from the 999 nameplate in the account menu. Your place then shows only as taken;</li>\n      <li>Signing out: clears the sign-in on this device;</li>\n      <li>Deleting your account: send a direct message to <a href=\"https://x.com/kubai087\">@kubai087</a> on X with how you signed in and your display name. Deleting your account removes your profile, saves, highlights and reader keys together, and cannot be undone.</li>\n    </ul>\n\n    <h2>8. About the ways to sign in</h2>\n    <div class=\"policy-callout\">\n      <p>Signing in with Google, with GitHub and with X creates three separate accounts. Saves, highlights and reader keys belong to one account and do not carry over to the others; they cannot be merged at present.</p>\n      <p>We recommend signing in the same way each time. The sign-in dialog marks the method this device used last.</p>\n    </div>\n\n    <h2>9. Children</h2>\n    <p>The site is intended for a general audience and is not directed at children under 14. We do not knowingly collect personal information from children; if you believe a child has signed in without a parent’s or guardian’s consent, please contact us and we will delete the account.</p>\n\n    <h2>10. Changes to this policy</h2>\n    <p>We may update this policy as the site’s features change. When we do, we will update this page and the date above, and for significant changes we will also give notice in a prominent place on the site.</p>\n\n    <h2>11. Contact us</h2>\n    <p>If you have any questions about this policy or your personal information, please contact <a href=\"https://x.com/kubai087\">@kubai087</a> on X.</p>",
    "text": "<h1>隱私權政策</h1>\n    <p class=\"policy-date\">更新及生效日期：2026 年 11 月 18 日</p>\n    <p class=\"policy-lead\">Vibe Design Tips（vibedesign.tips，以下簡稱「本站」或「我們」）是一個免費的設計技巧網站，由個人開發者經營。您不需登入即可閱讀本站所有內容；只有在使用收藏、螢光標記和下載 Skill 等功能時，才需要登入。本政策說明我們蒐集哪些資訊、如何使用及保存這些資訊，以及您享有的權利。請您在登入前詳細閱讀。</p>\n\n    <h2>一、我們蒐集的資訊</h2>\n    <h3>1. 登入時取得的資訊</h3>\n    <p>您使用 Google、GitHub 或 X 帳號登入時，我們僅向對方要求讀取您的公開個人資料，並保存以下資訊：</p>\n    <ul>\n      <li>帳號識別碼：Google、GitHub 或 X 提供的使用者 ID，用於辨識同一個帳號；</li>\n      <li>顯示名稱和大頭貼圖片網址；使用 GitHub 或 X 登入時，還包括使用者名稱（@handle）。</li>\n    </ul>\n    <p>以上資訊會在您每次登入時，依 Google、GitHub 或 X 上的最新個人資料更新。</p>\n    <h3>2. 使用功能時產生的資訊</h3>\n    <p>登入後，以下內容會與您的帳號一併保存：</p>\n    <ul>\n      <li>您收藏的技巧；</li>\n      <li>您加上螢光標記的文字段落；</li>\n      <li>讀取金鑰的相關紀錄：金鑰的雜湊值和最後 4 個字元、建立時間、最近使用時間，以及當日讀取次數。我們不保存金鑰本身。</li>\n    </ul>\n    <h3>3. 我們不蒐集的資訊</h3>\n    <p>我們不讀取您的電子郵件地址，不保存 Google、GitHub 或 X 的存取權杖（GitHub 的權杖在讀取個人資料後立即撤銷），也不會以您的名義發布任何內容。X 的授權頁面會列出「讀取貼文」權限，這是 X 在讀取個人資料時要求一併授予的權限，本站不會使用。</p>\n\n    <h2>二、我們如何使用資訊</h2>\n    <p>我們僅將上述資訊用於以下目的：</p>\n    <ul>\n      <li>辨識您的帳號，並維持登入狀態；</li>\n      <li>提供收藏、螢光標記和讀取金鑰等功能，並在您的各個裝置之間同步；</li>\n      <li>在本站公開的早期使用者名單中，依註冊順序顯示前 999 個帳號（早期使用者）的顯示名稱和大頭貼；使用者關閉顯示者除外；</li>\n      <li>防止濫用，保護本站和您帳號的安全；</li>\n      <li>統計瀏覽情形，以改善本站內容。</li>\n    </ul>\n    <p>我們不會將您的資訊用於廣告投放或使用者分析。</p>\n\n    <h2>三、Cookie 和本機儲存空間</h2>\n    <ul>\n      <li>登入 Cookie：用於維持登入狀態，有效期限 30 天，登出時清除；</li>\n      <li>登入標記 Cookie：不含任何個人資訊，僅用於告知頁面這台裝置可能已登入，讓未登入的訪客不必向帳號介面發出請求；</li>\n      <li>瀏覽器的本機儲存空間：用於保存主題、語言、上次使用的登入方式等偏好設定，僅存放在您的裝置上，不會傳送給我們。</li>\n    </ul>\n    <p>本站不使用廣告 Cookie 或跨網站追蹤 Cookie。</p>\n\n    <h2>四、第三方服務</h2>\n    <p>為經營本站，我們使用以下第三方服務。這些服務僅在提供相應服務所需的範圍內處理資訊：</p>\n    <ul>\n      <li>Cloudflare：代管網站和資料庫，並處理網路請求；</li>\n      <li>Google、GitHub 和 X：在您選擇以對應方式登入時，提供身分驗證；</li>\n      <li>Umami：統計頁面瀏覽量和功能使用次數。不使用 Cookie，只記錄彙總數據，不會用於識別個人。</li>\n    </ul>\n    <p>我們不會出售您的資訊，也不會提供給其他任何人，但法律另有規定者除外。</p>\n\n    <h2>五、資訊的儲存與保留</h2>\n    <ul>\n      <li>個人資料、收藏、螢光標記和讀取金鑰紀錄保存在 Cloudflare 的資料庫中，直到您刪除帳號為止；</li>\n      <li>登入工作階段在 30 天後失效；</li>\n      <li>為防止濫用，登入和 API 請求會依 IP 位址計數。計數僅用於頻率限制，最遲在次日零點（UTC）失效，失效後即刪除。</li>\n    </ul>\n    <p>Cloudflare 在全球多個地區營運網路，您的資訊可能會在您所在國家或地區以外的地方處理。</p>\n\n    <h2>六、資訊安全</h2>\n    <p>本站所有連線皆以 HTTPS 加密傳輸。登入工作階段權杖和讀取金鑰在資料庫中只保存雜湊值，即使資料庫內容外洩，也無法用於登入或讀取。儘管如此，任何網路服務都無法保證絕對安全；如發生資安事件，我們會盡快在本站及 X 上公告。</p>\n\n    <h2>七、您的權利</h2>\n    <ul>\n      <li>查閱：登入後，您可以在帳號選單中查看本站保存的個人資料、收藏和讀取金鑰；</li>\n      <li>更正：顯示名稱和大頭貼會依 Google、GitHub 或 X 上的個人資料更新，請在該處修改後重新登入；</li>\n      <li>刪除部分內容：您可以隨時取消收藏、刪除螢光標記或撤銷讀取金鑰；</li>\n      <li>早期使用者名單：如您是早期使用者，可隨時透過名單中的開關，選擇不在公開名單中顯示名稱和大頭貼。名單可從帳號選單中的 999 銘牌開啟。關閉後，您的位置只會顯示為已有人使用；</li>\n      <li>登出：清除這台裝置上的登入狀態；</li>\n      <li>刪除帳號：請在 X 上私訊 <a href=\"https://x.com/kubai087\">@kubai087</a>，並說明您的登入方式和顯示名稱。帳號刪除後，個人資料、收藏、螢光標記和讀取金鑰將一併刪除，且無法復原。</li>\n    </ul>\n\n    <h2>八、關於不同的登入方式</h2>\n    <div class=\"policy-callout\">\n      <p>使用 Google、GitHub 和 X 登入，會分別建立三個獨立的帳號。收藏、螢光標記和讀取金鑰分別保存在各自的帳號中，不會互通，目前也無法合併。</p>\n      <p>建議您每次都使用同一種方式登入。登入視窗會標示這台裝置上次使用的登入方式。</p>\n    </div>\n\n    <h2>九、兒童</h2>\n    <p>本站以一般讀者為對象，並非針對未滿 14 歲的兒童。我們不會在知情的情況下蒐集兒童的個人資訊；如您發現有兒童在未經父母或監護人同意的情況下登入本站，請與我們聯絡，我們會刪除該帳號。</p>\n\n    <h2>十、本政策的修訂</h2>\n    <p>本政策可能隨本站功能的變化而修訂。修訂後，我們會更新本頁內容和上方的日期；如有重大變更，也會在本站明顯位置提供通知。</p>\n\n    <h2>十一、聯絡我們</h2>\n    <p>如您對本政策或您的個人資訊有任何疑問，請在 X 上聯絡 <a href=\"https://x.com/kubai087\">@kubai087</a>。</p>"
  }
}
