← all publishers

AsiaOstrich

@asiaostrich source repo

Report this profile Claim this profile

• 199 skills
• 0 followers
• last month last updated

1. ▌
   Project Discovery · asiaostrich bundle

   [UDS] 在既有代码库新增功能之前，评估项目健康度、架构与风险。 Use when: 接手不熟悉或老旧的项目、动工前先估算风险、建立风险登记簿。 Not for: 对已经熟悉的代码库做持续指标追踪——请用 /metrics；从代码回推规格——请用 /reverse。 Keywords: discovery, project assessment, legacy onboarding, risk register, technical debt, 现状评估, 项目盘点, 风险登记簿, 老旧系统.
   10 installs
2. ▌
   Release Standards · asiaostrich bundle

   [UDS] 引导发布流程——语义化版本、发布模式，以及 start/finish/promote/deploy 的顺序。 Use when: 切一个发布版本、决定语义化版本要升哪一位、把 release candidate 晋级为稳定版、记录一次部署。 Not for: 撰写变更日志条目本身——请用 /changelog；部署的实现机制——请用 /deploy。 Keywords: release, semantic versioning, version bump, release candidate, promote, 发布, 语义化版本, 发版流程, 版本晋级.
   8 installs
3. ▌
   Runbook Assistant · asiaostrich bundle

   引导 Runbook 的撰写、维护与演练。 Use when: 撰写 Runbook、规划演练、审计 Runbook 覆盖范围、事故后更新 Runbook。 Not for: 处理正在进行中的事故——请用 /incident；部署流程本身——请用 /deploy。 Keywords: runbook, operations, drill, on-call, procedure, 运维手册, 演练, 值班, 标准流程.
   11 installs
4. ▌
   AI Friendly Architecture 3 · asiaostrich

   [UDS] 設計 AI 友善架構，包含明確模式、分層文件和語義邊界
   11 installs
5. ▌
   AI Instruction Standards 3 · asiaostrich

   [UDS] 建立和維護 AI 指令檔案（CLAUDE.md、.cursorrules 等）並採用適當結構
   10 installs
6. ▌
   Database Assistant · asiaostrich

   引导数据库设计、迁移与查询优化。 Use when: schema 设计、迁移规划、查询优化、索引策略。 Not for: 应用程序代码迁移或框架升级——请用 /migrate；数据之上的 API 契约——请用 /api-design。 Keywords: database, schema, migration, SQL, index, query, 数据库, 迁移, 查询, 索引策略.
   12 installs
7. ▌
   Dev Workflow Guide · asiaostrich

   [UDS] 把目前的软件开发阶段对应到正确的 UDS 命令与 Skill。 Use when: 不确定手上的任务该用哪个 UDS 命令、初次上手 UDS、带着一个功能从规划走到发布。 Not for: 选择或切换方法论——请用 /methodology；实际执行某阶段的工作——请用该阶段自己的 Skill。 Keywords: workflow, development phase, command routing, which command, UDS guide, 开发阶段, 命令对照, 流程指南.
   9 installs
8. ▌
   Git Flow 2 · asiaostrich bundle

   引导 Git 分支策略、分支命名与合并操作。 Use when: 创建分支、合并、pull request、Git 工作流程相关问题。 Not for: 撰写 commit message——请用 /commit；推送前的安全检查——请用 /push。 Keywords: branch, merge, PR, pull request, GitFlow, GitHub Flow, 分支, 合并, 工作流程, 分支命名.
   12 installs
9. ▌
   Security Assistant · asiaostrich

   引导安全审查与漏洞评估，遵循 OWASP 标准。 Use when: 安全审计、漏洞检查、安全编码审查、威胁建模。 Not for: 自动化的依赖包、CVE 与密钥扫描——请用 /scan；处理正在发生的安全事件——请用 /incident。 Keywords: security, OWASP, vulnerability, authentication, authorization, 信息安全, 漏洞, 认证, 授权, 威胁建模.
   8 installs
10. ▌
    Documentation Guide 3 · asiaostrich bundle

    引导文档结构、内容需求与项目文档的最佳实践。 Use when: 创建 README、撰写文档、规划 docs 目录、项目初始设置、技术文档。 Not for: 从源代码机械式生成文档——请用 /docgen；变更日志条目——请用 /changelog。 Keywords: README, docs, documentation, CONTRIBUTING, CHANGELOG, ARCHITECTURE, API docs, 文档, 说明文档, 技术文档.
    10 installs
11. ▌
    Migration Assistant · asiaostrich

    [UDS] 引导系统性的代码迁移、框架升级与技术现代化。 Use when: 规划框架或主版本升级、评估迁移风险、在 API 迁移前先抓取契约测试的固定样本。 Not for: 维持同一套框架的原地改善——请用 /refactor；数据库 schema 设计——请用 /database。 Keywords: migration, framework upgrade, modernization, breaking change, dependency upgrade, 迁移, 升级, 技术现代化, 破坏性变更.
    11 installs
12. ▌
    AI Collaboration Standards 2 · asiaostrich bundle

    AI 協作標準
    10 installs
13. ▌
    API Design Assistant · asiaostrich

    引导 API 设计，遵循 REST、GraphQL 与 gRPC 最佳实践。 Use when: 设计 API、审查端点、API 版本策略决策。 Not for: 验证运行中的 API 是否符合消费端期待——请用 /contract-test；API 背后的 schema 设计——请用 /database。 Keywords: API, REST, GraphQL, gRPC, endpoint, versioning, 接口设计, 端点, 版本策略.
    9 installs
