'blueprint' 검색 결과

Support Zoom meeting integration in Unreal Engine projects using C++ and Blueprint wrappers, intermediary code that calls the SDK. Consult guides for SDK mappings, initialization and meeting flows, compatibility, and troubleshooting.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Embedding Zoom meetings in an Unreal Engine project
• Checking how C++ or Blueprint wrappers map to the SDK
• Reviewing meeting join and start implementation patterns

Build Unreal Engine 5 gameplay with Blueprint visual scripting: Blueprint Classes, the Event Graph and Construction Script, variables/functions/macros, and Blueprint communication (Cast, Interfaces, Event Dispatchers). Use when working in Blueprints, wiring an event graph, deciding how Blueprints talk to each other, or when the user mentions Blueprint, BP, event graph, construction script, or a Blueprint .uasset.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build a Solution Blueprint for a Dynamics 365 Finance and Supply Chain Management implementation through guided interviews. Define scope and architecture, compare options, and document decisions, their rationale, assumptions, and unresolved questions across working sessions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create an architecture blueprint for a new D365 implementation
• Define implementation scope and rollout phases
• Compare data migration and integration approaches

Send research questions to a running NVIDIA AI-Q Blueprint backend and receive reports with citations and source URLs preserved. Track longer research jobs, check their progress, and retrieve completed reports after a local interruption.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Research a topic through AI-Q
• Check progress on a long research job
• Resume tracking research after an interruption

Set up and operate NVIDIA AI-Q Blueprint locally or on your own infrastructure. Choose a deployment mode, configure credentials, check service health, troubleshoot failures, and provide a verified server address for aiq-research.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Starting a backend for aiq-research
• Running AI-Q through a terminal or browser
• Deploying AI-Q to a Kubernetes cluster

Deploy applications to Render by inspecting code and preparing build settings, environment variables, and required services. Generates render.yaml deployment configuration or creates services through MCP, then checks deployment status, logs, and basic health.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Publish a web application on Render
• Prepare deployment configuration for multiple services
• Set up databases and scheduled jobs

Install Scenic, a language for describing scenarios with randomized conditions, into the Python environment used by CARLA. Check command-line tools and version compatibility, optionally download example scenarios and map assets, and save the installation paths.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing Scenic to work with CARLA
• Diagnosing scenario model import failures
• Checking missing vehicle definition tables

Analyze a codebase to document its technologies, architecture, dependencies, and implementation patterns. Produce a Markdown reference with optional diagrams, code examples, and guidance for adding features consistently with the existing design.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Understand an unfamiliar codebase's architecture
• Document components, dependencies, and data flow
• Create guidance for adding features consistently

Import an FBX character into a CARLA source build as a pedestrian available through the Python API. Check its GEN3 skeleton, create assets and a walker blueprint, register it, and verify spawning, ground placement, and movement.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add a custom FBX character as a CARLA pedestrian
• Check whether an FBX uses the required GEN3 skeleton
• Investigate floating or motionless imported pedestrians

Create print-friendly slides explaining system architecture or a pipeline, a sequence of processing steps. The layout combines a cream background, blueprint grids, process boxes, rust-red callouts, and dashed feedback loops.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Explaining a system architecture
• Presenting the steps in a processing pipeline
• Showing feedback loops in a workflow

Performance benchmarking for a deployed NVIDIA RAG Blueprint server: profiling pass + aiperf load test driven by a single YAML config. Not for accuracy / RAGAS scoring (use rag-eval) or for deploying / repairing services (use rag-blueprint).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

