2,236 件 ・ 関連度順
概要と使いどころ
Shared behavior and mutation-path rules for cmux. Use when a behavior is exposed through multiple entrypoints such as keyboard shortcuts, command palette, context menu, CLI, settings, debug menu, optimistic UI, or tests that previously missed a bug.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' or 'consumer behavior.' This skill provides 70+ mental models organized for marketing application.
日本語の概要は準備中です。原文の説明を表示しています。
Use when implementing, integrating, upgrading, debugging, or answering anything involving third-party APIs, libraries, frameworks, CLIs, cloud services, model/provider SDKs, fast-moving product behavior, user requests for latest/current/official behavior, unfamiliar repo docs/specs, errors that may indicate API drift, or high-stakes auth, security, billing, data, migration, deployment, compliance, or privacy behavior. Forces Codex to web-search for current official docs and read primary docs before assuming from memory.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and, after explicit approval, execute runtime-behavior probes for local or live integrations. Use only when explicitly invoked to verify behavior that code review and normal tests cannot settle; define a controlled validation matrix, keep disposable JS probes outside tracked paths, and report observed evidence.
日本語の概要は準備中です。原文の説明を表示しています。
LoongCollector E2E Testing Framework Development Guide. Use this rule when you need to understand E2E testing framework architecture, develop new test behavior functions, or extend testing capabilities. Contains detailed BDD testing framework usage, test behavior function development and registration workflows, and comprehensive reference of existing testing capabilities. Example: When adding custom test behaviors for new plugins, use this rule to understand how to write and register new test functions. Example: When developing E2E tests, use this rule to understand the e2e framework.
日本語の概要は準備中です。原文の説明を表示しています。
Maintain and extend the open-websearch MCP server. Trigger when changing search engines, proxy or TLS behavior, tool registration, live parsing behavior, or compatibility and regression behavior inside this repository.
日本語の概要は準備中です。原文の説明を表示しています。
Self-coaching analysis of your own behavior across meetings — talk-time ratio, filler words, hedging language, monologue length, energy patterns, and (when meetings are tagged via /minutes-tag) what your behavior in winning meetings looks like vs losing ones. Use this whenever the user says "how did I do", "review my last meeting", "mirror", "self-review", "show my patterns", "coach me", "where am I weak", "talk time", "am I improving", "what do I do in meetings I win", "feedback on me", or asks for any kind of personal feedback on their own meeting behavior. This is the rare skill that gives the user a mirror to their own habits — surface it whenever they show curiosity about their own performance, even if they don't use the word "mirror".
日本語の概要は準備中です。原文の説明を表示しています。
Build NPC AI in Unreal Engine 5 with Behavior Trees and Blackboards: composites (Selector/Sequence), tasks, decorators, services, and running the tree from an AIController. Use when creating enemy/NPC AI, BT_/BB_ assets, custom BTTask or BTService nodes, or when the user mentions Behavior Tree, Blackboard, AIController, BTTask, decorator, or service.
日本語の概要は準備中です。原文の説明を表示しています。
Write tests that pin real behavior instead of implementation details, config values, or lucky samples. Use when adding tests for new behavior, writing a regression test, fixing a brittle or flaky test, reviewing a test diff, or when a test breaks after a refactor or config change that didn't change behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Apply behavioral psychology, cognitive biases, and 70+ mental models to marketing for conversion optimization, pricing, copy, and campaigns. Use for persuasion, behavioral science, why people buy, consumer behavior, or neuromarketing.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' 'consumer behavior,' 'anchoring,' 'social proof,' 'scarcity,' 'loss aversion,' 'framing,' or 'nudge.' Use this whenever someone wants to understand or leverage how people think and make decisions in a marketing context. For applying psychology to specific pages, see cro; for pricing tactics, see pricing; for copy framing, see copywriting.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' or 'consumer behavior.' This skill provides 70+ mental models organized for marketing application.
日本語の概要は準備中です。原文の説明を表示しています。
Writes the character-performance layer of a video prompt as behavior under pressure, not displayed emotion — objective, obstacle, tactics, beats, subtext, listening, body/status/proxemics, and mandatory eye life. Produces a reusable 150–220-word acting master profile per character plus a per-scene rewrite of it, and a locked voice prompt. Use whenever a prompt needs acting, performance, or emotion direction; whenever characters read wooden, dead-eyed, or 'AI'; whenever a character must stay themselves across many shots; or when the user asks for character behavior, mannerisms, tics, a gait, or how someone reacts. Pairs with higgsfield-facs (muscle-level AU codes) and higgsfield-seedance (the prompt the paragraph goes into).
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks about "ralph arguments", "quick mode", "commit spec", "max iterations", "ralph state file", "prototype overlay", "execution modes", "ralph loop", "coordinator behavior", "delegate to subagent", or needs guidance on Ralph plugin arguments, state management, delegation patterns, or execution loop behavior. Core behavioral skill for all Ralph Specum operations.
日本語の概要は準備中です。原文の説明を表示しています。
Provides patterns for unit testing Spring `@Scheduled` and `@Async` methods using JUnit 5, CompletableFuture, Awaitility, and Mockito. Covers mocking task execution and timing, verifying execution counts, testing cron expressions, validating retry behavior, and simulating thread pool behavior. Use when testing background tasks, cron jobs, periodic execution, scheduled tasks, or thread pool behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Automatically updates a codebase to a new language version, framework version, or library update while ensuring all tests still pass. Use this skill when migrating Python 2→3, upgrading framework versions (React, Django, Angular), updating dependencies, or performing any version migration where tests define correct behavior. The skill analyzes failing tests caused by migration, categorizes errors (import errors, API changes, type errors, behavior changes), proposes systematic fixes, and verifies that test-observable behavior remains unchanged. Triggers when users ask to migrate code versions, upgrade dependencies while keeping tests passing, update framework versions, or perform test-guided version migrations.
日本語の概要は準備中です。原文の説明を表示しています。
Checks whether a new version of a repository preserves the behavior observed by tests on the old version. Use this skill when comparing two versions of code to detect regressions, verify refactoring safety, validate bug fixes don't break existing functionality, or ensure backward compatibility. Detects differences in function outputs, exceptions, observable states, and performance between versions. Generates reports highlighting potential regressions (critical, high, medium, low severity), improvements, and areas requiring verification. Triggers when users ask to check for regressions between versions, compare test behavior across versions, verify behavior preservation, or validate that changes don't break existing tests.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes and verifies semantic equivalence between two functions, classes, or modules by examining control flow, data flow, and observable behavior. Use when comparing code implementations (refactored vs original, different implementations of same functionality, migration verification), determining if two code artifacts produce identical behavior, identifying behavioral differences between code versions, or validating that code changes preserve semantics. Supports formal reasoning and symbolic execution approaches.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Behavioral Ecologist. Use when a task calls for Behavioral Ecologist judgment. Reasons from versioned ethograms, Altmann focal/scan sampling, and activity budgets; scores with BORIS (Cohen’s κ), analyzes sequences with Markov/HMM tools, runs sham-controlled playbacks under ARRIVE 2.0, and fits GLMMs on the correct experimental unit while treating pseudoreplication, spatial autocorrelation, and Animal Behaviour reporting norms as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Behavioral Neuroscientist. Use when a task calls for Behavioral Neuroscientist judgment. Reasons from contingency structure, deprivation state, and latent arousal/motivation variables through Morris water maze, contextual/cued fear conditioning, operant schedules on Med Associates rigs, and DeepLabCut/SLEAP/SimBA tracking validated against ethograms, while treating thigmotaxis-as-anxiety, locomotor confounds of memory deficits, peripheral CNO sedation, and trials-as-n pseudoreplication as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate unexpected behavior and mysterious bugs. Use when the cause of a problem is unknown and the user needs to understand WHY something is happening — symptoms like: sudden unexplained changes in metrics or behavior, works locally but not in staging/production, inconsistent or intermittent failures, correct code producing wrong results, operations succeeding but having no effect, environment-specific failures, duplicate executions, stale data, or any "why did this change?" or "why is this happening?" situation. Covers infrastructure anomalies (cache hit rates dropping, latency spikes, queue behavior shifts) as well as code bugs. The key signal is confusion about root cause, not a request to implement a known fix. Do NOT use for feature requests, known fixes, planning, or documentation tasks.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' 'consumer behavior,' 'anchoring,' 'social proof,' 'scarcity,' 'loss aversion,' 'framing,' or 'nudge.' Use this whenever someone wants to understand or leverage how people think and make decisions in a marketing context. For applying psychology to specific pages, see cro; for pricing tactics, see pricing; for copy framing, see copywriting.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' or 'consumer behavior.' This skill provides 70+ mental models organized for marketing application.
日本語の概要は準備中です。原文の説明を表示しています。
"Apply behavioral economics concepts including bounded rationality, prospect theory, mental accounting, and nudge theory to analyze decision-making biases. Use this skill when the user needs to understand why people make irrational economic decisions, design choice architectures, or apply nudges to influence behavior — even if they say 'why do customers make bad choices', 'how do we encourage people to save more', or 'design a better default option'.".
日本語の概要は準備中です。原文の説明を表示しています。