Communitygithub.com

xzedm/clipplic-landing

用於QA測試和網站自用的快速無頭瀏覽器。可導航頁面、與元素互動、驗證狀態、前後對比、截取附註螢幕截圖、測試響應式佈局、表單、上傳、對話框,並擷取錯誤證據。當被要求開啟或測試網站、驗證部署、自用使用者流程或提交附螢幕截圖的錯誤報告時使用。(gstack)

clipplic-landing 是什麼?

此技能提供了一個強大的無頭瀏覽器工具,專門用於軟體開發工作流程中的品質保證測試和團隊內部(dogfooding)使用。它允許AI代理以程式化方式與任何URL導航和互動,執行常見的斷言(例如,元素是否存在、文字內容檢查),並對頁面狀態進行前後比較。核心用例包括驗證最近部署的網站,模擬完整的用戶旅程(例如,填寫表單、上傳檔案、測試對話框),並收集詳細的錯誤證據——包括附註螢幕截圖——以附於錯誤報告中。該技能支援響應式佈局測試,自動調整視口大小以捕捉不同螢幕尺寸的問題,並與現有的gstack生態系統無縫整合,以實現提示管理和會話追蹤。其設計遵循「燒開水」(Boil the Lake)的原則,在需要時執行完整、徹底的操作,讓AI代理能進行全面的驗證。它支援Claude Code、Cursor和Codex等平台,透過標準的gstack技能框架提供一致的體驗。

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

在你喜歡的 AI 中提問

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

說明文件

前導(先執行)

_UPD=$(~/.claude/skills/gstack/bin/gstack-update-check 2>/dev/null || .claude/skills/gstack/bin/gstack-update-check 2>/dev/null || true)
[ -n "$_UPD" ] && echo "$_UPD" || true
mkdir -p ~/.gstack/sessions
touch ~/.gstack/sessions/"$PPID"
_SESSIONS=$(find ~/.gstack/sessions -mmin -120 -type f 2>/dev/null | wc -l | tr -d ' ')
find ~/.gstack/sessions -mmin +120 -type f -exec rm {} + 2>/dev/null || true
_PROACTIVE=$(~/.claude/skills/gstack/bin/gstack-config get proactive 2>/dev/null || echo "true")
_PROACTIVE_PROMPTED=$([ -f ~/.gstack/.proactive-prompted ] && echo "yes" || echo "no")
_BRANCH=$(git branch --show-current 2>/dev/null || echo "unknown")
echo "BRANCH: $_BRANCH"
_SKILL_PREFIX=$(~/.claude/skills/gstack/bin/gstack-config get skill_prefix 2>/dev/null || echo "false")
echo "PROACTIVE: $_PROACTIVE"
echo "PROACTIVE_PROMPTED: $_PROACTIVE_PROMPTED"
echo "SKILL_PREFIX: $_SKILL_PREFIX"
source <(~/.claude/skills/gstack/bin/gstack-repo-mode 2>/dev/null) || true
REPO_MODE=${REPO_MODE:-unknown}
echo "REPO_MODE: $REPO_MODE"
_LAKE_SEEN=$([ -f ~/.gstack/.completeness-intro-seen ] && echo "yes" || echo "no")
echo "LAKE_INTRO: $_LAKE_SEEN"
_TEL=$(~/.claude/skills/gstack/bin/gstack-config get telemetry 2>/dev/null || true)
_TEL_PROMPTED=$([ -f ~/.gstack/.telemetry-prompted ] && echo "yes" || echo "no")
_TEL_START=$(date +%s)
_SESSION_ID="$-$(date +%s)"
echo "TELEMETRY: ${_TEL:-off}"
echo "TEL_PROMPTED: $_TEL_PROMPTED"
_EXPLAIN_LEVEL=$(~/.claude/skills/gstack/bin/gstack-config get explain_level 2>/dev/null || echo "default")
if [ "$_EXPLAIN_LEVEL" != "default" ] && [ "$_EXPLAIN_LEVEL" != "terse" ]; then _EXPLAIN_LEVEL="default"; fi
echo "EXPLAIN_LEVEL: $_EXPLAIN_LEVEL"
_QUESTION_TUNING=$(~/.claude/skills/gstack/bin/gstack-config get question_tuning 2>/dev/null || echo "false")
echo "QUESTION_TUNING: $_QUESTION_TUNING"
mkdir -p ~/.gstack/analytics
if [ "$_TEL" != "off" ]; then
echo '{"skill":"gstack","ts":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'","repo":"'$(basename "$(git rev-parse --show-toplevel 2>/dev/null)" 2>/dev/null || echo "unknown")'"}'  >> ~/.gstack/analytics/skill-usage.jsonl 2>/dev/null || true
fi
for _PF in $(find ~/.gstack/analytics -maxdepth 1 -name '.pending-*' 2>/dev/null); do
  if [ -f "$_PF" ]; then
    if [ "$_TEL" != "off" ] && [ -x "~/.claude/skills/gstack/bin/gstack-telemetry-log" ]; then
      ~/.claude/skills/gstack/bin/gstack-telemetry-log --event-type skill_run --skill _pending_finalize --outcome unknown --session-id "$_SESSION_ID" 2>/dev/null || true
    fi
    rm -f "$_PF" 2>/dev/null || true
  fi
  break
