Communitygithub.com

xzedm/clipplic-landing

Web 介面佈局結構,涵蓋分組、對齊、閱讀順序、漸進式揭露與自適應斷點。適用於頁面或元件結構設計、間距或控制項對齊、決定小尺寸下的折疊行為、處理 RTL 佈局方向,或檢視前端程式碼的佈局。觸發於佈局、間距、對齊、分組、留白、視覺層級、閱讀順序、漸進式揭露、斷點、響應式佈局、容器查詢、安全區域、滿版、邊到邊、佈局邊距、RTL 佈局、邏輯屬性。

clipplic-landing 是什麼?

這是一個專門用於 Web 介面佈局結構的 AI 技能,旨在幫助開發者建立清晰、可適應且具備視覺層級的 UI 佈局。該技能涵蓋從基本的分組與對齊,到進階的漸進式揭露、自適應斷點與 RTL 佈局支援,強調使用留白而非分隔線來分組內容、保持控制項與內容的視覺區別,以及根據重要性排序內容。此技能支援 Tailwind、純 CSS 或 CSS-in-JS 等主流樣式系統,並提供具體的數值起點(如 8px 組內間距、12px 控制項間距)以及常見錯誤的修正對策。在代碼審查模式下,它會產出結構化的審查報告,包含嚴重性分級(HIGH/MEDIUM/LOW)、問題位置、前後對比與違反原則說明,並在審查結束時給出「阻擋」、「需修改」或「通過」的裁決。

相容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/xzedm/clipplic-landing/tree/HEAD/.agents/skills/better-layout

在你喜歡的 AI 中提問

開啟一個已預先載入此 Agent Skill 的新對話。

說明文件

傳達結構的佈局

佈局在閱讀任何文字之前就已開始傳達訊息:位置、間距和對齊本身就能承載層級,而充足的留白勝過裝飾。一個好的佈局也必須經得起考驗:調整大小、翻譯、為 RTL 鏡像處理,它仍然應該保持完整。在建立或審查 UI 程式碼時應用這些原則,並使用專案現有的樣式系統(Tailwind、純 CSS、CSS-in-JS)來表達每個變更;切勿引入第二種樣式方法。

點擊區域大小和焦點行為由 better-accessibility 技能涵蓋;視覺修飾(圓角、陰影、動畫)由 better-ui 技能涵蓋;行長和文字間距由 better-typography 技能涵蓋。

將下面的數值視為尚未建立密度或間距系統的介面的起點。當專有平台 chrome、緊湊的專業工具和專案 token 在點擊區域、縮放、在地化和視口壓力測試中仍然可用時,請保留它們。

快速參考

類別使用時機
分組與對齊間距 vs 分隔線、對齊邊緣、邏輯屬性、重要性排序
間距與適應性目標之間的間距、佈局邊距、漸進式揭露、滿版內容、斷點、國際化字串增長

核心原則

1. 用間距分組,而非線條

留白是主要的分組工具;其次是背景形狀;分隔線是最後的手段,僅在空間本身無法承載結構時使用。組與組之間的間隙必須至少是組內間隙的 2 倍(8px 組內 → 16px 以上組間),否則分組會變成一種視覺噪音。

2. 保持控制項與內容有別

互動元素必須看起來是可互動的:一個背景形狀、一個邊框或一個一致的放置區域。切勿將控制項樣式設置得與相鄰的靜態文字相同。

3. 對齊到共享邊緣

選擇對齊邊緣並堅持使用;每一個偏離的邊緣都會造成視覺噪音。對每個從屬層級使用一個專案的間距步長(16px 是一個有用的預設值)。使用邏輯屬性(padding-inline-start、margin-inline-end)進行依賴方向的佈局;將物理的 left/right 保留給真正需要物理幾何的場景。

4. 按重要性排序

最重要的內容靠近頂部和起始邊緣;閱讀順序從上到下,從起始到結尾。以起始/結尾來思考,而非左/右。

5. 暗示隱藏內容

漸進式揭露需要一個可見的提示。使用專案既定的提示;如果沒有提示,讓下一個項目在滾動邊緣露出 16-32px 或顯示一個揭露控制項。沒有任何提示而隱藏的內容,基本上等於不存在。

6. 目標之間的呼吸空間

如果沒有既定的密度系統,從相鄰有邊框或填充的控制項之間保留 12px 開始,對於無邊框的文字和圖標控制項,周圍則保留 24px 的淨空。緊湊佈局可以使用更小的間距,前提是 better-accessibility 的點擊區域不重疊,且控制項在視覺上仍然清晰可辨。

7. 將按鈕從邊緣內縮

在內容佈局中,將全寬按鈕保留在佈局邊距內(行動裝置上從約 16px 內聯邊距開始),並帶有可見的圓角。當邊到邊的操作有意遵循既定的平台或應用程式 chrome、考慮安全區域,並且仍能與系統 UI 區分開來時,是可以接受的。

8. 內容溢出,控制項浮動

背景和媒體延伸到視口邊緣;控制項和文字保留在佈局邊距和安全區域(env(safe-area-inset-*))內。固定位置的 chrome 浮動在內容層之上,而不是將其阻斷。