14. ▌
    Brainstorm Assistant · asiaostrich bundle

    [UDS] 在规格出现之前执行的结构化多角色头脑风暴，并附带评分质量关卡。 Use when: 想法还很模糊、在敲定方向前探索替代方案、需要多样性而不是第一个看似合理的答案。 Not for: 方向已经定了的工作规划——请用 /plan 或 /sdd；记录已经做成的决策——请用 /adr。 Keywords: brainstorm, ideation, divergence, convergence, persona ensemble, devil advocate, 头脑风暴, 发想, 发散收敛, 多角色.
    9 installs
15. ▌
    Metrics 2 · asiaostrich

    [UDS] 長期追蹤開發指標、程式碼品質指標與技術債。 Use when: 評估專案的持續健康狀態、分類技術債並觀察其趨勢、向團隊回報程式碼品質。 Not for: 初次評估一個不熟悉的程式碼庫——請用 /discover；單看測試覆蓋率——請用 /coverage 或 /ac-coverage。 Keywords: metrics, code quality, technical debt, project health, debt trend, 開發指標, 技術債, 專案健康度, 品質趨勢.
    12 installs
16. ▌
    Incident 2 · asiaostrich

    [UDS] 引導事故回應、根因分析和事後檢討文件撰寫
    11 installs
17. ▌
    Metrics 3 · asiaostrich

    [UDS] 追蹤開發指標、程式碼品質指示器與專案健康狀態
    10 installs
18. ▌
    Code Review Assistant 2 · asiaostrich bundle

    [UDS] 系统性代码审查的参考资料：八大审查类别，以及 BLOCKING/IMPORTANT/SUGGESTION 评论前缀。 Use when: 审查 pull request 或 diff、决定审查意见的措辞与优先级、与团队议定审查范围。 Not for: 执行有关卡的审查流程——该部分已移至采用层（XSPEC-095）；提交前的关卡验证——请用 /checkin。 Keywords: code review, pull request review, review checklist, BLOCKING, comment prefix, 代码审查, 审查类别, 评论前缀, 审查清单.
    11 installs
19. ▌
    Refactoring Assistant · asiaostrich bundle

    [UDS] 引导重构决策与策略选择，包含「重构还是重写」这个判断。 Use when: 代码已经难以修改、在战术性与架构性重构之间做选择、要在老旧代码里安全地动手。 Not for: 换到不同框架或主版本——请用 /migrate；清除调试残留与死代码——请用 /sweep。 Keywords: refactor, rewrite, strangler, legacy code, technical debt, code smell, 重构, 重写, 技术债, 坏味道.
    10 installs
20. ▌
    Requirement Assistant · asiaostrich bundle

    [UDS] 撰写符合 INVEST 准则的用户故事与需求。 Use when: 把一个功能构想转成用户故事、定义可测试的验收条件、检视待办项目的质量。 Not for: 带有设计与差异操作的完整规格文档——请用 /sdd；判断这个构想本身对不对——请用 /brainstorm。 Keywords: requirement, user story, INVEST, acceptance criteria, backlog refinement, 需求, 用户故事, 验收条件, 待办梳理.
    11 installs
21. ▌
    Journey Test Assistant 2 · asiaostrich

    [UDS] 从项目描述生成连贯的用户旅程测试计划（TESTPLAN）与旅程 E2E 骨架。 Use when: 新项目从第一天就需要一条测试旅程、测试跨多个故事延续的状态、建立以用户画像驱动的旅程计划。 Not for: 单一 AC 的独立 E2E 骨架——请用 /e2e；测量实际达成的代码覆盖率——请用 /coverage。 Keywords: user journey, TESTPLAN, journey test, persona, cross-story state, 用户旅程, 旅程测试, 测试计划, 用户画像.
    14 installs
22. ▌
    Contract Test Assistant · asiaostrich bundle

    [UDS] 引导 API 与微服务的契约测试策略。 Use when: API 契约、微服务、消费者驱动测试、提供者验证。 Not for: 一开始的 API 接口设计——请用 /api-design；经由 UI 的用户可见流程——请用 /e2e。 Keywords: contract test, Pact, OpenAPI, consumer-driven, provider, 契约测试, 消费者驱动, 提供者验证.
    10 installs
23. ▌
    Observability Assistant · asiaostrich bundle

    引导可观测性建设、指标设计与告警配置。 Use when: 新服务的埋点、SLO 定义、告警设计、成熟度评估。 Not for: 设置数值目标与 Error Budget 策略——请用 /slo；日志格式与级别——请用 /logging-guide。 Keywords: observability, metrics, traces, golden signals, alerting, SLO, 可观测性, 指标, 追踪, 告警.
    9 installs
24. ▌
    Pr Automation Assistant · asiaostrich

    引导 pull request 创建、审查自动化与合并策略。 Use when: 创建 PR、自动化审查流程、配置合并策略。 Not for: 审查本身的内容实质——请用 /code-review；分支命名与合并策略——请用 /git-workflow-guide。 Keywords: pull request, PR, merge, review, GitHub, GitLab, 合并请求, 审查自动化, 合并策略.
    10 installs
25. ▌
    Project Structure Guide 3 · asiaostrich bundle

    依各语言的最佳实践组织项目目录结构的指南。 Use when: 创建项目、重整结构、新增模块、配置构建流程、决定文件该放哪里。 Not for: 专门为 AI 导览而设计的结构——请用 /ai-friendly-architecture；原地重整既有代码——请用 /refactor。 Keywords: project, structure, directory, layout, gitignore, scaffold, file placement, utils, helpers, shared, 项目结构, 目录布局, 文件摆放.
    10 installs
