「behavior」の検索結果

Tune the GitHub Copilot AI — `copilot-instructions.md`, PR-review patterns, suggestion behavior, output verbosity. NOT for dev-environment setup (use `devcontainer`).

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

Use this skill whenever the user wants to create, edit, explain, validate, or troubleshoot a proctmux.yaml/procmux.yaml file, add or change proctmux processes, configure lifecycle behavior such as stop signals/on_kill/autostart, customize unified-mode layout/keybindings/style, or enable Makefile/package.json process discovery. Use it even when the user says this casually, such as "add my dev server to proctmux", "fix this proctmux config", "write a config for these services", or "what YAML option controls focus".

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

Use when adding, running, or debugging proctmux end-to-end integration tests, especially PTY/TUI behavior, terminal snapshots, unified/client modes, timing flakes, VT100 emulator limits, or files under tests/e2e and internal/testharness/e2e.

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

Automate terminal UI (TUI) apps with agent-tui for testing, inspection, demos, and scripted interactions. Use when automating CLI/TUI flows, regression testing terminal apps, verifying interactive behavior, or extracting structured text from terminal UIs. Also use when asked what agent-tui is, how it works, or to demo it. Do not use for web browsers, GUI apps, or non-terminal interfaces.

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

Harness-first workflow for evaluating and improving terminal UIs through real interaction. Use this whenever the user wants to review a TUI experience, compare before/after behavior, identify UX friction, validate navigation or filtering flows, inspect visual stability, or turn observed interaction problems into concrete follow-up tests and improvement recommendations. Prefer this skill any time a TUI should be exercised through a reproducible PTY/session harness instead of only reading code.

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

Modos operacionais de IA (brainstorm, implement, debug, review, teach, ship, orchestrate). Use para adaptar o comportamento com base no tipo de tarefa.

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

[Workflow] Use when activating the Code Refactoring workflow for restructure and improve existing code without changing behavior.

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

[Code Quality] Use when you need restructure code without changing behavior using extract method, extract class, rename, move, and inline patterns.

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

Use when reviewing, fixing, or verifying a pull request. Focus on correctness regressions, missing tests, permission mistakes, unsafe behavior, and minimal fixes.

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

Use when exposing app features to App Intents, Shortcuts, Siri, Spotlight, widgets, controls, or system actions — small safe AppIntents, AppShortcutsProvider, AppEnum/AppEntity, parameters, and open-vs-background behavior.

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

Use when designing, reviewing, or implementing a sidebar for an Apple-platform app — top-level navigation only, grouped sections, NavigationSplitView, consistent SF Symbols, and safe compact-width behavior.

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

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

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

Record browser or Web UI interaction demos as optimized GIFs using the available built-in browser, state-based frame capture, and deterministic encoding, then publish to a dedicated assets branch when the task includes attaching the GIF to a pull request. Use when asked to make, record, or generate a GIF that demonstrates a browser workflow, and for every pull request that changes product-user-visible GUI behavior, which MUST include a GIF recorded from the pull request's real server and model flow.

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

Benchmark CodeGraph retrieval quality on a real codebase by comparing agent behavior with vs without CodeGraph. Use when the user runs /agent-eval or asks to test, benchmark, audit, or validate a codegraph version (the local dev build or a published npm version) against a language's repo.

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

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.

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

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.

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

Design and review client UI changes — visual token discipline, reuse-before-adding, feedback surfaces (toast vs in-place notice vs empty state), overlay and menu safety, platform window adaptation, loading states, and error copy placement. Use when adding or changing product-user-visible GUI behavior, or when reviewing such a PR.

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

Validate database schema, migrations, indexes, and query behavior with structured pass/fail reporting.

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

GodoMaster — Godot 4.x game development intelligence: GDScript, nodes/scenes, 2D/3D rendering, physics, animation, UI, audio, input, shaders, networking, performance, export, file I/O, testing, localization, AI behavior, asset pipeline, and architecture tooling. Complete workflow for indie and professional game development based on official Godot documentation.

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

Pressure-test startup ideas against real user pain, current behavior, competitors, first-customer access, MVP scope, founder-market fit, and a two-week launch test. Produces a direct strong, weak, or pivot verdict.

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

GStack design plan review for user journey, layout, interaction model, responsive behavior, accessibility, and visual risk before UI work starts.

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

GStack report-only QA method for checking web or UI behavior, documenting blockers, and preserving evidence without modifying code.

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

GStack investigation method for bugs, incidents, failing tests, regressions, and unclear behavior where evidence and root cause should precede fixes.

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

GStack QA method for web/UI behavior verification and narrow fix loops when the user explicitly allows QA to repair issues.

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