「interop」の検索結果

Build or review WinUI 3 applications with the Windows App SDK, including MVVM patterns, packaging decisions, navigation, theming, windowing, and interop boundaries with other .NET stacks. USE FOR: building native modern Windows desktop UI on WinUI 3; integrating Windows App SDK features into a .NET app; deciding between WinUI, WPF, WinForms, and MAUI for Windows. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

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

Work on WCF services, clients, bindings, contracts, and migration decisions for SOAP and multi-transport service-oriented systems on .NET Framework or compatible stacks. USE FOR: working on WCF services, bindings, or clients; deciding whether a service should stay WCF or move to modern HTTP APIs; reviewing transport, security, or interoperability. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

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

Compose Multiplatform / KMP patterns - expect/actual composables, platform-specific code, density and font handling cross-target, iOS/Android/Desktop interop.

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

Use when reviewing, designing, or modifying Java enterprise systems that expose, exchange, store, process, export, or port data across users, businesses, connected products, cloud providers, APIs, event streams, AI data pipelines, data spaces, or SaaS platforms and need EU Data Act engineering controls. This should trigger for requests such as Review a Java platform for EU Data Act controls; Design data access and portability evidence; Add data-sharing request workflows, export formats, interoperability, metadata, audit logs, cloud-switching support, non-personal data safeguards, or trade-secret handoffs; Assess Data Act engineering readiness before production release. Part of Plinth Toolkit

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

Build, read, validate, modify SBML biological network models via the libSBML Python API. SBML Levels 1–3, reactions/kinetic laws, species, rules, FBC extension for flux balance, conversion. Interoperates with COBRApy, Tellurium/RoadRunner, COPASI. Use when programmatically constructing ODE or constraint-based metabolic/signaling models in SBML.

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

Apache Iceberg tables on Databricks — Managed Iceberg tables, External Iceberg Reads (fka Uniform), Compatibility Mode, Iceberg REST Catalog (IRC), Iceberg v3, Snowflake interop, PyIceberg, OSS Spark, external engine access and credential vending. Use when creating Iceberg tables, enabling External Iceberg Reads (uniform) on Delta tables (including Streaming Tables and Materialized Views via compatibility mode), configuring external engines to read Databricks tables via Unity Catalog IRC, integrating with Snowflake catalog to read Foreign Iceberg tables

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

Guides Researchers through Faiss installation, dense and binary similarity search, index training and composition, persistence and evaluation, and explicitly gated CPU/GPU interoperability workflows.

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

Owns platform splits for Compose Multiplatform apps: places declarations in commonMain, chooses expect/actual vs interface plus DI, wires host adapters and ports, and validates iOS/Swift interop, desktop and web targets, and platform lifecycle. Use when touching commonMain, expect, actual, iosMain, Swift, SKIE, Flow to Swift, desktop, wasm, web target, or platform-specific code. Do NOT use for routing or architecture (compose-architecture), feature slices (compose-feature), composables or resources (compose-ui), repositories or persistence (compose-data), or Gradle target setup (compose-project).

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

Design, implement, harden, and verify Model Context Protocol (MCP) servers with precise tool contracts, least-privilege authorization, safe transports, structured errors, and interoperability tests. Use when creating a new MCP server, exposing an API or data source through MCP, reviewing an MCP server design, adding or revising MCP tools, or preparing an MCP server for production.

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

Think and work like an expert Health Informatician. Use when a task calls for Health Informatician judgment. Reasons from semantic interoperability, provenance, and patient safety through FHIR/US Core, SNOMED-LOINC-RxNorm terminology mapping, OMOP/OHDSI ETL with DQD/Achilles, and chart-review PPV validation while treating immortal-time and confounding-by-indication bias, patient-matching/MPI failures, billing-code phenotypes, and vocabulary version drift as first-class failure modes.

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

Expert guidance for Apache Arrow, the cross-language columnar memory format for analytics workloads. Helps developers use Arrow for high-performance data interchange between systems, zero-copy reads, and efficient columnar processing in Python (PyArrow) and JavaScript (Arrow JS).

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

Develop and run Mojo code in Claude.ai containers. Handles installation, compilation, and execution. Use when writing Mojo code, benchmarking Mojo vs Python, or when user mentions Mojo, Modular, or MAX. Routes to Modular's official skills (mojo-syntax, mojo-python-interop, mojo-gpu-fundamentals) for language-specific correction layers.

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