26. ▌
    Retrospective Assistant · asiaostrich bundle

    [UDS] 引导 Sprint 与 Release 周期的结构化团队回顾。 Use when: Sprint 结束、发布后复盘、迭代审视、流程改善。 Not for: 生产环境事故的事后复盘——请用 /incident；追踪两次回顾之间的指标趋势——请用 /metrics。 Keywords: retrospective, retro, sprint review, lessons learned, action items, 回顾, 复盘, 迭代审视, 流程改善.
    10 installs
27. ▌
    Security Scan Assistant · asiaostrich

    引导自动化安全扫描、依赖包审计与密钥检测。 Use when: 依赖包审计、CVE 扫描、密钥检测、许可证合规。 Not for: 人工的威胁建模与安全设计审查——请用 /security；一般的代码整洁度——请用 /sweep。 Keywords: scan, audit, CVE, dependency, secret, SBOM, vulnerability, 扫描, 审计, 依赖包, 密钥检测.
    10 installs
28. ▌
    Test Coverage Assistant · asiaostrich bundle

    [UDS] 以八维度框架分析代码层级的测试覆盖率，并建议该优先补上哪些缺口。 Use when: 覆盖率数字看起来很健康但缺陷照样流出、要在行覆盖率之外判断测试完整性、设定覆盖率目标。 Not for: 需求层级的 AC 与测试追踪——请用 /ac-coverage；补写缺少的测试——请用 /tdd 或 /spec-derive。 Keywords: test coverage, eight dimensions, line coverage, branch coverage, test quality, 测试覆盖率, 八维度, 测试完整性, 覆盖缺口.
    12 installs
29. ▌
    AI Friendly Architecture 4 · asiaostrich

    设计 AI 友善架构，包含明确的模式、分层文档与语义边界。 Use when: 为 AI 协作规划项目结构、优化代码库以利 AI 分析、建立 AI 上下文。 Not for: 编写指令文件本身——请用 /ai-instruction-standards；依语言惯例安排目录布局——请用 /project-structure-guide。 Keywords: architecture, AI-friendly, context, modules, documentation layers, .ai-context.yaml, 架构, AI 友善, 上下文, 语义边界.
    10 installs
30. ▌
    AI Instruction Standards 4 · asiaostrich

    创建并维护 AI 指令文件（CLAUDE.md、AGENTS.md、.cursor/rules/ 等），并采用适当结构。 Use when: 创建 AI 指令文件、区分通用规则与项目特定规则、配置 AI 工具。 Not for: 调整代码库结构让 AI 好导览——请用 /ai-friendly-architecture；要求以证据为基础的回答——请用 /ai-collaboration-standards。 Keywords: CLAUDE.md, AGENTS.md, cursorrules, windsurfrules, clinerules, AI instructions, system prompt, 指令文件, AI 设定, 系统提示词.
    10 installs
31. ▌
    AI Collaboration Standards 3 · asiaostrich bundle

    防止 AI 幻觉，确保分析代码或提出建议时给出以证据为基础的回应。 Use when: 分析代码、提出建议、提供选项，或用户询问把握度／确定性时。 Not for: 编写 AI 指令文件本身——请用 /ai-instruction-standards；审查具体的 diff——请用 /code-review。 Keywords: certainty, assumption, inference, evidence, source, 证据, 假设, 推论, 确定性, 反幻觉.
    9 installs
32. ▌
    Durable Execution Assistant · asiaostrich

    [UDS] 引导容错工作流设计，包含检查点、重试策略与回滚计划。 Use when: 长时间运行的工作流总是中途失败、设计检查点的粒度、选择重试或退避策略。 Not for: 处理正在发生中的线上事故——请用 /incident；部署回滚的实现机制——请用 /deploy。 Keywords: durable execution, checkpoint, retry, backoff, idempotency, rollback, 持久执行, 检查点, 重试策略, 幂等.
    10 installs
33. ▌
    Incident Response Assistant · asiaostrich

    引导事故响应、根因分析与事后复盘文档撰写。 Use when: 生产环境事故、服务中断响应、撰写事后复盘、根因分析（RCA）。 Not for: 在故障发生前设计重试与检查点——请用 /durable；设置告警阈值与 Error Budget 策略——请用 /slo。 Keywords: incident, outage, post-mortem, RCA, root cause, 事故, 服务中断, 事后复盘, 根因分析.
    11 installs
34. ▌
    Metrics Dashboard Assistant · asiaostrich

    [UDS] 长期追踪开发指标、代码质量指标与技术债。 Use when: 评估项目的持续健康状态、分类技术债并观察其趋势、向团队汇报代码质量。 Not for: 初次评估一个不熟悉的代码库——请用 /discover；单看测试覆盖率——请用 /coverage 或 /ac-coverage。 Keywords: metrics, code quality, technical debt, project health, debt trend, 开发指标, 技术债, 项目健康度, 质量趋势.
    13 installs
35. ▌
    Plan 2 · asiaostrich

    从 Spec 文档、OpenSpec 变更或自由文本需求生成 plan.json。 Use when: 把规格转换成可供 /orchestrate 执行的任务计划。 Not for: 执行产出的计划——请用 /orchestrate；判断这个想法值不值得做——请用 /brainstorm。 Keywords: plan, spec, task plan, plan.json, DAG, 计划, 规格, 任务, 任务计划.
    9 installs
36. ▌
    Push 3 · asiaostrich

    AI 辅助的 git push 安全层，提供质量关卡与协作护栏。 Use when: 推送 commit、强制推送、推送到受保护分支、推送 feature 分支。 Not for: 撰写 commit 内容——请用 /commit；分支与合并策略的决策——请用 /git-workflow-guide。 Keywords: git push, force push, protected branch, quality gate, push receipt, PR automation, 推送, 保护分支, 质量门禁, 强制推送.
    8 installs
