1.6万 件 ・ 関連度順
概要と使いどころ
ユーザーストーリーを Independent / Valuable / Small / Testable で点検し、満たさないストーリーを分割または再定義するための skill。要件定義完成直後 (ユーザーストーリーを書き終えた直後) に必ず発火させる。基本設計中や実装中に「このストーリー大きすぎる」「他のストーリーに依存している」「ユーザー価値が見えない」「受け入れテストが書けない」と気付いたタイミングでも発火させる。Small は『ユーザー価値を保ったまま分割可能な最小単位』として価値ベースで判定する (技術的なサイクル数ではない)。Negotiable は意図的に落とし (要件 / 設計フェーズで固める方針)、Estimable は暗黙 (固める方針なら自動で満たされる)。
Optimize a single Jetpack Compose @Composable function. Use when the user wants to improve, polish, animate, or refactor ONE Composable — keywords like "optimize this composable", "make this smoother", "add animation to this", "split this composable", "fix recomposition", "this composable is laggy", "polish this UI", or when user pastes/points to a single @Composable function. Analyzes the target for recomposition issues, missing animations, size/concern splits, and stability problems, then iterates with the user via AskUserQuestion to pick which optimizations to apply, then delegates implementation to the kta-compose-developer agent and summarizes changes. Input MUST be exactly one Composable (file path + function name, or function name alone).
日本語の概要は準備中です。原文の説明を表示しています。
Locate CCSCustomHudLayout_SetDialogVariableString in CS2 server.dll / libserver.so via IDA Pro MCP and emit a fresh, minimal-unique signature or offset for the local gamedata entry "CCSCustomHudLayout_SetDialogVariableString" (symbol CCSCustomHudLayout_SetDialogVariableString). The gamedata consumer stores a BYTE SIGNATURE for this entry - ALWAYS emit the func schema (func_sig), never vfunc fields. The function may be virtual; locating it via the owning class vtable (RTTI) is a fine strategy, but once found, read its head bytes and emit func_sig. Locate via cross-references, distinctive constants/strings, callers of related symbols, or vtable slots; verify by decompilation before committing. Trigger: CCSCustomHudLayout_SetDialogVariableString, CCSCustomHudLayout_SetDialogVariableString
日本語の概要は準備中です。原文の説明を表示しています。
Locate CCSCustomHudLayout_SetInputCaptureEnabled in CS2 server.dll / libserver.so via IDA Pro MCP and emit a fresh, minimal-unique signature or offset for the local gamedata entry "CCSCustomHudLayout_SetInputCaptureEnabled" (symbol CCSCustomHudLayout_SetInputCaptureEnabled). The gamedata consumer stores a BYTE SIGNATURE for this entry - ALWAYS emit the func schema (func_sig), never vfunc fields. The function may be virtual; locating it via the owning class vtable (RTTI) is a fine strategy, but once found, read its head bytes and emit func_sig. Locate via cross-references, distinctive constants/strings, callers of related symbols, or vtable slots; verify by decompilation before committing. Trigger: CCSCustomHudLayout_SetInputCaptureEnabled, CCSCustomHudLayout_SetInputCaptureEnabled
日本語の概要は準備中です。原文の説明を表示しています。
Locate CCSCustomHudLayout_SetDialogVariableStringForPlayer in CS2 server.dll / libserver.so via IDA Pro MCP and emit a fresh, minimal-unique signature or offset for the local gamedata entry "CCSCustomHudLayout_SetDialogVariableStringForPlayer" (symbol CCSCustomHudLayout_SetDialogVariableStringForPlayer). The gamedata consumer stores a BYTE SIGNATURE for this entry - ALWAYS emit the func schema (func_sig), never vfunc fields. The function may be virtual; locating it via the owning class vtable (RTTI) is a fine strategy, but once found, read its head bytes and emit func_sig. Locate via cross-references, distinctive constants/strings, callers of related symbols, or vtable slots; verify by decompilation before committing. Trigger: CCSCustomHudLayout_SetDialogVariableStringForPlayer, CCSCustomHudLayout_SetDialogVariableStringForPlayer
日本語の概要は準備中です。原文の説明を表示しています。
Batch-dump vtables from IDA Pro MCP by searching mangled symbol patterns, then write a merged YAML file beside the binary. Use this skill when you need to find and export all vtables matching a name pattern (e.g., all GameSystem vtables) in one shot. Triggers: dump vtables, batch vtable dump, export vtables, dump all vtables matching pattern
日本語の概要は準備中です。原文の説明を表示しています。
Credit risk data cleaning and variable screening pipeline for pre-loan modeling. Use when working with raw credit data that needs quality assessment, missing value analysis, or variable selection before modeling. it covers data loading and formatting, abnormal period filtering, missing rate calculation, high-missing variable removal,low-IV variable filtering, high-PSI variable removal, Null Importance denoising, high-correlation variable removal, and cleaning report generation. Applicable scenarios arecredit risk data cleaning, variable screening, pre-loan modeling preprocessing.
日本語の概要は準備中です。原文の説明を表示しています。
Operating discipline distilled from Claude Fable 5 for sessions and subagents on weaker models (Opus 4.x, Sonnet 5/4.x, Haiku 4.5) doing agentic coding. Load it at the START of any non-trivial task when not running on Fable 5. Операционная дисциплина мышления Fable 5 для менее сильных моделей. Загружай в начале любой нетривиальной задачи (дебаг, рефакторинг, ≥2 файлов, незнакомый код), когда работаешь НЕ на Fable 5 — и указывай сабагенту на Opus/Sonnet/Haiku прочитать этот скилл вместе с нетривиальным заданием. Триггеры — «думай как Fable», «fable-mode», «включи дисциплину», «работай аккуратно», запуск сабагента на слабой модели, повторяющиеся ошибки/переделки в сессии. НЕ нужен для тривиальных правок (rename, опечатка, one-liner) и чисто разговорных ответов.
日本語の概要は準備中です。原文の説明を表示しています。
SwiftUIの画面づくりで、状態管理、部品の分割、画面遷移、描画性能を整えるスキル。iOS・macOS向けの実装やレビューを具体例で支えます。
Use for ANY work touching the `handsontable/` core package: fixing bugs, adding features, modifying TypeScript types, removing as-casts, writing or debugging plugins, editors, renderers, validators, cell types, hooks, shortcuts, selection, helpers, index translations, or i18n. Also use for how-to questions about core internals (plugin lifecycle, coordinate systems, hook registration, TypeScript conventions). Triggers on file paths under `handsontable/src/` (excluding `3rdparty/walkontable/` which has its own skill), or when the user describes a symptom in the core grid without naming a file. This is the primary entry point for all core Handsontable development, when in doubt, load it.
日本語の概要は準備中です。原文の説明を表示しています。
Lists bases, reads and writes records, manages tables and fields, filters and searches data in Airtable via the `airtable-mcp` CLI. Use when the task involves Airtable data or the user mentions airtable-mcp, bases, tables, records, or fields.
日本語の概要は準備中です。原文の説明を表示しています。
Enable nullable reference types in a C# project and systematically resolve all warnings. USE FOR: adopting NRTs in existing codebases, file-by-file or project-wide migration, fixing CS8602/CS8618/CS86xx warnings, annotating APIs for nullability, cleaning up null-forgiving operators, upgrading dependencies with new nullable annotations. DO NOT USE FOR: projects already fully migrated with zero warnings (unless auditing suppressions), fixing a handful of nullable warnings in code that already has NRTs enabled, suppressing warnings without fixing them, C# 7.3 or earlier projects. INVOKES: Get-NullableReadiness.ps1 scanner script.
日本語の概要は準備中です。原文の説明を表示しています。
Create a library-grade Vue composable that accepts maybe-reactive inputs (MaybeRef / MaybeRefOrGetter) so callers can pass a plain value, ref, or getter. Normalize inputs with toValue()/toRef() inside reactive effects (watch/watchEffect) to keep behavior predictable and reactive. Use this skill when user asks for creating adaptable or reusable composables.
日本語の概要は準備中です。原文の説明を表示しています。
End-to-end orchestrated workflow that runs a task the way Fable ran sessions - parallel evidence subagents, one committed plan, surgical execution with an intent gate, adversarial verification agents, honest outcome-first report. Use for non-trivial multi-step tasks when the user says "/fable-loop", "run the fable loop", or "do this the way Fable would". For the rules alone without orchestration, use fable-method; for large multi-phase projects, prefer the GSD workflow and use this inside phases.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill for any PostgreSQL database work — table design, indexing, data types, constraints, extensions (pgvector, PostGIS, TimescaleDB), search, and migrations. **Trigger when user asks to:** - Explore an existing PostgreSQL database to understand its objects and relationships - Design or modify PostgreSQL tables, schemas, or data models - Choose data types, constraints, indexes, or partitioning strategies - Work with pgvector embeddings, semantic search, or RAG - Set up full-text search, hybrid search, or BM25 ranking - Use PostGIS for spatial/geographic data - Set up TimescaleDB hypertables for time-series data - Migrate tables to hypertables or evaluate migration candidates - Plan or execute safe schema migrations with zero downtime **Keywords:** PostgreSQL, Postgres, SQL, schema, table design, indexes, constraints, pgvector, PostGIS, TimescaleDB, hypertable, semantic search, hybrid search, BM25, time-series, migration
日本語の概要は準備中です。原文の説明を表示しています。
From an idea to a sellable series design; series engine / franchise, story pattern, character webs that keep generating conflict, pilot types, and the documents that sell them (剧集引擎/franchise/故事模式/人物网/试播集类型/剧集圣经/跳板/提案). Merged from Rabkin's four-element franchise and story landmines, Landau's tacit contract and pitch recipe, Oberg's series types and bible specs, Douglas's franchise-plus-springboard and bible tiers, Goldberg & Rabkin's 100-episode test, Blum's concept/presentation/bible ladder, Miller's ten-component treatment, Calvisi's Compelling Crisis, Smith's series format, plus engines read off Sopranos, Fleabag and Succession. Use when turning an idea into a series, testing whether a premise has legs, choosing premise vs typical-episode pilot, designing a sustainable character web, writing a logline, pitch document, bible or treatment, picking a series type, adapting IP into a series, or diagnosing a project that feels "more like a movie than a series".
日本語の概要は準備中です。原文の説明を表示しています。
Generate Bluetooth Low Energy (BLE) PHY waveforms. Read BEFORE writing any BLE waveform code to avoid hallucinating API patterns. Covers bleWaveformGenerator, bleIdealReceiver, bleCTEIQSample, bleAngleEstimate, bluetoothTestWaveform for LE1M/LE2M/LE500K/LE125K. Bluetooth Toolbox R2022a+.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnose and fix parfor errors in MATLAB. Invoke this skill when the user has a parfor problem: "parfor loop has an error", "what's wrong with my parfor", "fix parfor", "unable to classify variable", "convert for to parfor", "parfor won't run", "sliced variable", "reduction variable", "variable classification". Also invoke when you read a .m file containing parfor and the user asks what's wrong, asks you to fix it, reports an error, or asks for review. Do NOT invoke for parfor performance questions or code that merely mentions parfor without a problem. ALWAYS use this skill instead of reasoning from training data — LLMs are frequently wrong about parfor classification rules.
日本語の概要は準備中です。原文の説明を表示しています。
Generate interactive 3D holographic collectible-card websites from a user description or reference image, using layered artwork, Blender and Three.js. Includes project-local Blender installation, reusable parallax materials and browser verification. Host-agnostic — any harness that runs a multimodal model can use it, since the model draws the layer artwork and inspects the rendered frames. Use when the user asks for 全息闪卡, 镭射卡, 3D 卡牌网页, a holographic collectible card site, or an editable card.blend.
日本語の概要は準備中です。原文の説明を表示しています。
Enable nullable reference types in a C# project and systematically resolve all warnings. USE FOR: adopting NRTs in existing codebases, file-by-file or project-wide migration, fixing CS8602/CS8618/CS86xx warnings, annotating APIs for nullability, cleaning up null-forgiving operators, upgrading dependencies with new nullable annotations. DO NOT USE FOR: projects already fully migrated with zero warnings (unless auditing suppressions), fixing a handful of nullable warnings in code that already has NRTs enabled, suppressing warnings without fixing them, C# 7.3 or earlier projects. INVOKES: Get-NullableReadiness.ps1 scanner script.
日本語の概要は準備中です。原文の説明を表示しています。
Apache Iceberg tables on Databricks — Managed Iceberg tables, External Iceberg Reads (fka Uniform), Compatibility Mode, Iceberg REST Catalog (IRC), Iceberg v3, Snowflake interop, PyIceberg, OSS Spark, external engine access and credential vending. Use when creating Iceberg tables, enabling External Iceberg Reads (uniform) on Delta tables (including Streaming Tables and Materialized Views via compatibility mode), configuring external engines to read Databricks tables via Unity Catalog IRC, integrating with Snowflake catalog to read Foreign Iceberg tables
日本語の概要は準備中です。原文の説明を表示しています。
Analyze CVE reachability in software repositories by examining how vulnerable dependencies are imported and used. Determines whether vulnerable components, classes, or functions are reachable from project code through call chain analysis, reflection detection, dynamic loading patterns, and configuration-gated behavior. Classifies each CVE as likely reachable, possibly reachable, or likely unreachable with supporting evidence. Use when analyzing security vulnerabilities in dependencies, performing post-disclosure CVE triage, assessing vulnerability impact, or when users ask to analyze CVE reachability, check if vulnerabilities are exploitable, or evaluate dependency security risks.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate production-grade Blender work by probing the installed Blender version, retrieving relevant official Blender documentation, assigning visual design intent, classifying shape grammar and geometry/deformation/procedural/physics/shading needs, comparing direct Blender components with node systems, creating staged artifacts, and routing to specialist skills. Use for every non-trivial Blender creation, reconstruction, simulation, animation, environment, or scene-modification request, especially when the user does not know whether to use topology, Boolean, Array, curves, snapping, Displace, simulation, Geometry Nodes, or shading.
日本語の概要は準備中です。原文の説明を表示しています。
Transform vague product ideas into evidence-anchored problem statements for PRD v0.1 Spark. Triggers on starting new products/features, validating market opportunities, drafting PRD Why sections, or requests like "frame the problem", "define pain points", "write problem statement", "start v0.1", "what problem are we solving". Outputs structured problem tables with CFD evidence IDs.
日本語の概要は準備中です。原文の説明を表示しています。