「state」の検索結果

Use to evaluate the current state of a diamond. Checks theory gates, confidence levels, and recommends next action.

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

Record a diamond's next decision (set_target; start_experiment and commit_to_build; release; close; an L0's state_purpose or review). Runs the theory gates each decision needs, validates evidence, and at close runs the executable Definition of Done checklist.

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

Central dispatcher for the canvas/state render fleet. Routes intent to a specialist (`/mycelium:diamond-render`, `/mycelium:ost-render`, `/mycelium:cycle-render`) OR lists what's renderable. Cross-cutting views spanning multiple canvases (opp→sol→cycle traceability, confidence-over-time, cluster-graduation-flow) are research-gated and NOT emitted by default. See `${CLAUDE_PLUGIN_ROOT}/engine/render-conventions.md` for shared conventions.

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

Build and review Blazor applications across server, WebAssembly, web app, and hybrid scenarios with correct component design, state flow, rendering, and hosting choices.

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

Apply whenever writing or editing source code in any core's build agent (backend-eng, ui-builder, or equivalent). Governs when a comment belongs at all and what it may say. Default is no comment; a comment is only for the non-obvious. Never restates what the code does, never narrates the task, fix, or conversation that produced it.

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

Provides Mermaid diagram syntax, best practices, and styling rules for technical visualizations. Use when creating diagrams, flowcharts, sequence diagrams, class diagrams, state diagrams, ER diagrams, architecture diagrams, C4 diagrams, or any visual documentation in markdown.

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

Provides Mermaid diagram syntax, best practices, and styling rules for technical visualizations. Use when creating diagrams, flowcharts, sequence diagrams, class diagrams, state diagrams, ER diagrams, architecture diagrams, C4 diagrams, visualizations, or any visual documentation in markdown. Always use this skill when generating or updating Mermaid code blocks.

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

Build custom AI agents in Claude Code from a user's problem statement. This skill analyzes the user's use case, asks smart clarifying questions, researches the internet for similar agents (GitHub repos, blogs, Claude Code community patterns), and then architects and builds production-ready Claude Code agents — including subagents, skills, hooks, slash commands, MCP integrations, and CLAUDE.md configuration. Use this skill whenever the user wants to create an agent, build an automation workflow, set up a Claude Code subagent, design a multi-agent system, or says things like 'build me an agent for...', 'automate this with Claude Code', 'I want a subagent that...', 'help me create a workflow', 'set up an agent pipeline', or any variation of wanting Claude Code to do something specialized. Also trigger when the user mentions agent architecture, agent SDK, agentic workflows, or task delegation in Claude Code — even if they don't use the word 'agent' explicitly.

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

Use when Codex must make a high-quality judgment on any complex problem, not only technical problems. Trigger when a question has high complexity, uncertainty, cost of being wrong, long-term impact, value tradeoffs, possible structural causes, or when the user asks for 全面思考, 深度理解, 系统性分析, 帮我想清楚, 从根上看, 这件事到底怎么看, 方法论, 复杂问题拆解, 系统方案, 架构判断, 策略判断, or 根因分析. Also trigger for project and engineering high-risk scenarios such as multi-module, multi-environment, multi-data-source, multi-state, financial truth, live trading, ledger, revenue, customer assets, order governance, broker interfaces, online availability, major solution selection, and system closure.

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

Check that a locally running site's WebMCP tools register and execute correctly. Use to verify WebMCP tools, confirm document.modelContext tools appear on the right pages and auth states, or test @nekuda/webmcp-sdk tools in a browser.

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

Use when building, debugging, or documenting Telegram bot polling flows that need safe agent routing, state tracking, and final-only replies without webhooks.

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

Verifies repository baseline test passing state and available memory/GPU resources to ensure safe mission execution.

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

React ecosystem expert including hooks, state management, component patterns, React 19 features, Shadcn UI, and Radix primitives

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

Workflow recovery protocol for resuming workflows after context loss, session interruption, or errors. Handles state reconstruction, artifact recovery, and seamless workflow continuation.

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

General rules pertaining to Mobile UI development. Covers UI/UX best practices, state management, and navigation patterns.

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

Independent LLM judge evaluates task completion separately from the executing agent, catching false success claims by reviewing task goal, actions taken, final state, and evidence. Produces PASS/FAIL with confidence score and reasoning.

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

Verify that task outputs actually achieve stated goals through 4 progressive levels of verification

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

Flutter and Dart expert including widgets, state management, and platform integration

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

Hunt authentication and authorization bypasses — forced browsing, path traversal in auth, header injection, JWT downgrade, OAuth state confusion, role manipulation. Use when an endpoint returns 401/403 but appears reachable.

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

Hunt OAuth 2.0 and OIDC flaws — redirect_uri abuse, state CSRF, PKCE bypass, scope manipulation, implicit-flow token theft, postMessage origin tricks, ID token sub claim swap, JWKS confusion, response_type confusion, and OAuth-CSRF. Use when an app has Google/GitHub/Facebook/Apple/custom OAuth or OpenID Connect.

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

Hunt JSON Web Token (JWT) vulnerabilities — alg=none bypass, RS256→HS256 key confusion, weak HMAC secret cracking, kid path traversal, JWKS injection, jku/x5u header attacks, embedded JWK confusion, expired-token acceptance, claim mutability, and token replay. Use when an app uses JWT for authentication or stateless sessions.

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

Hunt business logic flaws — race conditions, workflow state bypass, parameter pollution affecting logic, coupon/discount abuse, refund logic, multi-step process bypass, integer overflow, negative quantities, double-spend. Use when looking for non-CVE bugs that require understanding the app's intended workflow.

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

Plan and freeze workflow execution by creating an Execution Contract, setting PLAN_FROZEN/CURRENT_ROLE, and updating PROJECT_STATE decisions and Top 3. Use when starting workflow delivery, re-planning after unfreeze, or when scope/constraints change before execution.

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

Improve or implement purposeful motion systems, micro-interactions, gestures, and transition behavior for production-grade UI. Use when the user mentions animation, motion, transitions, micro-interactions, hover states, drawers, toasts, gestures, or making the UI feel more alive.

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