37. ▌
    Ac Coverage 2 · asiaostrich

    [UDS] Analyze AC-to-test traceability and coverage
    11 installs
38. ▌
    Sweep 3 · asiaostrich

    扫描代码库中的调试残留与代码质量问题；可选择自动修正安全的模式。 Use when: 提交前、PR 审查期间，或定期清理代码库。 Not for: 结构性的代码改善——请用 /refactor；针对安全的专门扫描——请用 /scan。 Keywords: sweep, debug cleanup, console.log, debugger, TODO, ts-any, code quality, 扫描, 清理, 调试残留.
    10 installs
39. ▌
    Push 2 · asiaostrich

    AI 輔助的 git push 安全層，提供品質關卡與協作護欄。 Use when: 推送 commit、強制推送、推送到受保護分支、推送 feature 分支。 Not for: 撰寫 commit 內容——請用 /commit；分支與合併策略的決策——請用 /git-workflow-guide。 Keywords: git push, force push, protected branch, quality gate, push receipt, PR automation, 推送, 保護分支, 品質閘門, 強制推送.
    11 installs
40. ▌
    Sweep 2 · asiaostrich

    掃描程式碼庫中的除錯殘留與程式碼品質問題；可選擇自動修正安全的模式。 Use when: 提交前、PR 審查期間，或定期清理程式碼庫。 Not for: 結構性的程式碼改善——請用 /refactor；針對安全的專門掃描——請用 /scan。 Keywords: sweep, debug cleanup, console.log, debugger, TODO, ts-any, code quality, 掃描, 清理, 除錯殘留.
    13 installs
41. ▌
    Orchestrate 2 · asiaostrich

    以 Claude 原生 Agent tool 編排多任務執行計畫（以 DAG 為基礎，不需外部引擎）。 Use when: 執行帶有平行／循序任務相依關係的 plan.json 檔案。 Not for: 一開始產生計畫——請用 /plan；彼此之間沒有相依關係的單一任務。 Keywords: orchestrate, plan, execute, DAG, task plan, 編排, 執行計畫, 並行, 任務相依.
    12 installs
42. ▌
    AI Friendly Architecture 2 · asiaostrich

    設計 AI 友善架構，包含明確的模式、分層文件與語意邊界。 Use when: 為 AI 協作規劃專案結構、最佳化程式碼庫以利 AI 分析、建立 AI 上下文。 Not for: 撰寫指令檔本身——請用 /ai-instruction-standards；依語言慣例安排目錄配置——請用 /project-structure-guide。 Keywords: architecture, AI-friendly, context, modules, documentation layers, .ai-context.yaml, 架構, AI 友善, 上下文, 語意邊界.
    12 installs
43. ▌
    AI Instruction Standards 2 · asiaostrich

    建立並維護 AI 指令檔（CLAUDE.md、AGENTS.md、.cursor/rules/ 等），並採用適當結構。 Use when: 建立 AI 指令檔、區分通用規則與專案特定規則、設定 AI 工具。 Not for: 調整程式碼庫結構讓 AI 好導覽——請用 /ai-friendly-architecture；要求以證據為基礎的回答——請用 /ai-collaboration-standards。 Keywords: CLAUDE.md, AGENTS.md, cursorrules, windsurfrules, clinerules, AI instructions, system prompt, 指令檔, AI 設定, 系統提示詞.
    9 installs
44. ▌
    Code Review Assistant · asiaostrich bundle

    Systematic code review checklist and pre-commit quality gates for PRs. Use when: reviewing pull requests, checking code quality, before committing code. Keywords: review, PR, pull request, checklist, quality, commit, 審查, 檢查, 簽入.
    11 installs
45. ▌
    Refactor · asiaostrich bundle

    [UDS] Guide refactoring decisions and strategy selection, including the refactor-versus-rewrite call. Use when: code has become hard to change, choosing between tactical and architectural refactoring, working safely inside legacy code. Not for: moving to a different framework or major version — use /migrate; clearing debug artifacts and dead code — use /sweep. Keywords: refactor, rewrite, strangler, legacy code, technical debt, code smell, 重構, 重寫, 技術債.
    10 installs
46. ▌
    Requirement · asiaostrich bundle

    [UDS] Write user stories and requirements that satisfy the INVEST criteria. Use when: turning a feature idea into a user story, defining testable acceptance criteria, checking a backlog item for quality. Not for: full specification documents with design and delta operations — use /sdd; deciding whether the idea is right at all — use /brainstorm. Keywords: requirement, user story, INVEST, acceptance criteria, backlog refinement, 需求, 使用者故事, 驗收條件.
    11 installs
47. ▌
    Journey Test Assistant · asiaostrich

    [UDS] Generate coherent user-journey test plans (TESTPLAN) and journey E2E skeletons from a project description. Use when: a new project needs a test journey from day one, testing state carried across multiple stories, building persona-driven journey plans. Not for: isolated per-AC E2E skeletons — use /e2e; measuring achieved code coverage — use /coverage. Keywords: user journey, TESTPLAN, journey test, persona, cross-story state, 使用者旅程, 旅程測試, 測試計畫.
    13 installs
48. ▌
    Contract Test · asiaostrich bundle

    [UDS] Guide contract testing strategy for APIs and microservices. Use when: API contracts, microservices, consumer-driven testing, provider verification. Not for: designing the API surface in the first place — use /api-design; user-visible flows through a UI — use /e2e. Keywords: contract test, Pact, OpenAPI, consumer-driven, provider.
    16 installs
