1.4万 件 ・ 関連度順
Use when the user needs to find, prioritize, or engage B2B prospects — defining an ICP, tiering accounts, building or enriching lists, reading buying signals, designing multi-channel cadences, cold calling, LinkedIn outreach, routing inbound leads, or diagnosing weak pipeline generation. Also for live prospecting coaching. Not for closing (use sales-skill), copy (use copywriter-skill), or CAC analysis (use channel-expert).
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to get found in Google or AI engines (ChatGPT, Perplexity, AI Overviews) — keyword and content strategy, technical or content SEO audits, schema markup, link building, topical clustering, E-E-A-T, AI citation (AEO), or deciding whether SEO is even the right channel for their startup. Calibrated for early-stage, low-authority sites. Not for paid acquisition or channel-mix/CAC analysis (use channel-expert), or writing the page copy itself (use copywriter-skill).
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user is working a B2B SaaS deal from qualified opportunity to closed-won — preparing discovery calls, structuring demos or POCs, handling a specific objection, qualifying with MEDDIC/MEDDPICC/SPICED, building mutual action plans, navigating negotiation or procurement, or reviewing pipeline health, forecast accuracy, and deal velocity. Not for finding or prospecting new leads (use prospecting) or upstream positioning (use product-position).
日本語の概要は準備中です。原文の説明を表示しています。
Use when a non-designer needs to audit a UI, generate a design spec (spacing, type scale, color tokens, grids), or build brand foundations (logo systems, palette and type pairing, brand guidelines). Covers the visual layer, UX/perceptual critique, and brand identity. For implementing the design in code (React/HTML/CSS), use frontend-design.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user needs to scope, write, or audit a product spec — a PRD, feature spec, user stories, acceptance criteria, or a "spec this out"/"break this into stories"/"definition of done" request — or wants an existing spec reviewed for gaps and anti-patterns. Triggers whenever a feature idea needs to become structured requirements that align a team on what to build. For the analytics behind success metrics, use data-analysis; for the technical design, use software-architect.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate complex development with AUTOMATIC parallel subagent execution, continuous dispatch scheduling, dependency analysis, file conflict detection, and IOSM quality gates. Analyzes task dependencies, builds critical path, launches parallel background workers with lock management, monitors progress, auto-spawns from discoveries. Use for multi-file features, parallel implementation streams, automated task decomposition, brownfield refactoring, or when user mentions "parallel agents", "orchestrate", "swarm", "continuous dispatch", "automatic scheduling", "PRD", "quality gates", "decompose work", "Mixed/brownfield".
日本語の概要は準備中です。原文の説明を表示しています。
Use when building Linux servers with liburing, batching SQEs, multi-shot operations, provided buffer rings, registered files and buffers, or zero-copy send. Not for packet I/O: use af-xdp.
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing bytecode dispatch loops, choosing stack or register VM shapes, adding inline caches, or building a first JIT with mmap. Not for a language toolchain: use compiler-frontend.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing loadable kernel modules: Kbuild, module parameters, proc and sysfs entries, char devices, or ftrace debugging. Not for driver architecture: use device-drivers.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing or debugging Makefiles, understanding pattern rules and automatic dependency generation, managing CFLAGS/LDFLAGS, or diagnosing incremental build, phony targets, or recursive make.
日本語の概要は準備中です。原文の説明を表示しています。
Use when studying Intel VT-x or AMD-V internals: VMCS and VMCB, EPT and NPT, VM exit handling, APIC virtualization, or building a minimal type-1 hypervisor. Not for running VMs: use qemu-kvm.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a C or C++ build uses clang and needs diagnostics, optimization remarks, clang-tidy, ThinLTO with lld, LLVM PGO, or a GCC-to-Clang migration. Not for LLVM IR work: use llvm.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing Bazel BUILD files with cc_library or cc_binary rules, Bzlmod dependencies, toolchain registration, remote execution, sandbox debugging, or bazel query and cquery graphs.
日本語の概要は準備中です。原文の説明を表示しています。
Use when evaluating Carbon for a C++ code base, running the carbon toolchain from a nightly or Bazel build, or comparing Carbon with staying on C++. Not for C++ modules: use cpp-modules.
日本語の概要は準備中です。原文の説明を表示しています。
Use when building static archives with ar, stripping or converting binaries, mapping crash addresses with addr2line, or demangling C++ symbols. Not for ELF analysis: use elf-inspection.
日本語の概要は準備中です。原文の説明を表示しています。
Use when managing Cargo workspaces, feature flags, build scripts, CI caching, dependency auditing, or Cargo.lock with Rust.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing CMakeLists.txt, out-of-source builds, target_link_libraries, target properties, find_package/FetchContent, toolchain files, CPack, CMake presets, or cmake configure errors.
日本語の概要は準備中です。原文の説明を表示しています。
Use when building a lexer, Pratt or recursive-descent parser, AST, symbol table, type checker, or LLVM IR emitter for a language or DSL. Not for optimizing IR: use llvm-passes.
日本語の概要は準備中です。原文の説明を表示しています。
Use when C code is written or audited and needs a pure-C baseline: standard, undefined behavior, integer and buffer safety, sanitizers, fuzzing, build flags. Not for C++: use modern-cpp-practices.
日本語の概要は準備中です。原文の説明を表示しています。
Use when explaining or building on Linux container primitives: namespaces, cgroups v2, overlayfs, runc and the OCI spec, seccomp-bpf, capabilities, or escapes. Not for VM isolation: use qemu-kvm.
日本語の概要は準備中です。原文の説明を表示しています。
Use when work reaches a session boundary or the user asks to hand off, delegate, or get a clipboard-ready prompt. Mode brief packages continuity; mode prompt builds the delegation prompt.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to build, run, or triage a coverage-guided C/C++ fuzz campaign on the libFuzzer or AFL++ engine. Not for harness design: use fuzz-harness-writing.
日本語の概要は準備中です。原文の説明を表示しています。
Use when directing, building, or auditing React/Next.js Tailwind UI: visual direction, responsive/dark-mode retrofits, UX audits. Not for typography or motion: use typography-audit or ui-animation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to build spring, easing, gesture, and choreographed animations with correct physics and reduced-motion support. Not for auditing existing motion or finding animation opportunities.
日本語の概要は準備中です。原文の説明を表示しています。