1,398 件 ・ 関連度順
概要と使いどころ
Research competitor paid-ad presence, messaging, creative, formats, landing pages, keyword and auction signals, transparent ad libraries, and strategic gaps across supported platforms. Use for competitor ads, ad libraries, ad spy, competitive PPC analysis, competitor creative, Google Ads Transparency, Meta Ad Library, or paid-media competitor research.
日本語の概要は準備中です。原文の説明を表示しています。
Detect null/undefined/empty handling gaps where callers or consumers may receive unexpected nullish values.
日本語の概要は準備中です。原文の説明を表示しています。
Find missing tests for critical paths, edge cases, and failure handling in changed code.
日本語の概要は準備中です。原文の説明を表示しています。
Detect breaking API contract changes, DTO modifications without compatibility handling, and missing tests for changed API boundaries.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze a script or existing edit, identify visual gaps, and generate supplemental B-roll coverage with clear parent and factual-status labels.
日本語の概要は準備中です。原文の説明を表示しています。
Use when evaluating, critiquing, transforming, or generating a Master's Informatics thesis idea, research gap, novelty, research question, experiment, AI/ML/CV/NLP/LLM/Edge-AI method, or when distinguishing R&D research from software implementation using the Frascati Manual 2015.
日本語の概要は準備中です。原文の説明を表示しています。
Self-verification loop. After completing a task, re-read the original request, list each requirement, verify whether it was met, and fix gaps before stopping.
日本語の概要は準備中です。原文の説明を表示しています。
Handle NULL values and set default values for missing fields in collections and materializations. Use when fields need defaults, nullable primary key errors occur, or source data has gaps. Use when user says "NULL values", "default value", "missing field", "nullable primary key error", or "fill in missing data".
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate any tdmcp test-coverage work: run the coverage harness, inspect coverage gaps, plan focused Vitest/msw or bridge tests, delegate coverage writers, verify coverage deltas, and re-run gates. Use whenever the user asks to raise coverage, add broad regression coverage, create a test harness, improve tests, re-run a coverage wave, or fix a coverage gate.
日本語の概要は準備中です。原文の説明を表示しています。
Build comprehensive attack trees to visualize threat paths. Use when mapping attack scenarios, identifying defense gaps, or communicating security risks to stakeholders.
日本語の概要は準備中です。原文の説明を表示しています。
Scoring rubrics for all 5 pipeline layers (Vision, Architecture, IA, BE, FE). Use when auditing specs, running self-checks, or remediating ambiguity gaps.
日本語の概要は準備中です。原文の説明を表示しています。
Structured methodology for adversarial thinking — generating attack scenarios, abuse cases, race conditions, and security edge cases against specs and implementations. Produces spec-level gap items, not code-level fixes.
日本語の概要は準備中です。原文の説明を表示しています。
Senior Kotlin specialist code review — framework-agnostic. Use whenever the user asks to review, audit, critique, or get feedback on Kotlin code, a file, a class, a function, a module, a diff, a branch, a commit, or a pull request. Judges Kotlin language idioms, logic correctness, architecture and layering, concurrency (coroutines, Flow, structured concurrency, cancellation, race conditions), null safety, exception safety, testability, performance, and security. Detects force-unwraps, unchecked casts, GlobalScope, leaked mutability, broken structured concurrency, hidden side effects, weak abstractions, untestable seams, allocation hot spots, weak crypto, input-validation gaps, and PII logging. Outputs prioritized findings with file:line anchors and minimal-diff fixes. No assumptions about DI framework, UI framework, or build system.
日本語の概要は準備中です。原文の説明を表示しています。
Smart Kotlin unit testing with auto-detection, coverage analysis, and AI edge cases. Use when generating tests for biz/ layer classes, analyzing test coverage gaps, or discovering edge cases.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Codeowners — cODEOWNERS file management covering ownership mapping analysis, coverage gap detection, team assignment validation, orphaned path identification, and review requirement auditing. Use when auditing code ownership across repositories, identifying unowned code paths, validating team configurations, or optimizing pull request review workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Claw Mar 23, 2026 Comparison 15 min min read OpenClaw vs Other AI Agent Frameworks - Comprehensive C GAP: agent framework / orchestrator SDK: competit
日本語の概要は準備中です。原文の説明を表示しています。
PVDetector, a training-free framework that detects PI attacks during LLM inference by measuring hidd GAP: no mappable capability in latest signal (our
日本語の概要は準備中です。原文の説明を表示しています。
Symbolic Guardrails for Domain-Specific Agents: Stronger … — 16. Apr. 2026 · We study symbolic guard GAP: OpenHands has a modular SDK design — our too
日本語の概要は準備中です。原文の説明を表示しています。
We need to find the structural connection between the two described situations. The user gave two bu GAP: OpenHands has a modular SDK design — our too
日本語の概要は準備中です。原文の説明を表示しています。
[TOOL_RESULT:web_search] {"results": "Why Most AI Systems Fail at Scale: Problem faced with … :: 12. GAP: OpenHands has a modular SDK design — our too
日本語の概要は準備中です。原文の説明を表示しています。
Consciousness and AI — OECS — 5. Feb. 2026 · Whether AI consciousness is possible depends on what pr GAP: OpenHands has a modular SDK design — our too
日本語の概要は準備中です。原文の説明を表示しています。
With this cross-journal Collection, the editors at Nature Communications , Communications Psychology GAP: no mappable capability in latest signal (our
日本語の概要は準備中です。原文の説明を表示しています。
Hierarchical, Hybrid, and Omnimodal Models Jun 30 58 m Jun 30, 2026 58 m read Show 10 25 50 100 pe GAP: no mappable capability in latest signal (our t
日本語の概要は準備中です。原文の説明を表示しています。
This work studies the post-training quantization of LLM parameters as a way to improve their runtime GAP: multi-agent orchestration: competitor signal
日本語の概要は準備中です。原文の説明を表示しています。