49. ▌
    Observability · asiaostrich bundle

    Guide observability setup, metrics design, and alerting configuration. Use when: new service instrumentation, SLO definition, alert design, maturity assessment. Not for: setting numeric targets and Error Budget policy — use /slo; log format and levels — use /logging-guide. Keywords: observability, metrics, traces, golden signals, alerting, SLO.
    12 installs
50. ▌
    Pr · asiaostrich

    Guide pull request creation, review automation, and merge strategies. Use when: creating PRs, automating reviews, configuring merge policies. Not for: the substance of the review itself — use /code-review; branch naming and merge strategy — use /git-workflow-guide. Keywords: pull request, PR, merge, review, GitHub, GitLab.
    11 installs
51. ▌
    Project Structure Guide · asiaostrich bundle

    Guide for organizing project directories following language-specific best practices. Use when: creating projects, reorganizing structure, adding modules, setting up builds, deciding file placement. Not for: structuring specifically for AI navigation — use /ai-friendly-architecture; restructuring existing code in place — use /refactor. Keywords: project, structure, directory, layout, gitignore, scaffold, file placement, utils, helpers, shared, where to put.
    10 installs
52. ▌
    Retrospective · asiaostrich bundle

    [UDS] Guide structured team retrospectives for Sprint and Release cycles. Use when: sprint end, release post-mortem, iteration review, process improvement. Not for: post-mortems for a production incident — use /incident; tracking metric trends between retros — use /metrics. Keywords: retrospective, retro, sprint review, lessons learned, action items.
    11 installs
53. ▌
    Scan · asiaostrich

    Guide automated security scanning, dependency auditing, and secret detection. Use when: dependency audit, CVE scanning, secret detection, license compliance. Not for: manual threat modeling and secure design review — use /security; general code cleanliness — use /sweep. Keywords: scan, audit, CVE, dependency, secret, SBOM, vulnerability.
    12 installs
54. ▌
    Coverage · asiaostrich bundle

    [UDS] Analyze code-level test coverage across the eight-dimension framework and recommend which gaps to close. Use when: coverage percentages look healthy but defects still ship, judging test completeness beyond line percentage, setting coverage targets. Not for: requirement-level AC-to-test traceability — use /ac-coverage; writing the missing tests — use /tdd or /spec-derive. Keywords: test coverage, eight dimensions, line coverage, branch coverage, test quality, 測試覆蓋率, 八維度, 測試完整性.
    12 installs
55. ▌
    Errors · asiaostrich

    [UDS] 設計一致的錯誤碼，遵循 PREFIX_CATEGORY_NUMBER 格式
    9 installs
56. ▌
    AI Friendly Architecture · asiaostrich

    Design AI-friendly architecture with explicit patterns, layered documentation, and semantic boundaries. Use when: structuring projects for AI collaboration, optimizing codebase for AI analysis, setting up AI context. Not for: writing the instruction files — use /ai-instruction-standards; language-conventional directory layout — use /project-structure-guide. Keywords: architecture, AI-friendly, context, modules, documentation layers, .ai-context.yaml.
    14 installs
57. ▌
    AI Instruction Standards · asiaostrich

    Create and maintain AI instruction files (CLAUDE.md, AGENTS.md, .cursor/rules/, etc.) with proper structure. Use when: creating AI instruction files, separating universal vs project-specific rules, configuring AI tools. Not for: shaping the codebase so AI can navigate it — use /ai-friendly-architecture; enforcing evidence-based answers — use /ai-collaboration-standards. Keywords: CLAUDE.md, AGENTS.md, cursorrules, windsurfrules, clinerules, AI instructions, system prompt.
    9 installs
58. ▌
    AI Collaboration Standards · asiaostrich bundle

    Prevent AI hallucination and ensure evidence-based responses when analyzing code or making suggestions. Use when: analyzing code, making recommendations, providing options, or when user asks about confidence/certainty. Not for: authoring the AI instruction files themselves — use /ai-instruction-standards; reviewing a concrete diff — use /code-review. Keywords: certainty, assumption, inference, evidence, source.
    11 installs
59. ▌
    Durable · asiaostrich

    [UDS] Guide fault-tolerant workflow design with checkpoints, retry policies, and rollback plans. Use when: a long-running workflow keeps failing partway, designing checkpoint granularity, choosing a retry or backoff strategy. Not for: responding to a production incident already in progress — use /incident; deployment rollback mechanics — use /deploy. Keywords: durable execution, checkpoint, retry, backoff, idempotency, rollback, 持久執行, 檢查點, 重試策略.
    15 installs
60. ▌
    Incident · asiaostrich

    Guide incident response, root cause analysis, and post-mortem documentation. Use when: production incident, outage response, post-mortem writing, RCA. Not for: designing retries and checkpoints before failure — use /durable; setting alert thresholds and Error Budget policy — use /slo. Keywords: incident, outage, post-mortem, RCA, root cause.
    14 installs
61. ▌
    Deploy · asiaostrich

    Guide reliable deployments without CI/CD platforms (GitHub Actions / GitLab CI). Use when: deploying to VPS, air-gapped servers, or environments without CI/CD infrastructure. Not for: pipelines on GitHub Actions or GitLab CI — use /ci-cd; version bumps and release promotion — use /release. Keywords: deployment, no-cicd, shell script, blue-green, smoke test, rollback.
    10 installs
62. ▌
    Error Code Guide · asiaostrich

    Design consistent error codes following the PREFIX_CATEGORY_NUMBER format. Use when: defining error codes, creating error handling, designing APIs. Not for: log format and levels — use /logging-guide; handling errors that already reached production — use /incident. Keywords: error code, error handling, error format, API errors.
    11 installs