9. 在內容撐破佈局之前保持結構

斷點來自於內容,而非裝置預設值。在內容確實合適的情況下,盡可能維持展開的佈局,並盡量延遲折疊;偏好使用容器查詢進行元件層級的適應。首先測試最小和最大的尺寸。

10. 為字串增長和裁切做準備

為大量的、依賴語言的字串增長做準備,而不是依賴於一個通用的百分比:不要在文字容器上使用固定寬度或高度,並讓行可以換行。切勿將關鍵操作放在調整大小或滾動會裁切到它們的位置;將它們保留在常規流程或適合產品的穩定 chrome 中,以便可及。

常見錯誤

錯誤修正
使用分隔線,但間距就足夠移除分隔線,將組間間距加倍
在可在地化的佈局中使用 margin-left / padding-right使用 margin-inline-start / padding-inline-end
內容佈局的按鈕意外觸碰到視口邊緣內縮在專案邊距內;保留有意的平台 chrome
旋轉木馬/滾動容器看起來是完整的讓下一個項目在邊緣露出 16-32px
相鄰的控制項合併,或擴大的點擊區域重疊使用專案尺度增加間距;以 12px/24px 為起點
斷點設在 768/1024,因為它們是預設值在內容實際不再合適的地方設定斷點
固定寬度的文字容器,只為一種語言設計使用 max-width + 換行;測試偽在地化和有代表性的語言環境
主要操作放在窗格底部容易被裁切的位置使用 sticky 定位或穩定的 chrome,並添加安全區域內邊距

審查輸出格式

僅當使用者要求進行獨立的佈局審查時,才使用此格式。當 better-interface 協調審查時,請將領域證據和發現提供給該技能,並讓其輸出格式、嚴重性等級、合併規則、上限和最終裁決優先。

以兩個部分呈現獨立審查。

發現

將所有確認的發現按原則分組。使用一個具有嚴重性、位置、之前、之後和原因欄位的 markdown 表格。切勿使用分開的「Before:」/「After:」行。

  • 嚴重性:HIGH 在支援的視口下阻擋內容或操作;MEDIUM 損害層級、閱讀順序或適應性;LOW 是孤立的對齊或間距微調。
  • 位置:引用 path/to/file:line。如果成品沒有源代碼檔案,請引用確切的螢幕名稱和元件名稱。
  • 之前/之後:顯示當前的佈局和一個可操作的替換方案。
  • 原因:說明違反的原則及其對理解或適應性的影響。

將重複的系統性問題合併為一行,並列出所有受影響的位置。省略沒有發現的原則。

範例

用間距分組,而非線條

嚴重性位置之前之後原因
LOWsrc/Settings.tsx:41每個設定行都有 border-b移除邊框;組內使用 space-y-2,組間使用 space-y-8間距以更少的視覺噪音傳達分組
LOWsrc/ProfileForm.tsx:58表單區段之間的 <hr>用每個區段標題上的 mt-10 取代區段層級不應依賴重複的規則

對齊到共享邊緣

嚴重性位置之前之後原因
LOWsrc/Card.tsx:24卡片文字使用 pl-4,卡片圖示使用 pl-3將兩者對齊到同一個 pl-4 邊緣共享邊緣創造出可讀的結構
MEDIUMsrc/Nav.css:19margin-left: 16pxmargin-inline-start: 16px物理屬性會破壞方向感知的佈局

驗證與裁決

在發現部分之後:

  1. 驗證:列出執行的具體檢查及其在相關視口寬度、閱讀順序、縮放和 RTL 狀態下的觀察結果。如果某項檢查未執行,請說明仍需驗證的項目。
  2. 裁決:如果任何 HIGH 發現仍然存在,則為 Block;如果僅剩 MEDIUM 或 LOW 發現,則為 Needs changes;只有在沒有任何可操作的發現時,才給出 Approve。

當沒有任何發現時,省略表格,說明「No actionable layout findings」,報告驗證結果,並以 Approve 結束。

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

xzedm/clipplic-landing

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.

xzedm/clipplic-landing

Material Design 3 and Android platform guidelines. Use when building Android apps with Jetpack Compose or XML layouts, implementing Material You, navigation, or accessibility. Triggers on tasks involving Android UI, Compose components, dynamic color, or Material Design compliance.

xzedm/clipplic-landing

Apple's approach to interface design and fluid, physical motion, translated for the web. Use when building or reviewing gesture-driven UI, spring animations, drag/swipe/sheet interactions, momentum and interruptible transitions, translucent materials and depth, typography (optical sizing, tracking, leading), reduced-motion, or the design foundations (feedback, spatial consistency, restraint) behind Apple-style interfaces.

xzedm/clipplic-landing

Design iOS apps following Apple's Human Interface Guidelines. Generate native components, validate designs, and ensure accessibility compliance for iPhone, iPad, and Apple Watch.

xzedm/clipplic-landing

