「state」の検索結果

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

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

Use when constructing base / upside / downside scenarios — three-statement modeling, sensitivity analysis, optionality reasoning. Triggers on 'model the scenarios', 'what if growth halves'.

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

Use when shaping a Livewire component before code — full-page vs partial, parent/child split, event flow, state-vs-props boundary, hydration cost — even on 'add this Livewire component'.

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

Use when the project's frontend stack is Livewire — dispatched by `directives/ui/{apply,review,polish}.ts`. Covers reactive state, events, lifecycle hooks, and component/view separation.

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

Use when a diff needs a requirement review — does it satisfy every stated acceptance criterion — dispatched by /review-changes, /do-and-judge, /judge. Never infers criteria from the diff.

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

Use to drive a scalar metric down or up across bounded iterations — keep on strict improvement, revert otherwise, state on disk. Triggers 'minimize X', 'optimize until it stops improving'.

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

Use BEFORE writing or editing any non-trivial UI — inventories components, design tokens, shadcn primitives, and reusable patterns into state.ui_audit. Hard gate for fe-design.

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

Black-box evaluation of a shipped LLM feature — adversarial probes for hallucination, prompt-injection, and cost-runaway vs stated expectations. Not RAG/embedding. Triggers 'review my chatbot'.

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

Use when designing or reviewing a form — validation timing, error display, submission lifecycle, optimistic UI, dirty/pristine state, idempotency — even on 'why does submit double-fire?'.

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

Use when deciding what earns a page — the page, action and info classes stated provider-neutrally, and the rule that a page without an owner, a runbook and a first diagnostic step is malformed.

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

Quando o usuário quer otimizar onboarding pós-signup, ativação de usuários, experiência de primeira execução ou time-to-value. Use também quando o usuário menciona "fluxo de onboarding", "taxa de ativação", "ativação de usuários", "experiência de primeira execução", "empty states", "checklist de onboarding", "aha moment" ou "experiência do novo usuário". Para otimização de signup/registro, veja signup-flow-cro. Para sequências de email contínuas, veja email-sequence.

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

Expert em LangGraph - o framework de nível produção para construir aplicações de IA com múltiplos atores e estado. Aborda construção de grafos, gerenciamento de estado, ciclos e ramificações, persistência com checkpointers, padrões human-in-the-loop e o padrão ReAct. Usado em produção no LinkedIn, Uber e 400+ empresas. Esta é a abordagem recomendada pelo LangChain para construir agentes. Use quando: langgraph, langchain agent, stateful agent, agent graph, react agent.

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

Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.

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

[Skill Management] Use when starting a detected workflow, initializing workflow state, or activating a workflow sequence.

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

[Process] Use when you need to end the active workflow and clear state.

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

Use when generating, documenting, or updating architecture diagrams, flowcharts, sequence, ER, class, or state diagrams using Mermaid in docs/architecture/.

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

Use when generating a single dense technical architecture, reference poster, or system diagram image for a software project. Produces a source-grounded bitmap diagram with topology, primitives, ingest/process flow, core logic, state scopes, tiers/modules, surfaces, runtime cards, and strict semantic color rules.

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

Plan and document handoffs, parent lane contracts, and parallel batch contracts between specialized AI agents (foreman, workers, reviewers). Use for multi-agent workflows, subagents, original goal preservation, native gates, claim ceilings, terminal states, baton passes, or guild-style agent coordination.

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

Use when reviewing an app for launch-readiness — Product Hunt polish, first impression, visual hierarchy, onboarding, empty states, screenshots, positioning, and the tiny details that make it feel premium.

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

Use when a macOS app needs a TCC permission or touches private data — the map of which API, Info.plist key, and entitlement each permission needs, pre-prompt explanation patterns, denied-state recovery with System Settings deep links, and honest privacy copy.

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

Use when adding, reviewing, or debugging Launch at Login in a macOS app — SMAppService registration, the requiresApproval state, a Settings toggle that reflects reality, and migration off deprecated login-item APIs.

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

Use when integrating an app with local AI models through Ollama — connection checks, model listing/selection, local-only mode, cloud-fallback consent, visible run states, and recovering from Ollama errors.

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

Produce an up-to-date, state-of-the-art recommendation using domain expertise and brief web research. Use only when explicitly invoked.

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

Re-analyze an existing GitHub Issue using its current title and body as input, refresh the implementation plan against the latest code state, and update the Issue in place. Use this when the user provides an Issue number (numeric, `#`-prefixed, or Issue URL) and wants to regenerate the Explore-based analysis. For reflecting comment-driven updates instead, use update-issue. For creating a brand-new Issue from a natural-language task description, use create-issue.

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