63. ▌
    Reverse · asiaostrich bundle

    [UDS] System archeology — reverse engineer an existing system across the Logic, Data, and Runtime dimensions. Use when: documenting an undocumented system, recovering specifications from existing code, mapping an unknown data model or runtime topology. Not for: assessing health and risk before a feature — use /discover; deriving tests forward from an approved spec — use /spec-derive. Keywords: reverse engineering, system archeology, legacy code, spec extraction, data model, runtime, 反向工程, 系統考古, 規格提取.
    13 installs
64. ▌
    Checkin · asiaostrich bundle

    [UDS] Reference for pre-commit quality gates: gate definitions, checklist items, and never-commit rules. Use when: deciding what must pass before a commit, auditing which quality gates a project enforces, checking readiness to check in. Not for: executing the gate sequence or aborting a commit — that moved to the adoption layer (XSPEC-095); finding and removing debug artifacts — use /sweep. Keywords: check-in, pre-commit, quality gate, commit readiness, never commit, 簽入, 提交前檢查, 品質關卡.
    15 installs
65. ▌
    Discover · asiaostrich bundle

    [UDS] Assess project health, architecture, and risks before adding features to an existing codebase. Use when: onboarding to an unfamiliar or legacy project, sizing risk before starting a feature, building a risk register. Not for: ongoing metric tracking on a codebase you already know — use /metrics; recovering specs from code — use /reverse. Keywords: discovery, project assessment, legacy onboarding, risk register, technical debt, 現況評估, 專案盤點, 風險登記簿.
    14 installs
66. ▌
    Release · asiaostrich bundle

    [UDS] Guide the release process — semantic versioning, release modes, and the start/finish/promote/deploy sequence. Use when: cutting a release, deciding a semantic version bump, promoting a release candidate to stable, recording a deployment. Not for: writing the changelog entries themselves — use /changelog; the deployment mechanics — use /deploy. Keywords: release, semantic versioning, version bump, release candidate, promote, 發布, 語意化版本, 發版流程.
    11 installs
67. ▌
    Runbook · asiaostrich bundle

    Guide runbook creation, maintenance, and drill exercises. Use when: writing runbooks, planning drills, auditing runbook coverage, post-incident runbook updates. Not for: responding to an incident already in progress — use /incident; the deployment procedure itself — use /deploy. Keywords: runbook, operations, drill, on-call, procedure.
    11 installs
68. ▌
    Database · asiaostrich

    Guide database design, migration, and query optimization. Use when: schema design, migration planning, query optimization, index strategy. Not for: application code migration or framework upgrades — use /migrate; the API contract over the data — use /api-design. Keywords: database, schema, migration, SQL, index, query.
    15 installs
69. ▌
    Dev Workflow · asiaostrich bundle

    [UDS] Map the current software development phase to the right UDS commands and skills. Use when: unsure which UDS command fits the task at hand, onboarding to UDS, walking a feature from planning through release. Not for: choosing or switching a methodology — use /methodology; doing the actual work of a phase — use that phase own skill. Keywords: workflow, development phase, command routing, which command, UDS guide, 開發階段, 指令對照, 流程指南.
    11 installs
70. ▌
    Git Workflow Guide · asiaostrich bundle

    Guide Git branching strategies, branch naming, and merge operations. Use when: creating branches, merging, pull requests, Git workflow questions. Not for: composing the commit message — use /commit; the safety checks around pushing — use /push. Keywords: branch, merge, PR, pull request, GitFlow, GitHub Flow.
    8 installs
71. ▌
    Security · asiaostrich

    Guide security review and vulnerability assessment following OWASP standards. Use when: security audit, vulnerability check, secure coding review, threat modeling. Not for: automated dependency, CVE, and secret scanning — use /scan; handling a breach in progress — use /incident. Keywords: security, OWASP, vulnerability, authentication, authorization.
    13 installs
72. ▌
    Documentation Guide · asiaostrich bundle

    Guide documentation structure, content requirements, and project documentation best practices. Use when: creating README, documentation, docs folder, project setup, technical docs. Not for: generating docs mechanically from source — use /docgen; changelog entries — use /changelog. Keywords: README, docs, documentation, CONTRIBUTING, CHANGELOG, ARCHITECTURE, API docs.
    11 installs
73. ▌
    Migrate · asiaostrich

    [UDS] Guide systematic code migration, framework upgrades, and technology modernization. Use when: planning a framework or major-version upgrade, assessing migration risk, capturing contract-test fixtures before an API migration. Not for: in-place improvement that keeps the same framework — use /refactor; database schema design — use /database. Keywords: migration, framework upgrade, modernization, breaking change, dependency upgrade, 遷移, 升級, 技術現代化.
    16 installs
74. ▌
    API Design · asiaostrich

    Guide API design following REST, GraphQL, and gRPC best practices. Use when: designing APIs, reviewing endpoints, API versioning decisions. Not for: verifying a running API against its consumers — use /contract-test; schema design behind the API — use /database. Keywords: API, REST, GraphQL, gRPC, endpoint, versioning.
    11 installs
75. ▌
    Brainstorm · asiaostrich bundle

    [UDS] Structured multi-persona brainstorming with a scored quality gate, run before a spec exists. Use when: an idea is still vague, exploring alternatives before committing to a direction, needing diversity rather than the first plausible answer. Not for: planning work whose direction is already decided — use /plan or /sdd; recording a decision already made — use /adr. Keywords: brainstorm, ideation, divergence, convergence, persona ensemble, devil advocate, 腦力激盪, 發想, 發散收斂.
    11 installs
