104건 · 관련도순
Add, review, or fix calls between Blazor and JavaScript. Organize JavaScript modules alongside components, control when calls run, combine related operations, and clean up references with handling for server disconnections.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Addresses HIPAA privacy and security requirements for health data interoperability under the 21st Century Cures Act, ONC Health IT Certification Program, and CMS Interoperability and Patient Access Final Rule. Covers information blocking prohibitions, FHIR API patient access, TEFCA exchange purposes, and privacy safeguards for health information exchange. Keywords: interoperability, information blocking, FHIR, TEFCA, Cures Act, patient access API, health information exchange.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Add, review, or fix JavaScript interop in Blazor components. USE FOR: calling JavaScript from Blazor, calling .NET from JavaScript, collocated .razor.js modules, IJSRuntime, IJSObjectReference lifecycle, DotNetObjectReference, ElementReference, timing rules for when JS is available, IAsyncDisposable disposal of JS references, server-side JS interop safety. DO NOT USE FOR: general Blazor component authoring without JS interop needs (use author-component), forms (use collect-user-input).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build servers and clients for A2A, an open protocol that lets AI agents communicate across frameworks. Publish agent capabilities, exchange tasks and results, stream progress, and add notifications for workflows involving multiple agents.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create or review Blazor components, reusable parts of a web interface. Covers passing data and events between parent and child components, content templates, asynchronous work, display states, and resource cleanup when components are removed.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create or review Blazor components (.razor files) with correct architecture. USE FOR: writing new Blazor components that do NOT involve JavaScript interop, implementing parameters and EventCallback, RenderFragment slots, component lifecycle (OnInitializedAsync, OnParametersSet), async patterns, IAsyncDisposable, CancellationToken, CSS isolation, code-behind. DO NOT USE FOR: creating new projects (use create-blazor-project), JavaScript interop or calling browser APIs from Blazor (use use-js-interop), forms and validation (use collect-user-input), prerendering issues (use support-prerendering), HTTP data fetching patterns (use fetch-and-send-data), coordinating state between unrelated components (use coordinate-components).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Set up Ignite UI Lite controls or GridLite in Blazor applications. Match package references, service registration, namespaces, theme stylesheets, and interactive rendering settings to the app’s structure, including projects with separate server and client code.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Write and review .NET calls to native C/C++ libraries using P/Invoke. Covers function declarations, string conversion, memory ownership, and platform differences to help investigate crashes, memory leaks, and corrupted data.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Correctly call native (C/C++) libraries from .NET using P/Invoke and LibraryImport. Covers function signatures, string marshalling, memory lifetime, SafeHandle, and cross-platform patterns. USE FOR: writing new P/Invoke or LibraryImport declarations, reviewing or debugging existing native interop code, wrapping a C or C++ library for use in .NET, diagnosing crashes, memory leaks, or corruption at the managed/native boundary. DO NOT USE FOR: COM interop, C++/CLI mixed-mode assemblies, or pure managed code with no native dependencies.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Add, configure, or review Ignite UI for Blazor Lite component support in Blazor applications. USE FOR: installing IgniteUI.Blazor.Lite or IgniteUI.Blazor.GridLite, registering AddIgniteUIBlazor() in Blazor Server, WASM, Hybrid, or split Blazor Web App projects, adding @using IgniteUI.Blazor.Controls, wiring the theme stylesheet, picking the right host page, locating the GridLite stylesheet path, explaining single-project vs split Server/Client Web App setup differences, and checking where an interactive render mode is needed for Ignite UI components to work. DO NOT USE FOR: general Blazor component authoring without Ignite UI, choosing app architecture or render mode from scratch (see create-blazor-project), JavaScript interop (see use-js-interop), authentication (see configure-auth), prerendering (see support-prerendering), or layout/component design questions that need no Ignite UI setup.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when reviewing, designing, or modifying Java enterprise systems that may support EU Digital Markets Act gatekeeper-platform concerns, core platform services, interoperability, business-user data access, consent-dependent data combination, ranking, self-preferencing, advertising transparency, or anti-circumvention controls. This should trigger for requests such as Review a Java platform for DMA controls; Design interoperability and business-user data access evidence; Add ranking, consent, preference, or anti-circumvention audit controls; Assess gatekeeper-platform engineering evidence before production release. Part of Plinth Toolkit
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze data interoperability issues in construction projects. Identify format incompatibilities and data loss points.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use DeepMind dm-haiku as a JAX neural-network library for transforms, modules, state/RNG, layers, advanced JAX interop, and optional Flax interop.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Builds Agent2Agent (A2A) servers and clients, the open protocol (originally from Google, now under the Linux Foundation) that lets AI agents from different frameworks call each other. Use when the user wants to create an A2A-compliant agent, build an Agent Card, implement task management, connect agents across frameworks, set up agent discovery, handle streaming responses, implement push notifications, or orchestrate multi-agent workflows. Trigger words: a2a, agent to agent, agent2agent, a2a protocol, a2a server, a2a client, agent card, agent interoperability, agent collaboration, multi-agent, agent discovery, a2a sdk, a2a task.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Bridge layer connecting the Agentic AI Foundation (AAIF) governance structure — Linux Foundation stewardship of MCP, goose, AGENTS.md — to the plurigrid/asi skill graph. Formalizes AAIF-compatible skill registration, IPSIE identity profiles, and the cross-protocol interoperability surface. Maps the AAIF platinum member ecosystem (AWS, Anthropic, Block, Bloomberg, Cloudflare, Google, Microsoft, OpenAI) to specific ASI skill integration points.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Open protocol for AI agent interoperability enabling standardized communication between agents, applications, and humans across different frameworks
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Open protocol for AI agent interoperability enabling standardized communication between agents, applications, and humans across different frameworks
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when defining clinical data model requirements for Health Cloud: HL7/FHIR data mapping, interoperability requirements, FHIR R4-aligned object activation, CodeableConcept constraints, and middleware translation requirements. NOT for the field-level mapping work itself — use data/fhir-data-mapping. NOT for choosing legacy HC24__ EHR objects vs standard clinical objects — use data/health-cloud-data-model.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Knowledge base from the NASA Digital Engineering Acquisition Framework Handbook (NASA-HDBK-1004). Use for acquiring digital/model-based data under contract: the Data Requirements Description (DRD) instrument and the Appendix A DRD suite (TDP, MBx, CDMP, CSA, CR, FCA/PCA, SDT, EMDAL, REF, MRI); the Data Type 1-5 control scale; SOW/RFP/Cost-Volume contract language and data rights (FAR/DFARS, Table 3 license categories); the Requirements Exchange Format (REF/ReqIF, UUID schema) and Master Records Index; model-based data definition (MBSE, CAD/PMI, M&S credibility, BOM, release-state mapping, PLM); digital data collaboration, the four owned architectures, and interoperability standards (MIL-STD-31000, STEP/ISO 10303, ASME Y14); the four MBE interoperability use cases; and MBE Plan development. Scope is the acquisition and contracting side of digital engineering. Does not reproduce ISO/STEP/ASME/MIL-STD/SAE standard text, and the companion NASA-HDBK-1009A carries the deeper digital-engineering practitioner detail this handbook defers to.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan and diagnose FIPA-style ontology-service interactions while keeping declared ontology relations, provider capability, and application authorization separate. NOT for treating an ontology mapping as provider authority or guaranteed interoperability.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Migrate existing Remotion video compositions to HyperFrames HTML and GSAP. Checks source code for unsupported patterns, maps animation and media features, compares rendered videos for visual similarity, and documents translation gaps.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build Python workflows for filtering, grouping, joining, and reshaping table data with Polars. Get guidance on migrating pandas code and using lazy evaluation, which optimizes a processing plan before execution, for large datasets.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build and review numerical workflows for MATLAB or GNU Octave, including arrays, tables, graphics, tests, and MAT files. Helps plan release migrations, reproducible projects, and Python integration while checking runtime, compatibility, and license requirements.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build Blazor interfaces with Microsoft Fluent UI components. The skill guides library setup, forms, selection controls, dialogs, notifications, and themes, and helps troubleshoot missing interface elements caused by provider configuration or JavaScript integration issues.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.