「behavior」の検索結果

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

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

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

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

Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.

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

Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.

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

Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.

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

Show or set NeatContext routing to auto, ask, or manual for Codex, with an optional default shared with every other NeatContext host. Use only when the user explicitly invokes this skill or clearly asks to change routing behavior.

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

Create a fresh NeatContext context from a user-defined behavioral profile and an existing local knowledge folder. Use only when the user explicitly asks to create a new context, or runs /neatcontext-create — not to save the current conversation.

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

Create a fresh NeatContext context from a user-defined behavioral profile and an existing local knowledge folder. Use only when the user explicitly invokes this skill or asks to create a new context rather than save the current conversation.

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

Show or set NeatContext routing to auto, ask, or manual for the current Kimi Code session, with an optional global default for new sessions. Use only when the user explicitly invokes this skill or clearly asks to change routing behavior.

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

Create a fresh NeatContext context from a user-defined behavioral profile and an existing local knowledge folder. Use only when the user explicitly invokes this skill or asks to create a new context rather than save the current conversation.

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

Migrate a UI component from one framework to another, preserving behavior and tests.

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

> Game theory, Monte Carlo simulations, behavioral economics, and competitive war gaming.

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

Expert-level polymer science covering polymer structure, thermoplastics and thermosets, mechanical behavior, processing methods, and polymer selection for engineering applications.

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

Frontend UI design, critique, audit, polish. Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.

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

Test coverage quality analysis — behavioral coverage, critical gap identification, test resilience evaluation.

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

Test coverage quality analysis — behavioral coverage, critical gap identification, test resilience evaluation.

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

Isolate the root cause of ML performance drops, inconsistent evaluations, prediction errors, and training-serving mismatches across data, labels, splits, pipelines, models, metrics, and runtime behavior. Use when investigating a reproducible failure or regression, not routine model selection or general performance validation.

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

Enforce traceability from natural-language intent to machine predicates, final observables, evidence, and owner-readable acceptance. Use when conducting any audit, review, QA pass, parity or compliance check, security assessment, code or architecture review, visual or behavioral comparison, data validation, system verification, completion gate, or claim that an implementation satisfies a human request.

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

Use BEFORE writing any test — enumerate cases per behavior (happy / boundary / error / abuse), prioritize by likelihood × impact, cross-check via subagent — even if the user just says 'add tests'.

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

Use on a bug, test failure, crash, or unexpected behavior — enforce reproduce → isolate → hypothesize → verify before any fix; fires even on 'this is broken' / 'quick fix'.

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

Use for deep React analysis: component tree, state flow, props flow, hooks usage, rendering behavior, and React-specific failure patterns.

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

Use for deep Node.js / Express project analysis: boot flow, middleware order, async behavior, data layer, auth/security, and Node-specific runtime failure patterns.

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

When shaping feedback — situation-behavior-impact, growth-vs-corrective split, cadence design, ladder-of-inference checks. Triggers on 'how do I give this feedback', 'perf review shape'.

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

Creates and manages project-level overrides for shared skills, rules, and commands — extending or replacing originals from .augment/ with project-specific behavior in agents/overrides/.

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