「behavior」の検索結果

Comprehensive market research and analysis skill. Use when sizing markets, conducting competitive analysis, generating professional market research reports, analyzing consumer behavior, or identifying market opportunities. Activates for: market research, market analysis, market report, TAM SAM SOM, market sizing, industry analysis, market landscape, competitive landscape, market trends, consumer research, Porter's Five Forces, PESTLE, SWOT, BCG Matrix, McKinsey-style report, consulting report, market opportunity, industry report, due diligence, M&A analysis, GTM market analysis, product-market fit validation.

日本語の概要は準備中です。原文の説明を表示しています。

Comprehensive marketing expertise combining campaign execution, strategy frameworks, psychological principles, and 140+ marketing tactics. Use when planning campaigns, developing content strategy, applying behavioral science, generating marketing ideas, or building go-to-market strategies. Covers email, social, SEO, paid ads, content, and psychology-driven optimization.

日本語の概要は準備中です。原文の説明を表示しています。

用户在市场波动中情绪受到影响，或试图从市场价格变动中获取信息而非从企业分析中获取信息时。 语言信号："市场在跌，是不是该卖"/"大家都在买"/"这只股票涨了很多，一定有道理" 不适用于：纯粹的企业基本面分析（不含市场价格判断的场景）。

日本語の概要は準備中です。原文の説明を表示しています。

用户面对市场极端情绪时需要做出逆向来决策。当所有人都在买入/卖出、市场处于极端乐观/悲观时。 语言信号："所有人都在赚钱"/"这次不一样"/"市场要崩了要不要全卖"/"再不买就来不及了" 不适用于：正常市场环境下的投资决策、纯基本面分析。

日本語の概要は準備中です。原文の説明を表示しています。

Browser-check what a change could have broken in timepicker-ui (library demo and docs-app, before/after). Use at the end of a task that changed library behavior or styles (app/src) or docs-app pages, or when the user asks to check that nothing broke. Not for demo examples in app/docs, copy/typo/comment edits or one-line fixes (HARD RULES §5 in CLAUDE.md). Main agent only, never delegated to a subagent.

日本語の概要は準備中です。原文の説明を表示しています。

Use when optimizing, auditing, or preparing to ship web animations or rendering performance work: frame loops, scroll/viewport reveals, mount/unmount transitions, canvas/WebGL lifecycles, reduced motion, lazy rendering, and deferred off-screen work. Use for jank, per-frame allocations, forced reflows, render loops, animations that do not pause off-screen, content-visibility, requestIdleCallback, analyzing Chrome DevTools performance traces for animation or rendering issues, or choosing between browser-driven CSS/WAAPI, minimal JS, phase, and Motion/GSAP. Use when the user explicitly asks about phase APIs or behavior. Do not use during exploratory animation ideation, prototyping, visual iteration, or trying variants, even when the code already imports phase; wait until the user asks for performance guidance, an audit, production implementation, ship-readiness review, or about phase itself.

日本語の概要は準備中です。原文の説明を表示しています。

Designs NUnit-based C# test suites for API, component, and integration coverage. Use when creating fixtures, wiring Testcontainers, or reducing flaky CI behavior.

日本語の概要は準備中です。原文の説明を表示しています。

Implements accessibility fixes in code. Use when remediating semantic HTML, ARIA, focus, keyboard support, or screen-reader behavior.

日本語の概要は準備中です。原文の説明を表示しています。

Designs and audits UI/UX systems with usability and accessibility requirements. Use when shaping flows, design systems, interaction patterns, or WCAG-aware product behavior.

日本語の概要は準備中です。原文の説明を表示しています。

Refactors code while preserving behavior. Use when reducing technical debt, planning codemods, applying strangler migrations, or tightening CI guardrails around risky changes.

日本語の概要は準備中です。原文の説明を表示しています。

Systematic debugging of issues — use when a test fails, runtime error occurs, unexpected behavior is reported, or an awareness tick produces anomalous results

日本語の概要は準備中です。原文の説明を表示しています。