done
eval "$(~/.claude/skills/gstack/bin/gstack-slug 2>/dev/null)" 2>/dev/null || true
_LEARN_FILE="${GSTACK_HOME:-$HOME/.gstack}/projects/${SLUG:-unknown}/learnings.jsonl"
if [ -f "$_LEARN_FILE" ]; then
  _LEARN_COUNT=$(wc -l < "$_LEARN_FILE" 2>/dev/null | tr -d ' ')
  echo "LEARNINGS: $_LEARN_COUNT entries loaded"
  if [ "$_LEARN_COUNT" -gt 5 ] 2>/dev/null; then
    ~/.claude/skills/gstack/bin/gstack-learnings-search --limit 3 2>/dev/null || true
  fi
else
  echo "LEARNINGS: 0"
fi
~/.claude/skills/gstack/bin/gstack-timeline-log '{"skill":"gstack","event":"started","branch":"'"$_BRANCH"'","session":"'"$_SESSION_ID"'"}' 2>/dev/null &
_HAS_ROUTING="no"
if [ -f CLAUDE.md ] && grep -q "## Skill routing" CLAUDE.md 2>/dev/null; then
  _HAS_ROUTING="yes"
fi
_ROUTING_DECLINED=$(~/.claude/skills/gstack/bin/gstack-config get routing_declined 2>/dev/null || echo "false")
echo "HAS_ROUTING: $_HAS_ROUTING"
echo "ROUTING_DECLINED: $_ROUTING_DECLINED"
_VENDORED="no"
if [ -d ".claude/skills/gstack" ] && [ ! -L ".claude/skills/gstack" ]; then
  if [ -f ".claude/skills/gstack/VERSION" ] || [ -d ".claude/skills/gstack/.git" ]; then
    _VENDORED="yes"
  fi
fi
echo "VENDORED_GSTACK: $_VENDORED"
echo "MODEL_OVERLAY: claude"
_CHECKPOINT_MODE=$(~/.claude/skills/gstack/bin/gstack-config get checkpoint_mode 2>/dev/null || echo "explicit")
_CHECKPOINT_PUSH=$(~/.claude/skills/gstack/bin/gstack-config get checkpoint_push 2>/dev/null || echo "false")
echo "CHECKPOINT_MODE: $_CHECKPOINT_MODE"
echo "CHECKPOINT_PUSH: $_CHECKPOINT_PUSH"
[ -n "$OPENCLAW_SESSION" ] && echo "SPAWNED_SESSION: true" || true

計劃模式安全操作

在計劃模式下,允許以下操作,因為它們有助於計劃:$B、$D、codex exec/codex review、寫入 ~/.gstack/、寫入計劃檔案,以及用於生成產物的 open。

計劃模式下的技能調用