76. ▌
    Code Review · asiaostrich bundle

    [UDS] Reference for systematic code review: eight review categories and BLOCKING/IMPORTANT/SUGGESTION comment prefixes. Use when: reviewing a pull request or diff, deciding how to phrase and prioritise review comments, agreeing review scope with a team. Not for: executing a gated review workflow — that moved to the adoption layer (XSPEC-095); pre-commit gate verification — use /checkin. Keywords: code review, pull request review, review checklist, BLOCKING, comment prefix, 程式碼審查, 審查類別, 評論前綴.
    14 installs
77. ▌
    Plan · asiaostrich

    Generate plan.json from Spec documents, OpenSpec changes, or free-text requirements. Use when: converting specifications into executable task plans for /orchestrate. Not for: executing the resulting plan — use /orchestrate; deciding whether the idea is worth doing — use /brainstorm. Keywords: plan, spec, task plan, plan.json, DAG.
    12 installs
78. ▌
    Push · asiaostrich

    AI-assisted safety layer for git push operations with quality gates and collaboration guardrails. Use when: pushing commits, force pushing, pushing to protected branches, pushing feature branches. Not for: composing the commit — use /commit; branch and merge strategy decisions — use /git-workflow-guide. Keywords: git push, force push, protected branch, quality gate, push receipt, PR automation.
    13 installs
79. ▌
    Sweep · asiaostrich

    Scan codebase for debug artifacts and code quality issues; optionally auto-fix safe patterns. Use when: before committing, during PR review, or periodic codebase cleanup. Not for: structural code improvement — use /refactor; security-specific scanning — use /scan. Keywords: sweep, debug cleanup, console.log, debugger, TODO, ts-any, code quality.
    12 installs
80. ▌
    Ac Coverage · asiaostrich

    [UDS] Analyze AC-to-test traceability and generate requirement-level coverage reports. Use when: auditing which acceptance criteria have tests, building a traceability matrix from a SPEC file, finding uncovered AC before release. Not for: code-level line/branch/function coverage — use /coverage; writing the missing tests — use /tdd or /spec-derive. Keywords: AC coverage, traceability, acceptance criteria, SPEC, traceability matrix, 驗收條件, 需求追蹤, 覆蓋率矩陣.
    14 installs
81. ▌
    Orchestrate · asiaostrich

    Orchestrate multi-task execution plans using Claude's native Agent tool (DAG-based, no external engine). Use when: executing a plan.json file with parallel/sequential task dependencies. Not for: producing the plan in the first place — use /plan; single tasks with no dependencies between them. Keywords: orchestrate, plan, execute, DAG, task plan.
    12 installs
82. ▌
    Adr · asiaostrich bundle

    [UDS] Create, manage, and track Architecture Decision Records (ADR). Use when: architecture decisions, technology choices, design trade-offs, pattern selection. Not for: decisions that do not change architecture — record them in the spec or commit; ideas not yet formed enough to decide — use /brainstorm. Keywords: ADR, architecture decision, decision record, trade-off.
    13 installs
83. ▌
    Bdd · asiaostrich bundle

    [UDS] Reference for Behavior-Driven Development: Gherkin Given-When-Then format and Three Amigos structure. Use when: writing or reviewing .feature scenarios, choosing ubiquitous language, running a discovery conversation about behaviour. Not for: executing the BDD lifecycle or RED/GREEN automation — that moved to the adoption layer (XSPEC-095); turning .feature files into E2E skeletons — use /e2e. Keywords: BDD, Gherkin, Given When Then, feature file, scenario, Three Amigos, 行為驅動開發, 場景, 特性檔.
    14 installs
84. ▌
    E2e · asiaostrich

    [UDS] Generate E2E test skeletons from BDD .feature scenarios, with framework detection and coverage gap analysis. Use when: turning finished .feature scenarios into runnable E2E skeletons, detecting the project E2E framework, finding AC with no E2E coverage. Not for: multi-story journeys with shared state — use the journey-test skill; writing the .feature scenarios themselves — use /bdd. Keywords: E2E, end-to-end test, feature file, test skeleton, framework detection, 端對端測試, 測試骨架, 場景轉測試.
    15 installs
85. ▌
    Logging Guide · asiaostrich

    Implement structured logging with proper log levels and sensitive data handling. Use when: adding logging, debugging, setting up observability. Not for: metrics, traces, and alerting design — use /observability; error code taxonomy — use /error-code-guide. Keywords: logging, log level, structured logging, observability.
    14 installs
86. ▌
    Skill Builder · asiaostrich

    [UDS] Turn a repeated manual process into a properly scoped Skill, with the right amount of process along the way. Use when: the same multi-step sequence has been done manually three or more times, formalising an ad-hoc Skill, deciding where a Skill belongs. Not for: recording historical facts or project state — that belongs in memory, not a Skill; one-off tasks that will not recur. Keywords: skill, skill builder, process knowledge, repeated process, automation, 技能建立, 流程知識, 自動化.
    12 installs
87. ▌
    Slo · asiaostrich bundle

    Guide SLI selection, SLO setting, and Error Budget management. Use when: defining service quality targets, setting up SLO-based alerting, Error Budget policy. Not for: instrumentation and metric collection — use /observability; responding to an active breach of the target — use /incident. Keywords: SLI, SLO, SLA, Error Budget, burn rate, service level.
    10 installs
88. ▌
    Tdd · asiaostrich bundle

    [UDS] Reference for Test-Driven Development: the Red-Green-Refactor cycle, FIRST principles, and Arrange-Act-Assert structure. Use when: writing a failing test before implementation, structuring a test with Arrange-Act-Assert, checking tests against FIRST. Not for: driving the RED/GREEN cycle interactively — that moved to the adoption layer (XSPEC-095); measuring how much code the tests cover — use /coverage. Keywords: TDD, test first, Red Green Refactor, FIRST, Arrange Act Assert, unit test, 測試驅動開發, 紅綠重構, 單元測試.
    13 installs
