「conflict」の検索結果

Produce only the assigned result, protect other owners' work, run the listed checks, and report an exact conflict instead of expanding scope.

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

Implement, review, or improve SwiftUI gesture handling. Use when adding tap, long press, drag, magnify, or rotate gestures, composing gestures with simultaneously/sequenced/exclusively, managing transient state with @GestureState, resolving parent/child gesture conflicts with highPriorityGesture or simultaneousGesture, building custom Gesture protocol conformances, or migrating from deprecated MagnificationGesture to MagnifyGesture or using the newer RotateGesture.

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

Implement, review, or improve CloudKit and iCloud sync in iOS/macOS apps. Use when working with CKContainer, CKRecord, CKQuery, CKSubscription, CKSyncEngine, CKShare, NSUbiquitousKeyValueStore, or iCloud Drive file coordination; when syncing SwiftData models via ModelConfiguration with cloudKitDatabase; when handling CKError codes for conflict resolution, network failures, or quota limits; or when checking iCloud account status before performing sync operations.

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

Git operations: commits, branches, PRs, and conflict resolution

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

Scaffold and deploy Cloudflare Workers with Hono routing, Vite plugin, and Static Assets. Describe project, scaffold structure, configure bindings, deploy. Use whenever the user wants to create a Worker project, set up Hono on Cloudflare, configure D1 / R2 / KV / Queues bindings, or troubleshoot Worker export syntax, API route conflicts, HMR issues, or deployment failures.

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

Audit and enforce the core/client boundary in multi-client projects. Detects where shared platform code is tangled with client-specific code, finds hardcoded client checks, config files that replace instead of merge, scattered client code, migration conflicts, and missing extension points. Produces a boundary map, violation report, and refactoring plan. Optionally generates FORK.md documentation and restructuring scripts. Triggers: 'fork discipline', 'check the boundary', 'is this core or client', 'platform audit', 'client separation', 'fork test', 'refactor for multi-client', 'clean up the fork'.

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

Set up Tailwind v4 + shadcn/ui themed UI with dark mode. Install deps, configure CSS variables via @theme inline, wire dark mode toggle, verify. Use whenever the user mentions Tailwind v4, setting up Tailwind theming, shadcn/ui colours, dark mode, or troubleshooting colours not working, tw-animate-css errors, @theme inline conflicts, @apply breaking after upgrade, or v3 → v4 migration issues.

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

Build and maintain one global mathematical symbol and unit table from the problem frame and active method cards, resolving cross-subquestion conflicts before code or paper work.

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

Diagnose and remediate cluster-wide HyperPod (EKS or Slurm) problems — creation / deployment failures (CloudFormation, EFA health check, lifecycle scripts, capacity), EKS access, node replacement, CloudFormation nested-stack errors, post-maintenance rollback state, dangling nodes, autoscaler conflicts. Includes `--validate` pre-flight. Read-only.

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

C-suite orchestration that routes founder questions to the right advisor role(s) and runs multi-role board meetings. Use when coordinating executive decisions, routing strategic questions, or resolving cross-department conflicts.

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

Channel economics: design and analyze the financial structure of go-to-market channels. Use when picking a channel mix, modeling partner margin or TCO, designing partner tiers and rebates, or analyzing channel conflict.

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

Use when seeing WebSocket errors like "Invalid frame header", "RSV1 must be clear", or "WS_ERR_UNEXPECTED_RSV_1" - covers multiple WebSocketServer conflicts, compression issues, and raw frame debugging techniques

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

Audit or generate XML sitemaps: limits, lastmod, status codes, robots conflicts. "audit our sitemap"

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

When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For choosing attribution models, comparing multi-touch/MMM/incrementality, or reconciling conflicting numbers across tools, see attribution. For A/B test measurement, see ab-testing.

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

When the user wants to figure out which marketing actually drives conversions and revenue, choose or interpret an attribution model, or reconcile conflicting numbers across tools. Also use when the user mentions "attribution," "attribution model," "first-touch vs last-touch," "multi-touch," "which channel drives revenue," "what's my real CAC," "my dashboards disagree," "Google/Meta says X but GA says Y," "media mix model," "MMM," "incrementality," "geo lift," "holdout test," "how did you hear about us," "self-reported attribution," "dark social," or wants to instrument attribution themselves — "stitch my bookings to their source," "SavvyCal/Calendly attribution," "close the identify gap," "track conversions on a third-party domain," "first-party / self-hosted attribution." For event tracking setup and UTMs, see analytics. For ad-platform pixels/CAPI, see ads. For pipeline and CRM revenue reporting, see revops. For the AI-search attribution blind spot, see ai-seo.

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