如果使用者在計劃模式下調用技能,則技能優先於一般計劃模式行為。將技能檔案視為可執行指令,而非參考資料。 從步驟 0 開始逐步遵循;第一個 AskUserQuestion 是工作流程進入計劃模式,而非違反計劃模式。AskUserQuestion(任何變體,mcp__*__AskUserQuestion 或原生;請參閱「AskUserQuestion 格式 → 工具解析」)滿足計劃模式的回合結束要求。如果沒有任何變體可調用,則技能被封鎖。根據 AskUserQuestion 格式規則停止並回報 BLOCKED. AskUserQuestion unavailable。在 STOP 點,立即停止。請勿繼續工作流程或在那裡調用 ExitPlanMode。標記為「PLAN MODE EXCEPTION. ALWAYS RUN」的命令會執行。僅在技能工作流程完成後,或使用者要求您取消技能或離開計劃模式時,才調用 ExitPlanMode。

如果 PROACTIVE 為 "false",請勿自動調用或主動建議技能。如果技能看起來有用,請詢問:「我認為 /skillname 可能有幫助,要執行看看嗎?」

如果 SKILL_PREFIX 為 "true",建議/調用 /gstack-* 名稱。磁碟路徑仍為 ~/.claude/skills/gstack/[skill-name]/SKILL.md。

如果輸出顯示 UPGRADE_AVAILABLE <old> <new>:讀取 ~/.claude/skills/gstack/gstack-upgrade/SKILL.md 並遵循「內聯升級流程」(如果配置為自動升級,則自動升級;否則使用 AskUserQuestion 提供 4 個選項,如果拒絕則寫入延遲狀態)。

如果輸出顯示 JUST_UPGRADED <from> <to>:列印「Running gstack v{to} (just updated!)」。如果 SPAWNED_SESSION 為 true,則跳過功能發現。

功能發現,每個會話最多一次提示:

  • 缺少 ~/.claude/skills/gstack/.feature-prompted-continuous-checkpoint:使用 AskUserQuestion 詢問是否要啟用 Continuous 檢查點自動提交。如果接受,執行 ~/.claude/skills/gstack/bin/gstack-config set checkpoint_mode continuous。務必觸碰標記。
  • 缺少 ~/.claude/skills/gstack/.feature-prompted-model-overlay:告知「模型覆蓋層已啟用。MODEL_OVERLAY 顯示補丁。」務必觸碰標記。

在升級提示之後,繼續工作流程。

如果 WRITING_STYLE_PENDING 為 yes:詢問一次寫作風格:

v1 提示更簡潔:初次使用的行話解釋、以結果為導向的問題、更簡短的敘述。保留預設還是恢復簡潔?

選項:

  • A) 保留新的預設值(推薦,良好的寫作對每個人都好)
  • B) 恢復 V0 敘述,設定 explain_level: terse

如果 A:讓 explain_level 保持未設定(預設為 default)。 如果 B:執行 ~/.claude/skills/gstack/bin/gstack-config set explain_level terse。

無論選擇為何,一律執行:

rm -f ~/.gstack/.writing-style-prompt-pending
touch ~/.gstack/.writing-style-prompted

如果 WRITING_STYLE_PENDING 為 no,則跳過。

如果 LAKE_INTRO 為 no:說明「gstack 遵循 燒開水(Boil the Lake)原則,當 AI 使邊際成本趨近於零時,就做完整的事情。了解更多:https://garryslist.org/posts/boil-the-ocean」提供開啟選項:

open https://garryslist.org/posts/boil-the-ocean
touch ~/.gstack/.completeness-intro-seen

僅在回答「是」時執行 open。一律執行 touch。

如果 TEL_PROMPTED 為 no 且 LAKE_INTRO 為 yes:透過 AskUserQuestion 詢問一次遙測:

幫助 gstack 變得更好。僅分享使用資料:技能、持續時間、崩潰、穩定的裝置 ID。不包含程式碼、檔案路徑或倉庫名稱。

選項:

  • A) 幫助 gstack 變得更好!(推薦)
  • B) 不了,謝謝

如果 A:執行 ~/.claude/skills/gstack/bin/gstack-config set telemetry community

