Explorar skills

DDD 端到端交付流程。DDD 理論基礎（戰略設計、戰術設計、CQRS）→ Event Storming 領域探索 → SA 領域分析 → SD 戰術設計 → 實作規劃。關鍵字: ddd, domain driven design, 領域驅動, bounded context, aggregate, event storming, 事件風暴, sa, sd, 系統分析, 系統設計, implementation plan, 實作規劃, cqrs, 戰略設計, 戰術設計, 限界上下文, 聚合, 聚合根, 領域事件, 通用語言, ubiquitous language, context mapping, 上下文映射

Structure delivery planning, cross-functional alignment, and sprint or milestone planning. Use this skill when a team needs to coordinate execution across product, engineering, and design.

Generate a copy-paste-ready GPT prompt that produces a polished architecture or workflow diagram image, and optionally render the image directly via Codex CLI image generation. Trigger when the user wants to create, make, generate, draw, or visualize a diagram, architecture image, system workflow picture, or flowchart, or pastes a Mermaid diagram asking for a polished image.

Author robust /goal conditions for Claude Code v2.1.139+. Provides the 4-piece recipe (end state + proof + invariant + bound), 6 pattern templates (migration, file-size budget, queue drain, test repair, dep upgrade, docs/changelog), and an anti-pattern checklist. The evaluator that judges /goal conditions only reads the transcript — never runs tools. This skill exists to make conditions the evalua

個別プロダクト/ワークロード設計用スキル。AWS / Azure / GCP を対象に、ベンダー中立のワークロードモデル、ベンダー別サービスマッピング、実装仕様、オブザーバビリティ仕様、コスト最適化ヒント、IaC スケルトンを生成する。コンピュート、データベース、メッセージング、ストレージ、キャッシュ、CDN のサービス選定を、可用性、レイテンシ、データ機密性、トラフィックパターン、整合性、復旧目標、コストポスチャに基づいて行う。特定のアプリケーションワークロード、マイクロサービスアーキテクチャ、プロダクトインフラ、ユースケースごとのクラウドサービス選定の設計やレビューに使用すること。1 クラウドのみの言及でも発動する。EC2/App Service/Cloud Run、RDS/Azure SQL/Cloud SQL、SQS/Service Bus/Pub/Sub などのサービス比較もワー

Researches the user's market, competitors, and competitive positioning to build a complete ICP profile. Shows findings for user approval before proceeding. Triggers: /profile, "research my market", "who are my competitors". Reads: ./gtm/company.md, ./gtm/icp.md. Writes: updates ./gtm/icp.md with competitive positioning. Standalone: yes (asks for domain if company.md missing).

Use when planning any non-trivial change — refactor, bug fix, migration, optimisation, communication — and the agent should find the natural seams / high-leverage points of the target system rather than brute-forcing through. Cut at joints (low resistance, clean result), not at bone (high resistance, blade dulls, messy result). The patron-saint chengyu of working WITH the grain of the system.

Adversarial red team — find security holes, logic bugs, wasted resources. Triggers: "critic", "red team", "attack this", "what's wrong", "find flaws", "challenge this". NOT FOR: code review before merge (use review), debugging (use systematic-debugging). Produces: prioritized list of flaws with severity and remediation steps.

Import and adapt an existing AI app concept (prompt, web form, API spec) into a Genai recipe skeleton following the clean-room philosophy. Use when the user wants to port or convert an existing AI application into a Genai skill.

Audits Claude's own output against the user's original request in the current session — did Claude do exactly what was asked, no more, no less? Checks requirements, styles, constraints, and flags scope creep (extras the user never asked for). Use when the user says "verify", "check your work", "did you follow my request", "audit this", "compliance check", or questions whether Claude improvised, mi

Short-form (X / LinkedIn) comparison of how something is done today vs how it will be done in 1–5 years. Strong for tech / AI / tooling takes. Use when the user wants to frame a directional bet, a tooling shift, or an obsolescence call — anything where the punchline is "this is the present; here's the future".

Full-spectrum web application VAPT skill for Claude Code, OpenCode, Codex CLI & Gemini CLI — from reconnaissance to exploitation to remediation reporting