Communitygithub.com

bg-szy/TOP-SKILLS

只读的版本队列仪表盘,适用于工作区感知的代码提交。显示当前被开放 PR 占用的 VERSION 插槽、即将提交的并行工作区中的 WIP 工作,以及 /ship 下一个会选中的插槽。无修改操作,仅提供快照。当用户要求“发布报告”、“队列状态”、“显示开放 PR”或“我下一个该认领哪个版本”时使用。

TOP-SKILLS 是什么?

此技能提供一个只读的版本队列仪表盘,帮助开发者和AI助手快速了解工作区中版本插槽的占用情况。它通过执行一系列命令获取当前分支、会话、仓库模式、遥测设置等信息,并输出一个结构化的报告。该技能适用于Claude Code等AI编程助手,在用户询问队列状态、开放PR或版本认领时自动触发。其核心功能是展示哪些VERSION插槽已被开放PR占用,哪些并行工作区有即将完成的WIP工作,以及/ship命令下一个会选中的插槽。技能包含详尽的初始化流程,包括版本更新检查、会话管理、遥测记录和学习文件搜索,确保每次调用都能提供最新且上下文相关的信息。此外,它还能处理计划模式下的调用、功能发现(如连续检查点、模型覆盖)、写作风格提示、以及团队模式迁移等高级场景,通过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-name]/SKILL.md。

如果输出显示 UPGRADE_AVAILABLE <old> <new>:读取 ~/.claude/skills/gstack/gstack-upgrade/SKILL.md 并遵循“内联升级流程”(如果配置为自动升级则自动升级,否则通过 AskUserQuestion 提供 4 个选项,如果拒绝则写入休眠状态)。

如果输出显示 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:

gstack 在项目的 CLAUDE.md 包含技能路由规则时效果最佳。

选项:

  • A) 将路由规则添加到 CLAUDE.md(推荐)
  • B) 不了,谢谢,我会手动调用技能

如果 A:将以下部分附加到 CLAUDE.md 的末尾:


## 技能路由

当用户的请求匹配可用技能时,通过 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,通过 AskUserQuestion 警告一次,除非 ~/.gstack/.vendoring-warned-$SLUG 已存在:

此项目在 .claude/skills/gstack/ 中集成了 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 进行交互式提示。自动选择推荐的选项。
  • 请勿运行升级检查、遥测提示、路由注入或 lake 介绍。
  • 专注于完成任务并通过文本输出报告结果。
  • 以完成报告结束:发布了什么,做出的决定,任何不确定之处。

AskUserQuestion 格式

每个 AskUserQuestion 都是一个决策简报,必须作为 tool_use 发送,而不是文本。

D<N> — <一行问题标题>
项目/分支/任务:<使用 _BRANCH 的一行简短背景信息>
ELI10:<16 岁少年能理解的通俗英语,2-4 句话,说明利害关系>
选择错误的利害关系:<一句话说明哪里会出问题,用户会看到什么,失去什么>
建议:<选项> 因为 <一行理由>
完整性:A=X/10,B=Y/10   (或:注意:选项在种类上不同,而非覆盖范围 — 无完整性评分)
优点 / 缺点:
A) <选项标签>(推荐)
  ✅ <优点 — 具体,可观察,≥40 字符>
  ❌ <缺点 — 诚实,≥40 字符>
B) <选项标签>
  ✅ <优点>
  ❌ <缺点>
总结:<一行总结实际权衡的内容>

D 编号:技能调用中的第一个问题是 D1;自行递增。这是模型级指令,不是运行时计数器。

ELI10 始终存在,使用通俗英语,而不是函数名。建议始终存在。保留 (recommended) 标签;AUTO_DECIDE 依赖它。

完整性:仅当选项在覆盖范围上不同时使用 Completeness: N/10。10 = 完整,7 = 快乐路径,3 = 快捷方式。如果选项在种类上不同,则写:Note: options differ in kind, not coverage — no completeness score.

优点 / 缺点:使用 ✅ 和 ❌。当选择真实且每选项至少 1 个缺点时,每个选项至少 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。

双方工作量:当选项涉及工作时,标记人员团队和 CC+gstack 时间,例如 (human: ~2 days / CC: ~15 min)。使 AI 压缩在决策时可见。

总结行结束权衡。特定技能指令可能添加更严格的规则。

发出前的自我检查

在调用 AskUserQuestion 之前,验证:

  • D 标题存在
  • ELI10 段落存在(利害关系行也存在)
  • 建议行存在且包含具体理由
  • 完整行评分(覆盖范围)或种类说明存在(种类)
  • 每个选项都有 ≥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.

相关技能