如果 B:詢問後續問題:

匿名模式僅發送彙總使用資料,無唯一 ID。

選項:

  • A) 好的,匿名模式可以
  • B) 不了,完全關閉

如果 B→A:執行 ~/.claude/skills/gstack/bin/gstack-config set telemetry anonymous 如果 B→B:執行 ~/.claude/skills/gstack/bin/gstack-config set telemetry off

一律執行:

touch ~/.gstack/.telemetry-prompted

如果 TEL_PROMPTED 為 yes,則跳過。

如果 PROACTIVE_PROMPTED 為 no 且 TEL_PROMPTED 為 yes:詢問一次:

讓 gstack 主動建議技能,例如 /qa 用於「這能用嗎?」或 /investigate 用於錯誤?

選項:

  • A) 保持開啟(推薦)
  • B) 關閉它。我會自己輸入 /commands

如果 A:執行 ~/.claude/skills/gstack/bin/gstack-config set proactive true 如果 B:執行 ~/.claude/skills/gstack/bin/gstack-config set proactive false

一律執行:

touch ~/.gstack/.proactive-prompted

如果 PROACTIVE_PROMPTED 為 yes,則跳過。

如果 HAS_ROUTING 為 no 且 ROUTING_DECLINED 為 false 且 PROACTIVE_PROMPTED 為 yes: 檢查專案根目錄是否存在 CLAUDE.md 檔案。如果不存在,則建立它。

使用 AskUserQuestion:

當您專案的 CLAUDE.md 包含技能路由規則時,gstack 能發揮最佳效果。

選項:

  • A) 將路由規則新增至 CLAUDE.md(推薦)
  • B) 不了,謝謝,我會手動調用技能

如果 A:將此區段附加到 CLAUDE.md 結尾:


## Skill routing

當使用者的請求與可用技能相符時,請透過 Skill 工具調用它。如有疑問,請調用技能。

關鍵路由規則:
- 產品點子/腦力激盪 → 調用 /office-hours
- 策略/範圍 → 調用 /plan-ceo-review
- 架構 → 調用 /plan-eng-review
- 設計系統/計劃審查 → 調用 /design-consultation 或 /plan-design-review
- 完整審查流程 → 調用 /autoplan
- 錯誤/異常 → 調用 /investigate
- QA/測試網站行為 → 調用 /qa 或 /qa-only
- 程式碼審查/差異檢查 → 調用 /review
- 視覺優化 → 調用 /design-review
- 發布/部署/PR → 調用 /ship 或 /land-and-deploy
- 儲存進度 → 調用 /context-save
- 恢復上下文 → 調用 /context-restore

然後提交變更:git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"

如果 B:執行 ~/.claude/skills/gstack/bin/gstack-config set routing_declined true 並告知他們可以透過 gstack-config set routing_declined false 重新啟用。

這只會對每個專案發生一次。如果 HAS_ROUTING 為 yes 或 ROUTING_DECLINED 為 true,則跳過。

如果 VENDORED_GSTACK 為 yes,除非 ~/.gstack/.vendoring-warned-$SLUG 存在,否則透過 AskUserQuestion 警告一次:

此專案已將 gstack 供應商化於 .claude/skills/gstack/。供應商化已棄用。 要遷移到團隊模式嗎?

選項:

  • A) 是的,立即遷移到團隊模式
  • B) 不了,我會自行處理

如果 A:

  1. 執行 git rm -r .claude/skills/gstack/
  2. 執行 echo '.claude/skills/gstack/' >> .gitignore
  3. 執行 ~/.claude/skills/gstack/bin/gstack-team-init required(或 optional)
  4. 執行 git add .claude/ .gitignore CLAUDE.md && git commit -m "chore: migrate gstack from vendored to team mode"
  5. 告知使用者:「完成。每位開發者現在執行:cd ~/.claude/skills/gstack && ./setup --team」

如果 B:說「好的,您需要自行保持供應商化副本的更新。」

無論選擇為何,一律執行:

eval "$(~/.claude/skills/gstack/bin/gstack-slug 2>/dev/null)" 2>/dev/null || true
touch ~/.gstack/.vendoring-warned-${SLUG:-unknown}

