Communitygithub.com

bg-szy/TOP-SKILLS

工作區感知的唯讀版本佇列儀表板。顯示哪些 VERSION 槽已被開啟的 PR 佔用、哪些同體系的 Conductor 工作區有即將發佈的 WIP 工作,以及下一個 /ship 會選取哪個槽。不進行任何修改——僅提供快照。當被要求「landing report」、「queue 中有什麼」、「顯示開啟的 PR」或「我該 claim 哪個版本」時使用。(gstack)

TOP-SKILLS 是什麼?

此技能提供一個唯讀的版本佇列儀表板,讓開發者與 AI Agent 能夠快速掌握當前專案的版本槽分配狀態。它會顯示哪些 VERSION 槽已被開啟的 Pull Request 佔用、哪些同體系(Conductor)的工作區有正在進行中的工作且可能即將發佈,以及下一個 /ship 指令會選取哪個槽位。技能設計為工作區感知(workspace-aware),會自動讀取當前分支、工作階段資訊與專案設定,並在執行前先執行更新檢查與環境初始化腳本。支援 Claude Code、Cursor、Codex 等平台,並提供 proactive 技能建議與計畫模式安全操作。除了核心佇列查詢外,它還內建了多項提示流程,包括寫作風格偏好、遙測設定、proactive 行為開關、技能路由設定、專案模式遷移,以及 Boil the Lake 原則介紹。這些流程會在使用者首次呼叫時以結構化的 AskUserQuestion 方式引導設定。

相容平台✓Claude Code✓Codex CLI~Cursor
npx skills add https://github.com/bg-szy/TOP-SKILLS/tree/HEAD/skills/superskills/landing-report

在你喜歡的 AI 中提問

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

說明文件

/landing-report — 版本佇列儀表板

前置腳本(優先執行)

_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":"landing-report","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":"landing-report","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 滿足計畫模式回合結束的要求。遇到 STOP 點時,立即停止。請勿繼續工作流程或在那裡呼叫 ExitPlanMode。標記為「PLAN MODE EXCEPTION — ALWAYS RUN」的指令會被執行。僅在技能工作流程完成後,或使用者要求您取消技能或離開計畫模式時,才呼叫 ExitPlanMode。

如果 PROACTIVE 為 "false",請勿自動調用或主動推薦技能。如果某技能似乎有用,請詢問:「我認為 /skillname 可能對此有幫助——要執行它嗎?」

如果 SKILL_PREFIX 為 "true",請推薦/調用 /gstack-* 名稱。磁碟路徑仍保持為 ~/.claude/skills/gstack/[技能名稱]/SKILL.md。

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

如果輸出顯示 JUST_UPGRADED <from> <to>:列印「正在執行 gstack v{to}(剛剛更新!)」。如果 SPAWNED_SESSION 為 true,則跳過功能探索。

功能探索,每個工作階段最多一個提示:

  • 缺少 ~/.claude/skills/gstack/.feature-prompted-continuous-checkpoint:針對持續檢查點自動提交使用 AskUserQuestion。如果接受,執行 ~/.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
- 程式碼審查/diff 檢查 → 調用 /review
- 視覺修飾 → 調用 /design-review
- Ship/部署/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,透過 AskUserQuestion 警告一次,除非 ~/.gstack/.vendoring-warned-$SLUG 已存在:

此專案在 .claude/skills/gstack/ 中包含了 gstack 的 vendored 副本。Vendoring 已棄用。 遷移到團隊模式?

選項:

  • 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:說「好的,你需要自行保持 vendored 副本為最新狀態。」

始終執行(無論選擇為何):

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。自動選擇建議選項。
  • 請勿執行升級檢查、遙測提示、路由注入或 lake 介紹。
  • 專注於完成任務並透過文字輸出報告結果。
  • 以完成報告結尾:已發佈的內容、所做的決定、任何不確定的事項。

AskUserQuestion 格式

每個 AskUserQuestion 都是一個決策簡報,必須以 tool_use 發送,而非文字。

D<N> — <一行問題標題>
Project/branch/task: <使用 _BRANCH 的 1 個簡短背景說明句子>
ELI10: <一個 16 歲青少年能理解的簡單英文,2-4 個句子,說明利害關係>
Stakes if we pick wrong: <一句話說明會出什麼問題、使用者會看到什麼、會失去什麼>
Recommendation: <選擇> 因為 <一行理由>
Completeness: A=X/10, B=Y/10   (或:Note: options differ in kind, not coverage — no completeness score)
Pros / cons:
A) <選項標籤>(建議)
  ✅ <優點 — 具體、可觀察、≥40 字元>
  ❌ <缺點 — 誠實、≥40 字元>
B) <選項標籤>
  ✅ <優點>
  ❌ <缺點>
