826건 · 관련도순
Evaluates ambient context artifacts (CLAUDE.md, memory, local skills, settings hooks) for compatibility with swarm governance. Returns a classified report so users can address interference before launching a team.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design an API compatibility and deprecation policy — stability tiers, sunset timelines, and CI gates. Use when asked to "define an API stability policy", "set our deprecation timeline", or "write semver rules".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Research community usage patterns, real-world gotchas, and client compatibility for a specific known library, tool, or protocol feature. Use when a technical-researcher orchestrator needs community-sourced evidence about a named library or feature — bug reports, workarounds, compatibility gaps, and patterns from issue trackers and discussions. Distinct from the broad ecosystem-researcher agent — this skill targets a KNOWN entity and mines what real users have actually experienced, not what exists in a domain.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user asks about "POSIX compatibility", "portable shell scripts", "cross-shell compatibility", "bashisms", "shebang selection", or mentions writing scripts that work on different shells (bash, sh, dash, zsh) or different systems.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design stable, compatible public APIs using extend-only design principles. Manage API compatibility, wire compatibility, and versioning for NuGet packages and distributed systems.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manages Apache Avro schema evolution with compatibility checking via Confluent Schema Registry API. Validates forward, backward, and full compatibility across schema versions automatically.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design serialization schemas using JSON Schema, Protocol Buffer definitions, or Apache Avro. Covers schema versioning, backwards compatibility, validation rules, and evolution strategies for long-lived data formats. Use when defining a new API contract or data interchange format, adding fields to an existing schema without breaking consumers, migrating between schema versions, choosing between schema systems, or documenting data validation rules for automated enforcement.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Provides specific version compatibility notes for NativeWind and Tailwind CSS to prevent common installation errors.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a human explicitly asks for a full repository agent-compatibility pass returning a scored report with prioritized fixes. Not for tasks that require source or remote-system changes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Open Source License guidance, selection, compliance review, and drafting. Use this skill when users ask about choosing open source licenses, checking license compatibility, reviewing projects for OSS compliance, generating LICENSE/NOTICE files, or understanding specific license terms. Triggers include questions about MIT, Apache, GPL, BSD, LGPL, AGPL, copyleft, permissive licenses, license compatibility, SPDX identifiers, or any OSS licensing topic.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guard Yuzu's stable C plugin ABI, descriptor contract, and loader compatibility. Use when changing `sdk/include/yuzu/plugin.h`, `plugin.hpp`, plugin descriptors, `agents/core/src/plugin_loader.cpp`, built-in plugins, or plugin action surfaces that affect compatibility.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design and review durable REST, GraphQL, RPC, or event-facing API contracts. Use for public or shared API contracts, endpoint/schema consistency, compatibility, pagination, error semantics, and API documentation. Discovers existing consumers and conventions before recommending a style.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert-level medical device design covering regulatory pathways, design controls, biocompatibility, sterilization, risk management, and verification and validation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert-level biomaterials covering biocompatibility, metals, ceramics, and polymers for medical implants, surface modification, host response, and regulatory considerations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when reviewing a .NET pull request for breaking changes that may affect other microservice repositories. Detects cross-repo API, DTO, endpoint, EF entity, and NuGet-package breaks, and checks whether a compatible downstream PR already exists. Keywords: cross-repo impact, breaking change, microservice compatibility, downstream break, compatible PR, blast radius review, api compatibility, contract break, dto shape change, endpoint break.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Make a WooCommerce plugin HPOS-compatible (High-Performance Order Storage, default-on in WC 10.x) — declare via FeaturesUtil::declare_compatibility on before_woocommerce_init, replace $wpdb->postmeta / WP_Query order code with wc_get_orders + WC_Order::get_meta / update_meta_data, gate runtime branches on OrderUtil::custom_orders_table_usage_is_enabled, build admin hook names dynamically with OrderUtil::get_order_admin_screen (HPOS = woocommerce_page_wc-orders, legacy = shop_order). Use when scaffolding an order-touching plugin, auditing existing code for HPOS readiness, or fixing post-WC-10 silent breakage. Triggers on shop_order, get_post_meta with order context, FeaturesUtil, OrderUtil, custom_order_tables, before_woocommerce_init.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
新しい Web API / CSS の利用追加に対し、Baseline 状態とブラウザ互換性 / progressive enhancement の有無を suggestion で示す。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
リファクタリング（構造変更）と機能変更（behavior change）が同一 diff に混在していないかを識別し、structural change に対する external behavior preservation の証拠（テスト・型・静的解析）が揃っているかを diff-time で確認する。証拠不足のときは Characterization Test 追加を促すか question とする。DTO/公開 API の破壊的変更検出は api-compatibility、完了主張の反証や抽出リファクタの性能特性退行は refactor-claim-audit、新知識の命名・責務・境界への反映は knowledge-to-code-alignment、投機的抽象化・スコープ逸脱は altitude-generalization / fix-scope-integrity へ委譲する
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Windows アプリ開発 (WinUI 3 / Windows App SDK 2.x) のライフサイクル・ウィンドウ・ 通知・リソース・ウィジェット・配置。AppInstance, 単一インスタンス化, RichActivation, PowerManager、 AppWindow, AppWindowPresenter, OverlappedPresenter, タイトルバー, DisplayArea, Win32 相互運用、 AppNotification, Toast, PushNotificationManager, バッジ通知、ResourceManager, MRT, PRI, ローカライズ、 WidgetProvider, WidgetManager, アダプティブカード、MSIX, 自己完結型, DeploymentManager, PackageVolume, IPackageValidator (パッケージ検証), RuntimeCompatibilityOptions, SemVer, サポート期間, リリースチャネル。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Choosing and operating an HTTP API versioning strategy that doesn't break clients — Stripe's date-based pinned versions, the Deprecation/Sunset header pair (RFC 9745 + RFC 8594), URI vs header vs media-type approaches, and the version-transformer pattern. Grounded in Stripe's published architecture and IETF RFCs. NOT for GraphQL schema evolution, gRPC/Protobuf wire compatibility, database schema migrations, or library/SDK semver.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Documents minimum SDK/OS version requirements for all OneKey platforms. Use when checking platform compatibility, understanding deployment targets, verifying version requirements, or when user asks if their device can run the project. Triggers on minimum version, SDK version, API level, deployment target, platform requirements, iOS version, Android version, Chrome version, Electron version, can I run, environment check, device compatibility, check environment.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Skill manifest management for dotnet-harness. Tracks skill dependencies, conflicts, version compatibility, and provides validation and resolution tools. Triggers on: skill manifest, dependency resolution, skill compatibility, version conflicts, build manifest, validate dependencies.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Skill manifest management for dotnet-agent-harness. Tracks skill dependencies, conflicts, version compatibility, and provides validation and resolution tools. Triggers on: skill manifest, dependency resolution, skill compatibility, version conflicts, build manifest, validate dependencies.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
코드 리뷰 의견을 실제 코드와 지원 환경에 대조해 타당성을 확인합니다. 불명확한 내용을 정리하고 근거를 들어 답변하며, 수정 사항마다 테스트합니다.