[omh] Recurring Hermes job on a schedule (cron, digests): design recurring Hermes operations with schedule, delivery, silence policy, context chain, and prepared-vs-observed status. Use when the user says: automation-blueprint, scheduled ops, scheduled operation, scheduled operations, automation blueprint, cron blueprint, cron-ready, recurring ops.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Provision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmi_path, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmi_path token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app registration (use entra-app-registration), Microsoft Foundry agent authoring (use microsoft-foundry).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Microsoft Entra Agent ID (preview) for creating OAuth2-capable AI agent identities via Microsoft Graph beta API. Covers Agent Identity Blueprints, BlueprintPrincipals, Agent Identities, required permissions, sponsors, and Workload Identity Federation. Includes Microsoft Entra SDK for AgentID (containerized sidecar) for polyglot agent authentication (Docker/Kubernetes), 3P agent integration, autonomous and interactive agent patterns. Triggers: "agent identity", "agent id", "Agent Identity Blueprint", "BlueprintPrincipal", "entra agent", "agent identity provisioning", "Graph agent identity", "entra sidecar", "agent id sidecar", "auth sidecar", "3P agent", "third-party agent identity", "polyglot agent auth".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the deliverable is WordPress Playground Blueprint JSON or a Blueprint bundle, including creating, editing, reviewing, validating schema keys, choosing steps/resources, and debugging Blueprint files. For only running or sharing a Playground environment, use wp-playground.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Provision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmi_path, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmi_path token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app registration (use entra-app-registration), Microsoft Foundry agent authoring (use microsoft-foundry).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert knowledge for Azure Blueprints development including troubleshooting, decision making, security, configuration, integrations & coding patterns, and deployment. Use when migrating off Blueprints, mapping to PBMM/ISO/SWIFT, automating via CLI/PowerShell/REST, or fixing deployment errors, and other Azure Blueprints related development tasks. Not for Azure Policy (use azure-policy), Azure Resource Manager (use azure-resource-manager), Azure Resource Graph (use azure-resource-graph), Azure Portal (use azure-portal).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when user wants a standalone HTML diagram in flat engineering blueprint style — architecture diagrams, system flows, technical spec sheets, component maps. Generates one HTML file using Tailwind v4 (browser CDN) for layout and D3 v7 (CDN) for SVG diagrams. User-invoked only — do NOT auto-trigger. Triggers on "/html-draft", "сделай blueprint", "технический чертёж", "архитектурная схема", "инженерная схема", "blueprint diagram", "engineering blueprint", "technical spec sheet", "architecture diagram", "system flow diagram".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

"/blueprint", "blueprint", "task graph", "contract derivation", "execution plan", "plan tasks from requirements", "contract-first planning" Turn requirements.md into an executable blueprint (plan.json + contracts.md). Five phases: Contracts → Tasks → Journeys → Verify Plan → Commit. Sits between /specify and /execute. Scope-adaptive (greenfield → bugfix). Uses hoyeon-cli (plan.json only; requirements.md is read as-is via Read tool).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Hoyeon blueprint workflow for Codex. Use when the user invokes "$hoyeon-blueprint" or wants to turn requirements.md into a validated plan.json and optional contracts.md. This adapter loads the canonical blueprint skill and follows its Codex runtime surface.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create a single HTML wireframe for a desktop dashboard using grey blocks, placeholder text bars, and crossed image boxes. Review navigation, information hierarchy, and panel placement before choosing final colors, copy, or imagery.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing a desktop dashboard layout
• Checking navigation and information hierarchy
• Planning KPI, chart, and table placement

Turn an incident review into an HTML presentation covering the root cause, fix, and follow-up actions. Use a dedicated template with speaker notes to help engineering, reliability teams, and leadership discuss next steps.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Presenting an incident review
• Explaining a bug's root cause and fix
• Discussing systemic follow-up actions

Create static SVG diagrams, scalable images for lessons, READMEs, and manuals. It uses real system names, nine diagram types, and consistent colors and arrows, with checks for readable labels, accessible descriptions, and valid markup.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add a diagram of system interactions to a README
• Explain state transitions in a manual
• Illustrate data flow from logs or specifications

Analyze an existing project's folders and produce a guide explaining directory purposes, naming conventions, and file placement. Choose a tree, list, or table, and optionally include templates for adding features consistently with the project's observed structure.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating a folder guide for new team members
• Documenting naming and file placement conventions
• Preparing folder templates for new features