Maps an unfamiliar or large codebase before implementation by locating entry points, ownership, execution paths, conventions, tests, dependencies, change hotspots, and unresolved questions. Use when onboarding to a repository, scoping a cross-cutting change, preparing a handoff or reusable CodeTour, explaining a subsystem, or when the agent is guessing where behavior lives. Not for diagnosing one reproduced failure or designing a new architecture before the current system is understood.

日本語の概要は準備中です。原文の説明を表示しています。

Audits an existing rendered interface or frontend diff for hierarchy, content clarity, interaction states, accessibility, responsive behavior, visual consistency, performance-sensitive UI patterns, and anti-generic design defects. Use for a UI/UX review, redesign audit, screenshot review, pre-release visual check, or design-system consistency pass. Not for building a new interface from scratch or for backend-only review.

日本語の概要は準備中です。原文の説明を表示しています。

Designs or reviews relational, document, key-value, graph, or search data models with ownership, invariants, access paths, migrations, consistency, retention, privacy, and recovery behavior. Use for schema changes, new data stores, indexes, migrations, persistence boundaries, or query-driven design. Not for a query-only bug without a model change or for API contract design.

日本語の概要は準備中です。原文の説明を表示しています。

Investigates a bug, failing test, build error, regression, flaky behavior, performance symptom, or unexpected result by reproducing it, minimizing the case, testing ranked hypotheses, tracing the first incorrect state, and locking the root cause with a regression check. Use before proposing a fix. Not for planning a new feature or reviewing a healthy diff.

日本語の概要は準備中です。原文の説明を表示しています。

Grounds version-sensitive engineering decisions in authoritative current sources by detecting the installed stack, retrieving official documentation or source, reconciling conflicts, and recording citations and confidence. Use for framework APIs, dependency behavior, standards, compatibility, migrations, or technical recommendations that may have changed. Not for stable project-local logic or broad product discovery.

日本語の概要は準備中です。原文の説明を表示しています。

Plans risk-based test coverage for a feature, service, release, or system by mapping user and business risk to test levels, environments, data, failure paths, automation, exploratory checks, and release gates. Use when choosing what to test or how much evidence is enough. Not for writing one test case, applying TDD to a single behavior, or debugging a failing test.

日本語の概要は準備中です。原文の説明を表示しています。

Designs, builds, or refactors user-facing web or application interfaces with deliberate visual direction, typography, color and spacing tokens, content hierarchy, responsive behavior, accessible interaction states, and real rendered-surface verification. Use for pages, components, dashboards, landing pages, design systems, and frontend polish. Not for backend logic, API-only work, or visual claims that cannot be rendered or inspected.

日本語の概要は準備中です。原文の説明を表示しています。

Diagnose HitKeep traffic drops, spikes, source shifts, and suspicious changes. Use when traffic, sessions, visitors, pageviews, events, or conversions changed; when a deploy may have affected measurement or behavior; or when search, referral, direct, campaign, and bot explanations need to be separated.

日本語の概要は準備中です。原文の説明を表示しています。

Maintain HitKeep dashboard localization. Use whenever a contributor adds or changes user-visible dashboard text, Transloco keys, locale JSON files, OptimusUI locale behavior, language switching, translated labels, localized layout, date/number/duration formatting, or supported dashboard languages.

日本語の概要は準備中です。原文の説明を表示しています。

Claude adapter for PlainTab test-first feature work, bug fixes, regression scripts, and behavior-focused validation.

日本語の概要は準備中です。原文の説明を表示しています。

Use when implementing PlainTab features or bug fixes with test-first development, red-green-refactor, regression scripts, browser checks, or behavior-focused validation before production code changes.

日本語の概要は準備中です。原文の説明を表示しています。

Use when diagnosing PlainTab bugs, broken UI behavior, failing extension/web-mode flows, storage or wallpaper regressions, startup issues, or performance regressions.

日本語の概要は準備中です。原文の説明を表示しています。

Use when reviewing PlainTab architecture, looking for refactoring opportunities, reducing coupling, improving testability, or making modules easier for agents to understand without redesigning stable behavior.

日本語の概要は準備中です。原文の説明を表示しています。