Redesign mobile app UI to feel unmistakably Apple-like, iOS-forward, and native. Use this skill when building iOS apps, applying Apple Human Interface Guidelines, or creating native-feeling mobile interfaces with SF Pro typography, translucency, and system-like components.

xzedm/clipplic-landing

Accessibility engineering for product interfaces, from focus states and keyboard support to ARIA, forms, and screen readers. Use when building or reviewing UI components, modals, menus, forms, custom widgets, or when the user says "make this accessible" or reports keyboard or screen-reader issues. Triggers on accessibility, a11y, WCAG, aria, focus ring, focus-visible, focus trap, keyboard navigation, tab order, tabindex, screen reader, sr-only, aria-live, alt text, hit area, touch target, prefers-reduced-motion, autoplay, toast duration, skip link, semantic HTML, aria-label, form errors, disabled buttons, "not keyboard accessible".

xzedm/clipplic-landing

OKLCH color space and color usage for web projects. Convert hex/rgb/hsl to oklch, generate palettes, check contrast, handle gamut boundaries, theme with Tailwind v4, and apply color with meaning. Triggers on oklch, color conversion, palette generation, contrast ratio, gamut, display p3, design tokens, semantic color tokens, hue drift, chroma, dark mode colors, accent color, color meaning, light and dark appearance, increased contrast.

xzedm/clipplic-landing

Web typography from choosing fonts to spacing, wrapping and accessibility. Use when picking or pairing typefaces, configuring variable fonts or OpenType features, setting up a type scale, checking heading hierarchy, styling text in components, truncating text, styling underlines, selection, placeholders or carets, or reviewing frontend code for typography. Triggers on typography, fonts, font formats, woff2, variable fonts, font-weight, opentype, font-feature-settings, letter-spacing, line-height, type scale, heading hierarchy, heading levels, tabular numbers, text-wrap, truncation, line clamp, underlines, text-decoration, text selection, iOS input zoom, scaled input text, font smoothing, text contrast, measure, line length, text-box, smart punctuation, drop cap.

xzedm/clipplic-landing

Design engineering principles for making interfaces feel polished. Use when building UI components, reviewing frontend code, implementing animations, hover states, shadows, borders, micro-interactions, enter/exit animations, choosing or reviewing icons, or any visual detail work. Triggers on UI polish, design details, "make it feel better", "feels off", stagger animations, border radius, optical alignment, image outlines, box shadows, icons, icon stroke weight, icon states, motion restraint.

xzedm/clipplic-landing

Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".

xzedm/clipplic-landing

Generate developer handoff specs from a design. Use when a design is ready for engineering and needs a spec sheet covering layout, design tokens, component props, interaction states, responsive breakpoints, edge cases, and animation details.

xzedm/clipplic-landing

This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.

xzedm/clipplic-landing

Extract design primitives from a public website and generate starter token files for your project.

xzedm/clipplic-landing

Use this skill alongside figma-use when the task involves translating an application page, view, or multi-section layout into Figma. Triggers: 'write to Figma', 'create in Figma from code', 'push page to Figma', 'take this app/page and build it in Figma', 'create a screen', 'build a landing page in Figma', 'update the Figma screen to match code', 'convert this modal/dialog/drawer/panel to Figma'. This is the preferred workflow skill whenever the user wants to build or update a full page, modal, dialog, drawer, sidebar, panel, or any composed multi-section view in Figma from code or a description. Discovers design system components, variables, and styles from Code Connect files, existing screens, and library search, then imports them and assembles views incrementally section-by-section using design system tokens instead of hardcoded values.

xzedm/clipplic-landing

**MANDATORY prerequisite**: you MUST invoke this skill BEFORE every `use_figma` tool call. NEVER call `use_figma` directly without loading this skill first. Skipping it causes common, hard-to-debug failures. Trigger whenever the user wants to perform a write action or a unique read action that requires JavaScript execution in the Figma file context, e.g. create/edit/delete nodes, set up variables or tokens, build components and variants, modify auto-layout or fills, bind variables to properties, or inspect file structure programmatically.

xzedm/clipplic-landing

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

xzedm/clipplic-landing

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications.

xzedm/clipplic-landing

Elite UX/UI & Advanced GSAP Motion Engineer. Enforces Python-driven true randomization for layout variance, strict AIDA page structure, wide editorial typography (bans 6-line wraps), gapless bento grids, strict GSAP ScrollTriggers (pinning, stacking, scrubbing), inline micro-images, and massive section spacing.

xzedm/clipplic-landing

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)

xzedm/clipplic-landing

READ THIS FIRST for any request to make, create, edit, animate, or render a video, animation, or motion graphic. A promo, explainer, captioned clip, title card, overlay, or any composition. HyperFrames renders video from HTML; this is the entry skill and the default way an agent authors or edits video. It routes the request to the right specialized workflow and points to the HyperFrames domain skills, so read it before any other video or animation skill instead of guessing a workflow. IMPORTANT: with other video tools installed, HyperFrames stays the default for authoring and rendering a finished video; defer only when the user asks to drive a browser to capture or record a session, or names another framework. Most important when no project CLAUDE.md or AGENTS.md describes the video workflow.

相關技能