Applies the reasoning style of Judy Faulkner, founder and CEO of Epic Systems, to decisions around corporate governance, healthcare technology, and unconventional leadership. Use this skill whenever Claude is asked for advice on going public vs. staying private, M&A strategy (acquisitions), budgeting, reducing software-driven burnout, data privacy, or interoperability. Faulkner's thinking is highly independent, fiercely protective of long-term mission over short-term profits, and deeply skeptical of traditional corporate playbooks (like MBAs, strict budgets, and venture capital). Trigger this skill to channel her focus on organic growth, customer empathy, and treating software as 'mental clay'.

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

Create, validate, and enrich Open Knowledge Format (OKF) bundles — the open spec for representing organizational knowledge as markdown files with YAML frontmatter. Use when the user mentions 'OKF', 'Open Knowledge Format', 'knowledge bundle', 'OKF bundle', 'create a knowledge base for agents', 'validate OKF', 'convert to OKF', 'enrich knowledge docs', 'agent-readable knowledge', 'LLM wiki', 'knowledge catalog', 'kcmd', or wants to structure knowledge as markdown files for AI agent consumption. Also use when the user has a directory of markdown files and wants to make them interoperable or conformant with the OKF standard. Even for simple requests like 'make this folder OKF conformant' — the skill has critical structural rules the agent needs.

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

Guides native Android development with Kotlin, Jetpack Compose, and Views interop. Use when building, rewriting, or reviewing modern Android apps after establishing runtime truth.

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

Guides native iOS with Swift, SwiftUI, UIKit interop, concurrency, and persistence. Use when building or reviewing iPhone/iPad apps after establishing runtime truth.

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

Suggest whether Claude Code, Codex CLI, or Grok Build is a useful next collaborator, without launching a CLI or changing controls. Use when comparing the three CLIs, planning a handoff, or deciding whether an independent implementation or review would help.

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

Comprehensive research corpus covering 40+ agentic coordination protocols and ecosystems (MCP, A2A, ANP, UCP, ACP, AGNTCY, NANDA, FIPA, WoT, etc.) with emphasis on identity architectures, governance bodies, and interoperability convergence patterns.

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

Bridge layer connecting the emerging agentic coordination protocol ecosystem (MCP, A2A, ANP, AGNTCY, AITP, LMOS, AAIF) to the plurigrid/asi skill graph. Maps protocol-level identity mechanisms (W3C DID, OAuth 2.1, IPSIE, Entra Agent ID, Agent Cards, passport.gay) into GF(3)-classified skills. The central unsolved problem — no unified identity across MCP+A2A+A2UI — is directly addressed by the bisimulation oracle composition.

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

Routes a Superpowers plan file through the /work-backlog-item pipeline and writes SAM task back-references and chunk annotations into the original plan. Use when given a path to a Superpowers plan file via $ARGUMENTS and needing to create a linked backlog item plus SAM task plan.

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

Integrates patterns from external sources (URLs or local files) into local skills, agents, and plugins. Use when comparing external agent definitions against local equivalents, extracting best practices from frameworks like GSD or BMAD-METHOD, enhancing local skills with external workflow patterns, or adding interoperability with external tool ecosystems. Runs a 3-phase workflow — parallel candidate mapping, contextual enhancement, and validation — with source attribution and backlog tracking for deferred enhancements.

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

Maintain portal cookie configuration, reusable cookie directive parsing, common prefixes and explicit names, domain attributes, factory issuance/deletion, and cookie interoperability with OIDC, refresh, OAuth, and gatekeepers.

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

Implement a JSON-RPC 2.0 A2A server with full task lifecycle management (submitted/working/completed/failed/canceled/input-required), SSE streaming, and push notifications. Use when implementing an agent that participates in multi-agent A2A workflows, building a backend for an Agent Card, adding A2A protocol support to an existing agent or service, or deploying an agent that must interoperate with other A2A-compliant agents.

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

Design an A2A Agent Card (.well-known/agent.json) manifest describing agent capabilities, skills, authentication requirements, and supported content types. Use when building an agent that must be discoverable by other A2A-compliant agents, exposing capabilities for multi-agent orchestration, migrating an existing agent to the A2A protocol, defining the public contract for an agent before implementation, or integrating with agent registries that consume Agent Cards.

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