89. ▌
    Testing Guide · asiaostrich bundle

    Testing pyramid and test writing standards for UT/IT/ST/E2E. Supports ISTQB and Industry Pyramid frameworks. Use when: writing tests, discussing test coverage, test strategy, or test naming. Not for: driving a Red-Green-Refactor cycle — use /tdd; measuring achieved coverage — use /coverage. Keywords: test, unit, integration, e2e, coverage, mock, ISTQB, SIT.
    10 installs
90. ▌
    Atdd · asiaostrich bundle

    [UDS] Reference for Acceptance Test-Driven Development: INVEST criteria, Gherkin AC format, and Three Amigos structure. Use when: defining acceptance criteria with a product owner, running a specification workshop, checking a user story against INVEST. Not for: executing the ATDD lifecycle or enforcing PO sign-off gates — that moved to the adoption layer (XSPEC-095); writing unit tests — use /tdd. Keywords: ATDD, acceptance test, acceptance criteria, INVEST, specification workshop, Three Amigos, 驗收測試驅動開發, 驗收條件, 規格工作坊.
    11 installs
91. ▌
    Docgen · asiaostrich bundle

    [UDS] Generate usage documentation (cheatsheets, references, guides) from project sources. Use when: producing a cheatsheet or feature reference from CLI and skill definitions, regenerating docs after commands change, checking generated docs are current. Not for: deciding what documentation a project needs or writing prose by hand — use /documentation-guide; changelog entries — use /changelog. Keywords: docgen, usage docs, cheatsheet, feature reference, generated documentation, 使用文件, 速查表, 文件產生.
    11 installs
92. ▌
    Audit · asiaostrich

    [UDS] Diagnose UDS installation health and submit structured feedback upstream. Use when: .standards/ looks broken or out of sync, verifying manifest integrity, reporting friction with an existing UDS standard. Not for: auditing your own application code quality — use /metrics or /code-review; dependency and secret scanning — use /scan. Keywords: UDS audit, health check, manifest integrity, standards feedback, friction, 安裝健康, 標準稽核, 回饋.
    10 installs
93. ▌
    Changelog · asiaostrich bundle

    [UDS] Generate and maintain CHANGELOG.md entries in Keep a Changelog format. Use when: writing changelog entries from commit history, filling the Unreleased section, categorising changes as Added/Changed/Fixed. Not for: choosing the next version number or running the release — use /release; writing the commit messages themselves — use /commit. Keywords: changelog, CHANGELOG.md, Keep a Changelog, release notes, unreleased, 變更日誌, 發布說明, 版本紀錄.
    14 installs
94. ▌
    CI CD · asiaostrich

    Guide CI/CD pipeline design, configuration, and optimization. Use when: setting up pipelines, optimizing build times, configuring deployment stages. Not for: deploying without a CI/CD platform — use /deploy; version bumps and promotion — use /release. Keywords: CI/CD, pipeline, GitHub Actions, deployment, build.
    15 installs
95. ▌
    Methodology · asiaostrich bundle

    [UDS] Select and track the active development methodology (SDD, BDD, TDD) for a project. Use when: deciding which methodology a project should follow, switching methodology, checking which phase the current methodology is in. Not for: finding which command to run at a given development stage — use /dev-workflow; executing a methodology itself — use /sdd, /bdd, or /tdd. Keywords: methodology, SDD, BDD, TDD, phase tracking, methodology selection, 方法論, 開發方法選擇, 階段追蹤.
    13 installs
96. ▌
    Knowledge Graph · asiaostrich bundle

    [UDS] Trace impact chains across specs, decisions, and code via a knowledge graph, with a Markdown fallback when no engine is present. Use when: asking what a spec or decision affects, finding which code implements an artifact, tracing dependencies between specs, ADRs, and modules. Not for: plain text search with no spec or decision anchor — use Grep; authoring the spec itself — use /sdd. Keywords: knowledge graph, impact chain, traceability, spec impact, decision graph, 知識圖, 影響鏈, 規格追蹤.
    10 installs
97. ▌
    Spec Derive · asiaostrich bundle

    [UDS] Derive BDD scenarios, TDD skeletons, integration and E2E tests, and ATDD tables from an approved specification. Use when: a spec has been approved and needs test artifacts, generating tagged test skeletons from acceptance criteria, producing contract stubs from a spec. Not for: recovering a spec from existing code — use /reverse; writing or reviewing the spec itself — use /sdd. Keywords: forward derivation, spec to test, BDD scenario, TDD skeleton, ATDD table, 正向推演, 規格衍生, 測試生成.
    17 installs
98. ▌
    Sdd · asiaostrich bundle

    [UDS] Create and review specification documents before writing code — spec format, states, and delta operations. Use when: a change needs a written spec first, reviewing a spec for completeness, amending an existing spec with delta sections. Not for: executing a gated SDD lifecycle — that moved to the adoption layer (XSPEC-095); lightweight micro-specs for rapid iteration — use the uds spec command. Keywords: SDD, spec, specification, design document, delta operation, spec review, 規格驅動開發, 規格文件, 變更操作.
    7 installs
99. ▌
    Commit · asiaostrich bundle

    [UDS] Generate commit messages that follow Conventional Commits, including the bilingual format. Use when: writing a commit message for staged changes, choosing a type and scope, producing a bilingual English and 中文 subject and body. Not for: deciding whether the change is ready to commit — use /checkin; aggregating commits into release notes — use /changelog. Keywords: commit message, Conventional Commits, feat, fix, refactor, scope, bilingual, 提交訊息, 雙語 commit, 提交規範.
    10 installs