Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation.
日本語の概要は準備中です。原文の説明を表示しています。
1,216 件 ・ 関連度順
概要と使いどころ
Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation.
日本語の概要は準備中です。原文の説明を表示しています。
세션 변경사항을 분석하여 검증 스킬 누락을 탐지합니다. 기존 스킬을 동적으로 탐색하고, 새 스킬을 생성하거나 기존 스킬을 업데이트한 뒤 프로젝트 CLAUDE.md를 관리합니다.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze session work and automatically convert reusable patterns into Claude Code skills. Use when: "세션을 스킬로", "스킬 만들어", "이거 스킬로", "skill factory", "이 작업 자동화해", "스킬 추출", "make this a skill", "extract skill", "convert to skill", "스킬 팩토리", "자동 스킬 생성". Differs from skill-creator (archived) and manage-skills (drift detection): this skill actively analyzes sessions, checks for duplicates, and creates skills via Agent Teams.
日本語の概要は準備中です。原文の説明を表示しています。
Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance issues, or unexpected behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Use when orchestrating Agent Teams for parallel development - team composition, task distribution, dependency management, and result aggregation. Triggers on /orchestrate, multi-agent coordination, parallel team work, task delegation to teammates.
日本語の概要は準備中です。原文の説明を表示しています。
Use when verifying build/test/lint before commit, PR, or completion claims. Runs verification pipeline in fresh subagent context with auto-repair. Triggers on /handoff-verify, pre-commit check, build verification, test validation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
日本語の概要は準備中です。原文の説明を表示しています。
Structured debugging methodology — use before proposing fixes for any error or failure. Covers: code bugs, build errors, deploy failures, config conflicts, dependency issues, infra problems. Also use when previous fix attempts failed or root cause is unclear.
日本語の概要は準備中です。原文の説明を表示しています。
Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.
日本語の概要は準備中です。原文の説明を表示しています。
Design a spaced retrieval schedule for any topic list and timeline. Use when planning units, term sequences, or revision programmes.
日本語の概要は準備中です。原文の説明を表示しています。
Generate, simulate, audit, and deploy a Uniswap v4 hook + test pool from a brief, on any Uniswap v4 chain (every testnet and mainnet) - pre-audited templates or a from-scratch freeform hook (flags auto-derived; static audit + dangerous-pattern scan + a behavioral forge test + fork sim gate the deploy). Dry-run by default; explicit arm: to broadcast; testnet default, mainnet behind a double opt-in; records the deploy to main. Every deployed hook inherits a mandatory 10 bps AeonFee protocol fee.
日本語の概要は準備中です。原文の説明を表示しています。
Three-mode idea engine - generate collides the week's zeitgeist with what you can ship into scored wedges; validate viability-screens the idea backlog; memo writes evidence-backed startup memos.
日本語の概要は準備中です。原文の説明を表示しています。
Provides guidance for writing, optimizing, and benchmarking Triton kernels for Intel XPU GPUs (Battlemage/Arc Pro B50) using the Xe-Forge optimization framework. Includes an LLM-driven trial-loop workflow (analyze, validate, benchmark, profile, finalize), XPU-specific patterns (tensor descriptors, GRF mode, tile swizzling), KernelBench fused kernels, and Flash Attention.
日本語の概要は準備中です。原文の説明を表示しています。
Design the three states every data UI forgets. Use for any component that fetches or lists data.
日本語の概要は準備中です。原文の説明を表示しています。
Applies the SUCCESs Framework from Made to Stick by Chip Heath and Dan Heath. Use when crafting messages that need to be remembered, writing pitches, creating presentations, designing training materials, telling stories that drive action, or diagnosing why a message isn't landing. The six principles (Simple, Unexpected, Concrete, Credible, Emotional, Stories) diagnose and fix communication failures. Triggers include 'how do I make this memorable', 'my pitch isn't landing', 'people forget what we told them', 'how do I tell a better story', 'our training materials are boring', 'how do I present data compellingly', 'nobody remembers our message', 'how do I get people to care about this', 'my writing is too abstract'. NOT for channel selection (use Traction), not for brand messaging structure (use StoryBrand), not for positioning (use Obviously Awesome).
日本語の概要は準備中です。原文の説明を表示しています。
Deep bug analysis to break the fix-forget-repeat cycle. Analyzes root cause category, why fixes failed, prevention mechanisms, and captures knowledge into specs. Use after fixing a bug to prevent the same class of bugs.
日本語の概要は準備中です。原文の説明を表示しています。
Creates new specialized agents using the 5-phase workflow (ANALYZE > DESIGN > CREATE > VALIDATE > REFINE). Use when building a new AI agent or validating an existing agent specification.
日本語の概要は準備中です。原文の説明を表示しています。
Universal skill diagnosis and optimization tool. Detect and fix skill execution issues including context explosion, long-tail forgetting, data flow disruption, and agent coordination failures. Supports Agy CLI for deep analysis. Triggers on "skill tuning", "tune skill", "skill diagnosis", "optimize skill", "skill debug".
日本語の概要は準備中です。原文の説明を表示しています。
Provides guidance on the new System.Diagnostics.Process APIs introduced in .NET 11: Process.Run, Process.RunAndCaptureText, Process.StartAndForget, Process.ReadAllText/Bytes/Lines, KillOnParentExit, InheritedHandles, and StartDetached. USE FOR: starting, orchestrating, or capturing output from external processes in applications targeting net11.0 or later. DO NOT USE FOR: applications targeting .NET 10 or earlier, or basic pre-.NET 11 Process.Start usage without new APIs.
日本語の概要は準備中です。原文の説明を表示しています。
Build forms, validate data, and react to user input in Blazor. USE FOR adding forms, search boxes, filter panels, inline editing, data-entry UI, file uploads, validation (annotations or custom), handling form submissions, and binding input controls. Covers EditForm, built-in input components, DataAnnotationsValidator, custom validation, SSR form patterns (SupplyParameterFromForm, FormName, AntiforgeryToken, Enhance), and @bind for simple interactive controls. DO NOT USE for project scaffolding (see create-blazor-project) or prerendering issues (see support-prerendering).
日本語の概要は準備中です。原文の説明を表示しています。
Re-detect this project's tech stack from package.json / requirements.txt / pyproject.toml / go.mod / Cargo.toml and diff it against the Tech Stack section of every CLAUDE.md. Read-only — returns added / removed / renamed dependencies, never edits.
日本語の概要は準備中です。原文の説明を表示しています。
Behavioral guardrails for LLM-assisted coding. Use when writing, reviewing, or refactoring code in any project to avoid overcomplication, keep changes surgical, surface assumptions early, and execute against verifiable success criteria.
日本語の概要は準備中です。原文の説明を表示しています。
Verify every @path chain import and every markdown link inside every CLAUDE.md in this project resolves to an existing file. Read-only — returns broken links with file:line refs, never edits.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes, generates, and enhances CLAUDE.md files for any project type using best practices, modular architecture support, and tech stack customization. Use when setting up new projects, improving existing CLAUDE.md files, or establishing AI-assisted development standards.
日本語の概要は準備中です。原文の説明を表示しています。