「node」の検索結果

Bevy ECS skill for UI layout. Keywords: Bevy, UI, Node, Flexbox, BackgroundColor, Button.

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

AI movement decision router for chase, patrol, crowd, and bake choices on top of NavigationAgent/Server. Use when deciding node agent vs RID server, bake vs obstacle, layer masks, or retarget policy — not for engine navmesh recipes. Keywords: AI navigation, chase retarget, patrol, crowd RVO, bake vs obstacle, NavigationAgent decision tree.

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

Expert patterns for RPG/action ability systems including cooldown strategies, combo systems, ability chaining, skill trees with prerequisites, upgrade paths, and resource management. Use when implementing unlockable abilities, character progression, or complex skill systems. Trigger keywords: PlayerAbility, AbilityManager, cooldown, SkillTree, SkillNode, prerequisites, can_use, execute, ComboSystem, ability_chain, global_cooldown, charge_system, upgrade_path.

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

Expert patterns for migrating 2D games to 3D including node type conversions, camera systems (third-person, first-person, orbit), physics layer migration, sprite-to-model art pipeline, and control scheme adaptations. Use when porting 2D projects to 3D or adding 3D elements. Trigger keywords: CharacterBody2D to CharacterBody3D, Area2D to Area3D, Camera2D to Camera3D, Vector2 to Vector3, collision_layer migration, sprite to MeshInstance3D, 2D to 3D conversion.

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

Bevy ECS skill for animation blending. Keywords: Bevy, AnimationGraph, blend, AnimationGraphHandle, AnimationNodeType.

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

Add Temps error tracking to applications using the Sentry-compatible SDK. Temps exposes a Sentry-compatible DSN that works with the official Sentry SDK for each language/framework — no code changes beyond initialization are required. Use when the user wants to: (1) Add error tracking to any app (React, Next.js, Vue, Svelte, Angular, Node.js, Python, Go, Rust, Ruby, Java, PHP, .NET, React Native, Flutter), (2) Wire up uncaught exception and unhandled promise rejection capture, (3) Configure session replay for errors, (4) Upload source maps for readable stack traces, (5) Report releases and environments, (6) Capture custom errors/messages. Triggers: "add error tracking", "add sentry", "track exceptions", "report errors", "temps error tracking", "wire up error monitoring".

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

Deploy applications to the Temps platform with automatic framework detection, Dockerfile generation, and container orchestration. Supports Next.js, Vite, React, Node.js, Python, Go, Rust, Java, and C# applications. Use when the user wants to: (1) Deploy their app to Temps, (2) Set up CI/CD with Temps, (3) Configure deployment settings, (4) Create a Dockerfile for Temps, (5) Deploy a containerized application, (6) Set up automatic deployments from Git. Triggers: "deploy to temps", "temps deployment", "push to temps", "containerize for temps", "temps ci/cd".

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

Use when implementing state machines in Godot — enum-based, node-based, and resource-based FSM patterns with trade-offs

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

Use when designing scene tree structure — composition vs inheritance, when to split scenes, node hierarchy patterns

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

Use when implementing decoupled communication between nodes — global EventBus autoload with typed signals

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

Use when building user interfaces — Control nodes, themes, anchors, containers, and layout patterns

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

Use when a new Godot system or feature has open design decisions — interrogates them in batched rounds, scope first, each question with a recommended answer, and records the answers before any design or code. Triggers on "grill me", "ask me first", "question me on the design", "what do I need to decide before building". Not for choosing between nodes or APIs, and not for bug fixes.

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

Use when designing a new Godot feature or system — guides scene tree planning, node type selection, and architectural decisions

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

Use when building reusable node components — composition patterns, component communication, and interface design

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

Core ComfyUI knowledge covering workflow format, node types, pipeline patterns, and MCP tool usage

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

Drive the LTX Director (Timeline) node. Its Add Image/Text/Audio buttons are DOM-only and cannot be clicked by an agent; edit the hidden timeline_data JSON widget instead. Load when a workflow contains LTXDirector / LTXDirectorGuide / PromptRelayEncodeTimeline, or when asked to add, move, retime, or remove timeline segments (image / text / audio / motion).

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

Build MiniMax H3 (Hailuo) local video workflows with native T2V/I2V/R2V nodes, Comfy-Org INT8 weights, turbo LoRAs for 8GB VRAM, 15-second stereo-audio clips, and the official MiniMax prompting guides (cite by link, do not copy).

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

Common ComfyUI errors and fixes. OOM, missing nodes, dtype mismatches, black images, and debugging strategies

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

Swap an OUTFIT or transfer CLOTHING onto a person LOCALLY, keeping their face, pose and background. Use for "put this jacket on her", "change his shirt", "clothes swap", "try on", "outfit transfer", "virtual try-on", "dress her in", "wear this outfit". Prefer this over API/cloud edit nodes and over generic img2img/inpainting. NOT for identity-preserving edits that are not about clothing (background swaps, relighting, age/expression changes, object removal). Use a general image-edit workflow for those.

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

Expert knowledge for Azure Relay development including troubleshooting, security, configuration, and integrations & coding patterns. Use when configuring Hybrid Connections, WCF relays, Entra ID/SAS auth, Private Link, or .NET/Node.js Relay clients, and other Azure Relay related development tasks. Not for Azure Service Bus (use azure-service-bus), Azure Event Hubs (use azure-event-hubs), Azure Web PubSub (use azure-web-pubsub), Azure Application Gateway (use azure-application-gateway).

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

输出节点识别与解析。导航时机：添加新的输出节点类型、修改输出提取逻辑。

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

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

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

Loads full context for a React Flow (@xyflow/react) user journey mapping project. Use when working on, extending, debugging, or building features for the journey map tool. Triggers on: "journey map project", "open journey map", "work on journey map", "build user journey", "react flow journey project", "journey-map app", or any request to add features like swimlanes, emotion curves, persona nodes, touchpoints, or pain point markers.

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

Keeps README badge + inline counts in sync with the real number of skills, agents, graph nodes/edges, communities, converted pipelines, and test inventory. Runs automatically on every commit via a git pre-commit hook. Use when the README drifts from reality or before publishing a release.

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