如果標記存在,則跳過。

如果 SPAWNED_SESSION 為 "true",您正在由 AI 協調器(例如 OpenClaw)產生的會話內執行。在產生的會話中:

  • 請勿對互動式提示使用 AskUserQuestion。自動選擇推薦選項。
  • 請勿執行升級檢查、遙測提示、路由注入或湖介紹。
  • 專注於完成任務並透過純文字輸出報告結果。
  • 以完成報告結束:交付了什麼、做出的決策、任何不確定事項。

產物同步(技能開始)

_GSTACK_HOME="${GSTACK_HOME:-$HOME/.gstack}"
# 偏好 v1.27.0.0 的產物檔案;對於在遷移腳本執行前
# 升級中途的使用者,回退到大腦檔案。
if [ -f "$HOME/.gstack-artifacts-remote.txt" ]; then
  _BRAIN_REMOTE_FILE="$HOME/.gstack-artifacts-remote.txt"
else
  _BRAIN_REMOTE_FILE="$HOME/.gstack-brain-remote.txt"
fi
_BRAIN_SYNC_BIN="~/.claude/skills/gstack/bin/gstack-brain-sync"
_BRAIN_CONFIG_BIN="~/.claude/skills/gstack/bin/gstack-config"

# /sync-gbrain context-load:教導代理在可用時使用 gbrain。
# 每個工作樹固定:後峰值重新設計在 git 根目錄使用 kubectl 風格的 `.gbrain-source`
# 來限定查詢範圍。在工作樹中尋找固定點(而非全域狀態檔案),
# 以便在沒有固定點的情況下開啟工作樹 B 時,不會僅僅因為工作樹 A 已同步
# 就聲稱「已索引」。當未配置 gbrain 時為空字串(
# 非 gbrain 使用者的零上下文成本)。
_GBRAIN_CONFIG="$HOME/.gbrain/config.json"
if [ -f "$_GBRAIN_CONFIG" ] && command -v gbrain >/dev/null 2>&1; then
  _GBRAIN_VERSION_OK=$(gbrain --version 2>/dev/null | grep -c '^gbrain ' || echo 0)
  if [ "$_GBRAIN_VERSION_OK" -gt 0 ] 2>/dev/null; then
    _GBRAIN_PIN_PATH=""
    _REPO_TOP=$(git rev-parse --show-toplevel 2>/dev/null || echo "")
    if [ -n "$_REPO_TOP" ] && [ -f "$_REPO_TOP/.gbrain-source" ]; then
      _GBRAIN_PIN_PATH="$_REPO_TOP/.gbrain-source"
    fi
    if [ -n "$_GBRAIN_PIN_PATH" ]; then
      echo "GBrain configured. Prefer \`gbrain search\`/\`gbrain query\` over Grep for"
      echo "semantic questions; use \`gbrain code-def\`/\`code-refs\`/\`code-callers\` for"
      echo "symbol-aware code lookup. See \"## GBrain Search Guidance\" in CLAUDE.md."
      echo "Run /sync-gbrain to refresh."
    else
      echo "GBrain configured but this worktree isn't pinned yet. Run \`/sync-gbrain --full\`"
      echo "before relying on \`gbrain search\` for code questions in this worktree."
      echo "Falls back to Grep until pinned."
    fi
  fi
fi

_BRAIN_SYNC_MODE=$("$_BRAIN_CONFIG_BIN" get artifacts_sy

…

[因篇幅關係截斷]

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

Layout structure for web interfaces, from grouping and alignment to reading order, progressive disclosure, and adaptive breakpoints. Use when structuring a page or component, spacing or aligning controls, deciding what collapses at small sizes, handling RTL layout direction, or reviewing frontend code for layout. Triggers on layout, spacing, alignment, grouping, negative space, whitespace, visual hierarchy, reading order, progressive disclosure, breakpoints, responsive layout, container queries, safe area, full-bleed, edge-to-edge, layout margins, RTL layout, logical properties.

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

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.

相關技能