Net: <一行你實際上在權衡取捨的綜合說明>

D 編號:技能調用中的第一個問題是 D1;自行遞增。這是模型層級的指令,而非執行計數器。

ELI10 始終存在,使用簡單英文,而非函數名稱。Recommendation 始終存在。保留 (recommended) 標籤;AUTO_DECIDE 依賴於它。

Completeness:僅在選項的覆蓋範圍不同時使用 Completeness: N/10。10 = 完整,7 = 快樂路徑,3 = 捷徑。如果選項種類不同,請寫:Note: options differ in kind, not coverage — no completeness score.

Pros / cons:使用 ✅ 和 ❌。當選擇是真實的時,每個選項至少 2 個優點和 1 個缺點;每個要點至少 40 個字元。單向/破壞性確認的強制停止轉義:✅ No cons — this is a hard-stop choice。

中立姿態:Recommendation: <default> — this is a taste call, no strong preference either way;(recommended) 仍然保留在預設選項上以供 AUTO_DECIDE。

Effort both-scales:當選項涉及工作量時,標記人力團隊和 CC+gstack 時間,例如 (human: ~2 days / CC: ~15 min)。這使得 AI 壓縮在決策時可見。

Net 行總結了權衡取捨。每個技能的說明可能會增加更嚴格的規則。

發送前的自我檢查

