882 件 ・ 関連度順
概要と使いどころ
This skill teaches security teams how to detect and respond to unauthorized cryptocurrency mining operations in cloud environments. It covers identifying cryptomining indicators through compute usage anomalies, network traffic patterns to mining pools, GuardDuty CryptoCurrency findings, and runtime process monitoring on EC2, ECS, EKS, and Azure Automation workloads.
日本語の概要は準備中です。原文の説明を表示しています。
Turns product or tech specs into concrete Notion tasks that Claude code can implement. Breaks down spec pages into detailed implementation plans with clear tasks, acceptance criteria, and progress tracking to guide development from requirements to completion.
日本語の概要は準備中です。原文の説明を表示しています。
Walk every branching path and boundary condition in content, report only unhandled edge cases. Orthogonal to adversarial review - method-driven not attitude-driven. Use when you need exhaustive edge-case analysis of code, specs, or diffs.
日本語の概要は準備中です。原文の説明を表示しています。
Choose and implement local, directed, broadcast, cancellable, and network events.
日本語の概要は準備中です。原文の説明を表示しています。
Design SS14 components as serialized state in the correct assembly.
日本語の概要は準備中です。原文の説明を表示しています。
Implement entity behavior, subscriptions, lifecycle handling, and reusable action APIs.
日本語の概要は準備中です。原文の説明を表示しています。
Implement complete SS14 features across ownership, ECS, networking, resources, localization, UI, and tests.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a professional product specification sheet with images, feature tables, technical specs, and contact information.
日本語の概要は準備中です。原文の説明を表示しています。
Extract product details from a supplier data sheet, then generate a branded e-commerce listing image with the product name, price, and key specs.
日本語の概要は準備中です。原文の説明を表示しています。
Convert external documents — specs, contracts, reports — to markdown for knowledge base ingestion.
日本語の概要は準備中です。原文の説明を表示しています。
Deploy Abridge clinical AI integration to HIPAA-compliant cloud infrastructure. Use when deploying to GCP Cloud Run, AWS ECS, or Azure Container Apps with healthcare-grade secrets management and compliance controls. Trigger: "deploy abridge", "abridge production deploy", "abridge Cloud Run", "abridge AWS deploy", "abridge HIPAA infrastructure".
日本語の概要は準備中です。原文の説明を表示しています。
Reconcile gene trees against a species tree under probabilistic models of duplication, transfer, and loss (DTL) using ALE (Szöllősi 2013 amalgamated likelihood), GeneRax (Morel 2020 ML reconciliation), AleRax (Morel 2024 co-estimation), Whale.jl (Bayesian DTL+WGD), RANGER-DTL 2 parsimony, NOTUNG, ecceTERA, and Treerecs. Use when inferring ancestral gene-family content, distinguishing duplication from horizontal transfer from differential loss, rooting deep species trees from gene-content signals (STRIDE / Williams 2017 ALE-rooting), counting DTL events per branch, refining noisy gene trees against a species tree, modeling WGD events jointly with DTL, or producing publication-grade gene-family histories for phylogenomic / comparative analyses.
日本語の概要は準備中です。原文の説明を表示しています。
API documentation workflow for generating OpenAPI specs, creating developer guides, and maintaining comprehensive API documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Use by any agent before writing specs, editing code, or changing workflow files when the change could add compatibility behavior, aliases, silent fallbacks, or default-value fallbacks.
日本語の概要は準備中です。原文の説明を表示しています。
Create complete specs (requirements, design, tasks) for all features in roadmap.md using parallel sub-agent dispatch by dependency wave.
日本語の概要は準備中です。原文の説明を表示しています。
Review a task implementation against approved specs, task boundaries, and verification evidence. Use after an implementer finishes a task, after remediation, or before accepting a task as complete.
日本語の概要は準備中です。原文の説明を表示しています。
Responde dimensão, proporção, área segura, tipografia mínima e contagem de slides por plataforma. Use quando o usuário perguntar "qual o tamanho", "que dimensão", "quantos slides", "área segura", "cabe texto onde", "especificação do formato", ou quando outra skill precisar validar medidas. Fonte única desses números.
日本語の概要は準備中です。原文の説明を表示しています。
Write and refine high-quality user stories — INVEST criteria, "As a X, I want Y, so that Z" format, Gherkin acceptance criteria when applicable, definition of ready, anti-patterns, and a review checklist. Use when creating or reviewing user stories, PRD section 6, backlog items, or acceptance criteria. Do NOT use for technical specs, architecture decisions, or task decomposition.
日本語の概要は準備中です。原文の説明を表示しています。
Arquitetura e diagnóstico AWS — VPC, EC2, ECS, EKS, ALB, NLB, RDS, ElastiCache, S3, CloudFront, Route53, IAM, WAF, GuardDuty. Use quando o usuário disser "AWS", "VPC", "ALB", "RDS", "revisar a arquitetura", "Well-Architected", "subnet", "security group", "IAM", ou citar qualquer serviço AWS. Leitura livre; qualquer mudança passa pelo portão de confirmação.
日本語の概要は準備中です。原文の説明を表示しています。
Review code changes against linked GitHub issue specs to catch implementation drift — building something plausible but wrong. Checks each acceptance criterion against actual code.
日本語の概要は準備中です。原文の説明を表示しています。
UI runtime 驗證 SKILL — 刷新 Cocos asset-db、執行 validate-ui-specs.js、headless-snapshot-test.js、capture-ui-screens.js，並依環境選用 cocos-screenshot 或 cocos-preview-qa 檢查實際畫面殘差，回寫 generated-review / runtime-verdict。USE FOR: 修改 layout / skin / screen / content / Panel / UI 資產後的驗證收尾。DO NOT USE FOR: 純資產生成、無 target 的整專案大範圍探索。
日本語の概要は準備中です。原文の説明を表示しています。
UI 資產品質驗證 SKILL — 執行 validate-visual-assets.js、validate-ui-specs.js 與必要的 snapshot regression，對 skin family 資產、screen package、proof draft / family-map 進行全面驗證，並回寫 generated-review。USE FOR: 任何 UI 資產生成後、在 ui-preview-judge 前必須先通過的 QA 關卡。DO NOT USE FOR: debug runtime 崩潰（用 cocos-log-reader）、Layout 佈局調整（用 ui-vibe-pipeline）。
日本語の概要は準備中です。原文の説明を表示しています。
Run a structured discovery interview and produce a complete, developer-ready Product Requirements Document. Load when the user asks to write a PRD, create product requirements, document a feature, define user stories with acceptance criteria, or turn a rough idea into a formal product requirements document. Also triggers on "document this feature", "write requirements for", "create a one-pager", "turn this into a PRD", "I need a PRD for", or any request to produce a structured product document for stakeholder alignment or engineering handoff. Supports Full PRD, Lean PRD, and One-Pager formats. Note: for executable feature specifications (FRs, NFRs, ACs as Given/When/Then consumable by AI coding agents), route to `feature-spec` instead — PRDs frame the product, feature-specs encode the implementable contract.
日本語の概要は準備中です。原文の説明を表示しています。
Tactical fast path: turn a small problem, bug report, edit request, or narrow refactor into three deliverables — a brief change-spec (docs/specs/), a detailed implementation-ready plan (docs/plans/), and a TODO.md with agent-pickable tasks and milestones. Load when the user describes a tactical problem and wants quick planning artifacts, says "plan this change", "create a TODO", "write a plan for this", "problem to plan", "break this into tasks for agents", "I want to change X — plan it", or when process-decomposer routes here after determining the user needs lightweight planning deliverables. Also triggers on "create tasks from this problem", "make this actionable", or "turn this into a plan agents can execute". For feature-sized work that needs an executable spec + constitution + cross-check gate, route to `spec-driven-development` (or `feature-spec`) instead.
日本語の概要は準備中です。原文の説明を表示しています。