Pick the right LLM for CONTRACT REVIEW — reviewing an existing agreement for risk, deviations from standard, missing protections, and internal contradictions, and proposing redlines. Vendor-neutral routing grounded in mid-2026 legal benchmarks. Contract review is a COMPOSITE skill (extraction + reasoning + redlining + conflict-detection), so this routes by the dominant sub-task. Asks up to 4 quick questions (cost, speed, accuracy/stakes, privacy/jurisdiction/ language), then recommends a primary model + fallback + what to avoid + what a human must verify. Use when someone asks "which model to review this contract / NDA / MSA", "best AI to redline", "route this contract review", or is about to review an agreement without a fixed model.

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

Run an attorney-facing knockout/availability trademark search across the United States and Canada. Use whenever a user (founder, client, or attorney) asks whether a brand, mark, name, logo, slogan, or product name is "available," "free to use," "clearable," or "already taken" — or asks Claude to "search the trademark register," "check USPTO," "check CIPO," "do a knockout search," "clearance search," "availability search," or "see if [mark] is trademarked." Trigger even when the user phrases it casually ("can I call my company X?", "is this name taken?"). Covers federal USPTO (TESS/TSDR), federal Canada (CIPO), common-law/web/state, and WIPO Madrid international. Output is a knockout availability memo with green/yellow/red verdict for attorney review. Includes professional-responsibility gating (AI-use disclosure, conflict check, scope confirmation) before substantive analysis. Not legal advice — produces work product for attorney sign-off.

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

Use this skill whenever a lawyer or mediator needs help analyzing a dispute for mediation purposes. This includes: reviewing case materials (pleadings, contracts, correspondence, evidence) to identify issues in dispute, summarizing each party's position and interests, conducting legal analysis of the key issues, proposing mediation strategies or settlement directions, and preparing for mediation sessions. Trigger this skill when the user mentions 'mediation', 'dispute analysis', 'settlement', 'dispute resolution', 'identify issues in dispute', 'party positions', 'mediation brief', 'case analysis for mediation', 'ADR', 'mediation preparation', 'caucus strategy', 'settlement options', or any request to analyze a conflict between two or more parties with the goal of finding resolution. Also trigger when the user uploads case files and asks for a structured breakdown of who wants what, what the core disagreements are, or how the case might settle. Even if the user doesn't explicitly say 'mediation', trigger when the context involves analyzing opposing positions in a dispute with a resolution-oriented (rather than litigation-oriented) goal.

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

Analyzes how multiple regulations interact for a specific product, service, or business model. Identifies where obligations overlap, reinforce, complement, duplicate, or conflict; builds a priority matrix; produces an integrated compliance timeline; and estimates the total compliance burden. Use when (1) scoping a new product or service against the full regulatory landscape before launch, (2) conducting M&A due diligence on a target's multi-regulation exposure, (3) building a strategic compliance roadmap where single-regulation analyses miss the interactions, (4) advising on complex situations where regulations touch the same conduct from different angles, or (5) estimating budget and resourcing for multi-regulation compliance. Primary coverage of EU digital regulation (GDPR, Data Act, AI Act, CRA, NIS2, DORA, DMA, DSA, ePrivacy) and national implementations; the framework extends to any jurisdiction where overlapping regulatory regimes apply to the same activity.

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

Structured debugging methodology — use before proposing fixes for any error or failure. Covers: code bugs, build errors, deploy failures, config conflicts, dependency issues, infra problems. Also use when previous fix attempts failed or root cause is unclear.

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

Design a RULER emotional literacy sequence for recognising, understanding, labelling, expressing, and regulating emotions. Use when students struggle with emotional regulation, conflict, or anxiety.

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

Generates an offline operation queue with persistence, automatic retry on connectivity, and conflict resolution. Use when user needs offline-first behavior, queued mutations, or pending operations that sync when back online.

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

Generate CloudKit sync infrastructure using CKSyncEngine with conflict resolution, sharing, and account monitoring. Use when adding iCloud sync to an iOS/macOS app.

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

Automatically merge open PRs that have passing CI, no blocking reviews, and no conflicts

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