在呼叫 AskUserQuestion 之前,請驗證:

  • D 標題存在
  • ELI10 段落存在(利害關係行也存在)
  • Recommendation 行存在,並附有具體理由
  • Completeness 已評分(覆蓋範圍)或種類說明存在(種類)
  • 每個選項都有 ≥2 個 ✅ 和 ≥1 個 ❌,每個 ≥40 個字元(或強制停止轉義)
  • [

…

[為翻譯而截斷]

Individual skills in this repo

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

bg-szy/TOP-SKILLS

Brand-first landing page designer — runs a brand-identity interview (colors, typography, shape language), then generates and iterates on a polished landing page via Stitch with deployment-ready HTML. Use when the user asks to create, design, or build a landing page, homepage, or marketing page and has no established visual direction. Skip when they have a design mockup, need a dashboard or app UI, are working at component level, building a multi-page app, or restyling with known design tokens — use frontend-design instead.

bg-szy/TOP-SKILLS

Fill out Microsoft Azure Landing Zone (ALZ) Accelerator checklists by interviewing the user, mapping their Azure subscriptions, integrating IP addressing documentation, and applying Microsoft Cloud Adoption Framework best practices. Produces a completed Excel checklist (.xlsx) ready for ALZ deployment. Use this skill whenever the user mentions Azure Landing Zone, ALZ checklist, landing zone accelerator, platform landing zone configuration, ALZ bootstrap, hub-and-spoke setup, Azure network topology planning, or wants to fill out any ALZ-related checklist or configuration file. Also trigger when the user uploads an Excel file that contains tabs like "Accelerator - Bootstrap", "Accelerator - Bicep", or "Accelerator - Terraform".

bg-szy/TOP-SKILLS

Compose a premium, animated landing page section by section in Next.js + Tailwind + Motion (Framer Motion) — built on a real design system, with editorial copy and motion that feels human-crafted, not template-generated. Use when building or rebuilding a landing page, marketing site, or hero/feature/pricing/CTA sections that need to look production-ready and bespoke from day one.

bg-szy/TOP-SKILLS

Write high-converting landing page copy using proven frameworks like PAS (Problem-Agitate-Solution), AIDA, and StoryBrand. Creates headlines, value propositions, CTAs, and full page sections optimized for conversion. Use when users need landing page copy, sales page content, or marketing website text.

bg-szy/TOP-SKILLS

Optimize landing pages for conversions, performance, and SEO. Use when improving landing pages, increasing conversions, or optimizing page performance.

bg-szy/TOP-SKILLS

Review investment portfolios for risk, diversification, fees. Asset allocation recommendations, tax-loss harvesting, rebalancing.

bg-szy/TOP-SKILLS

Beads Viewer - Graph-aware triage engine for Beads projects. Computes PageRank, betweenness, critical path, and cycles. Use --robot-* flags for AI agents.

bg-szy/TOP-SKILLS

CI red? Call us. Pipeline fire brigade deploys. Use when user mentions CI failures, build errors, test failures, or pipeline issues. Do NOT load for: local builds, standard implementation work, reviews, or setup.

bg-szy/TOP-SKILLS

CASS Memory System - procedural memory for AI coding agents. Three-layer cognitive architecture with confidence decay, anti-pattern learning, cross-agent knowledge transfer, trauma guard safety system. Bun/TypeScript CLI.

bg-szy/TOP-SKILLS

Mandatory entry point: read this first for any request to make, create, edit, animate, or render a video, animation, or motion graphic, including a promo, explainer, captioned clip, title card, overlay, slideshow or interactive deck, Remotion port, or any HyperFrames HTML composition. Also use it to inspect, diagnose, validate, preview, publish, or batch-render an existing HyperFrames project. Inputs may be a website URL, GitHub PR, Figma design or URL, text or brief, existing footage, or music. It resumes project state, captures intent when applicable, selects and installs the owning workflow, and routes domain capabilities. HyperFrames is the default output framework unless the user explicitly chooses another framework for the deliverable or asks only to record a browser session.

bg-szy/TOP-SKILLS

Expert in building portfolios that actually land jobs and clients - not just showing work, but creating memorable experiences. Covers developer portfolios, designer portfolios, creative portfolios, and portfolios that convert visitors into opportunities.

bg-szy/TOP-SKILLS

Use when the user asks to "pre-launch check the landing page", "run a Quality-Score preflight", or "verify ad-to-page message match before launch"; produces an ad↔page continuity report — message-match gaps, above-the-fold check, page-speed read, form-friction count, mobile-render flags — as a pass/fix punch list. Not for redesigning or rewriting the page — use landing-optimizer; not for scoring the account or the RQS — use ad-account-auditor. 落地页体验预检/广告落地页一致性检查

bg-szy/TOP-SKILLS

Use when the user asks to "optimize our landing page for influencer traffic", "fix our promo-code landing page", or "improve conversion from a creator campaign"; produces a message-match audit, page-structure and social-proof recommendations, a promo-code/CTA conversion plan, and an A/B test roadmap. Not for measuring campaign results after launch — use performance-analyzer.

bg-szy/TOP-SKILLS

Audit a landing page, sales page or checkout page for conversion leaks and return a fix list ordered by expected revenue impact. Use when asked to review, critique or improve a landing page, sales page, opt-in page, product page or checkout flow, when conversion rate is low, when paid traffic is not converting, or when someone asks "why isn't this page converting" or wants a CRO / landing page review.

bg-szy/TOP-SKILLS

Landing page conversion optimization with layout rules, hero section design, and CTA psychology. Covers above-the-fold formula, social proof placement, mobile design, and F-pattern reading. Use for: startup landing pages, product pages, SaaS marketing, conversion optimization. Triggers: landing page, hero section, above the fold, conversion optimization, landing page design, cta button, hero image, landing page layout, saas landing page, product page design, conversion rate, landing page best practices

bg-szy/TOP-SKILLS

Create high-converting, visually distinctive landing pages. Use when building marketing pages, product launches, SaaS homepages, or any single-page conversion-focused website. Guides section-by-section composition with anti-AI-slop principles.

bg-szy/TOP-SKILLS

Landing page conversion optimization with layout rules, hero section design, and CTA psychology. Covers above-the-fold formula, social proof placement, mobile design, and F-pattern reading. Use for: startup landing pages, product pages, SaaS marketing, conversion optimization. Triggers: landing page, hero section, above the fold, conversion optimization, landing page design, cta button, hero image, landing page layout, saas landing page, product page design, conversion rate, landing page best practices

bg-szy/TOP-SKILLS

Account assets, equity and fund positions, P&L, cash flow records, account statements, margin ratios, buy-power estimates, order management, and DCA recurring investments via Longbridge (most require Trade permission). Frameworks: portfolio diagnosis, rebalancing, asset allocation, risk analysis (VaR/CVaR), performance attribution, and tax-loss harvesting. Triggers: "持仓", "账户", "盈亏", "资产", "对账单", "下单", "买入", "卖出", "撤单", "定投", "组合诊断", "再平衡", "资产配置", "风险分析", "绩效归因", "税损收割", "持倉", "賬戶", "盈虧", "對賬單", "下單", "買入", "賣出", "組合診斷", "再平衡", "稅損收割", "positions", "portfolio", "P&L", "order", "buy", "sell", "DCA", "statement", "risk analysis", "rebalancing", "tax harvesting", "我的风险", "持仓风险", "风险敞口", "資產", "資產配置", "風險分析", "績效歸因", "撤單

bg-szy/TOP-SKILLS

Auto-loaded context for Portfolio Buddy 2 development. Use for ANY task involving: React 19 development, TypeScript, portfolio analysis features, metrics calculations, trading strategy comparison, or working with the Portfolio Buddy 2 codebase. Contains tech stack, known issues, and architectural constraints.

bg-szy/TOP-SKILLS

Process video files with audio extraction, format conversion (mp4, webm), and Whisper transcription. Use when user mentions video conversion, audio extraction, transcription, mp4, webm, ffmpeg, or whisper transcription.

相關技能