「utility」の検索結果

Perform visual similarity search for utility model patents using an image URL, with filtering by country, legal status, date ranges, and assignee. Supports utility model patents only (type U) with shape-only or shape+pattern+color matching models. Triggered when users mention utility patent image search, utility model patent search, utility patent infringement check, product structure patent search, or utility model visual search. Even if the user does not explicitly mention "utility patent," this skill should be triggered whenever the need involves searching for similar utility model patents through an image. For design patents, use ecommerce.Nexscope-patent-image-search instead.

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

Detect and search for similar utility/invention patents based on product information. Trigger when users mention utility patent detection, patent infringement risk, patent similarity search, patent screening, invention patent search, patent risk assessment, TRO (Temporary Restraining Order) risk analysis, utility patent, invention patent detection, patent infringement risk, patent search, TRO risk, Ruiguan. Even if the user does not explicitly say "utility patent", trigger this skill whenever their need involves checking whether a product may infringe existing utility/invention patents before selling in a target market.

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

Build a production behavior-tree runtime (Blackboard, action/condition leaves, sequence/selector/parallel composites, decorators) and a Utility AI system (response curves — linear, exponential, sigmoid, quadratic — considerations, and action evaluators), plus hybrid BT-drives-Utility agents. Use when implementing a reusable behavior-tree or utility-based decision system, or tuning enemy/NPC decisions beyond a simple FSM, or when the user mentions behavior tree, blackboard, decorator, selector, sequence, tick status, utility AI, response/scoring curve, or consideration. For choosing between FSM/BT/steering or for pathfinding, use game-ai; for Unreal's BehaviorTree/Blackboard assets, use unreal-behavior-trees.

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

Use this skill to configure a Lightning Service Console app in Salesforce — Console Navigation (split view), workspace tabs and subtabs, the utility bar with Omni-Channel, Macros and History, Quick Text, keyboard shortcuts, and navigation rules per object. Trigger keywords: Service Console, console app, workspace tabs, subtabs, utility bar macros, Omni-Channel utility, split view, Quick Text, console navigation rules, keyboard shortcuts service console, navType Console, workspaceConfig mappings, WorkspaceMapping fieldName, UtilityBar FlexiPage, tabLimitConfig, listPlacement, MacroInstruction, QuickText Channel multipicklist, isNavTabPersistenceDisabled. NOT for opening or refreshing console tabs from code — use lwc/lwc-console-workspace-api. NOT for Omni-Channel routing setup — use admin/omni-channel-routing-setup.

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

Create and configure Lightning apps in Salesforce Setup, add navigation items and tabs to apps, configure utility bar components, and control app visibility by profile or permission set. Also covers the deployable metadata behind all of that: CustomApplication, CustomTab, and the FlexiPage of type UtilityBar. Trigger keywords: Lightning app, App Manager, custom tab, navigation bar, utility bar, app visibility, CustomApplication, tabs element, standard- tab prefix, defaultLandingTab, formFactors, navType, uiType, workspaceConfig, applicationVisibilities, tabSettings, AppDefinition, TabDefinition, AppTabMember, app deployed but not visible. NOT for console navigation, workspace tabs and subtabs - use admin/service-console-configuration. NOT for the record page or app page inside the app - use admin/lightning-app-builder-advanced.

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

Provides patterns for testing utility classes, static methods, and helper functions. Validates pure functions, null handling, edge cases, and boundary conditions. Generates AssertJ assertions and @ParameterizedTest for string utils, math utils, validators, and collection helpers. Use when testing utils, test helpers, helper functions, static methods, or verifying utility code correctness.

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

Expert in designing and implementing intelligent game AI systems including behavior trees, finite state machines, GOAP, utility AI, pathfinding, steering behaviors, and perception systems. Specializes in creating believable, performant NPC behaviors that enhance player experience. Use when "game AI, NPC behavior, behavior tree, state machine for game, enemy AI, pathfinding, A* algorithm, navmesh, steering behavior, GOAP, utility AI, AI perception, combat AI, companion AI, boss AI, crowd simulation, flocking, game-ai, behavior-trees, pathfinding, npc, state-machines, goap, utility-ai, steering, perception" mentioned.

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

新しい機能を実装する前に、既存コードやnpm・PyPIのパッケージ、MCP serversなどを調べます。候補を比較し、採用・拡張・自作の判断につなげるスキルです。

• 機能追加前に既存の解決策を調べたいとき
• 依存パッケージの導入前の比較
• 外部連携に使えるツールの調査

Utility

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

Create uncontested market space using value innovation instead of competing head-to-head. Use when the user mentions "blue ocean", "red ocean", "strategy canvas", "ERRC framework", "value innovation", "non-customers", "buyer utility map", "the market is too crowded", "how do we stand out", or "escape the price war". Also trigger when exploring a new market category, or finding underserved or non-customers. Covers the Four Actions Framework, Six Paths, buyer utility map, and value-cost trade-offs. For real strategy formulation and bad-strategy detection, see good-strategy-bad-strategy. For tech adoption strategy, see crossing-the-chasm. For product positioning, see obviously-awesome.

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

Quick reference for Tailwind CSS utility patterns, responsive design, and configuration. Triggers on: tailwind, utility classes, responsive design, tailwind config, dark mode css, tw classes.

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

Perform visual similarity search for design patents using an image URL, with filtering by country, legal status, date ranges, Locarno classification, and assignee. Supports design patent types only (type D). Triggered when users mention patent image search, design patent search, search patent by image, visual patent lookup, patent similarity detection, patent image matching, or design patent infringement check. Even if the user does not explicitly mention "patent image," this skill should be triggered whenever the need involves searching for similar design patents through an image. For utility model patents, use ecommerce.Nexscope-utility-patent-image-search instead.

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

Expert guide for TypeScript 5.8+ advanced type system, strict mode, generics, utility types, branded types, inferred type predicates, isolated declarations, and type-safe architectural patterns / Panduan ahli untuk sistem tipe TypeScript 5.8+, mode strict, generics, utility types, branded types, inferred type predicates, isolated declarations, dan pola arsitektur type-safe.

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

Use when a task needs the judgment of an Energy Auditor — running a blower-door/duct-leakage diagnostic sequence on a home or light-commercial building, testing combustion appliances for worst-case backdraft risk before recommending air sealing, reconciling utility billing history against walkthrough findings, ranking retrofit measures by savings-to-investment ratio (SIR) for a weatherization or utility rebate program, or writing the prioritized scope of work an install crew executes without the auditor on site. Distinct from an energy-engineer (industrial/commercial capital planning, IPMVP measurement and verification, calibrated simulation) — this role owns the field diagnostics and the residential/light-commercial audit-to-scope handoff.

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

Use when designing or customizing industry-specific guided processes in Salesforce Industries clouds: insurance claims lifecycle (FNOL through closure), telecom order management decomposition, and utility service request workflows. Trigger keywords: FNOL process design, claims OmniScript customization, Industries order decomposition workflow, utility service order design, insurance claim lifecycle stages, telecom commercial-to-technical order flow. NOT for the Industries object model — use architect/industries-data-model. NOT for Insurance Cloud licensing and policy architecture — use architect/insurance-cloud-architecture.

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

Use when writing TypeScript code, fixing type errors, or configuring strict type safety. Auto-activates on .ts/.tsx files. Covers null handling, utility types, and ESLint.

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

Openapi utility services - real-time currency exchange rates, HTML-to-PDF conversion (renders JavaScript), .it domain registration/management, and managed RAG (retrieval-augmented generation over your documents). Use for these one-off utility tasks.

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

Turns a vague "what should we do about X" into a scored decision - explicit actions, an explicit unknown, an explicit prior, and one utility scale - then picks by maximum expected utility and checks the result for framing effects. Use when facing a choice between options under uncertainty, when a decision has stalled in circular debate, when someone asks "should we do A or B", or before writing any decision record, strategy memo, or roadmap commitment.

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

Create consistent, scalable design systems using Tailwind CSS utility classes with custom themes, design tokens, and responsive design patterns. Use when building design systems, implementing custom themes, creating reusable utility patterns, configuring Tailwind theme extensions, implementing dark mode, building responsive layouts, creating design tokens, using arbitrary values, or establishing consistent spacing and typography scales.

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

This skill should be used when the user asks to "このファイルを変えたら何が壊れる？", "what depends on this function", "影響範囲を調べて", "show me what imports this module", or wants to understand the blast radius before modifying a shared utility, exported type, or public API. Traces import/require references up to two levels deep and lists affected test files.

工場やオフィスの電力・天然ガス調達を、料金体系、使用量、契約条件から検討するスキル。供給会社の比較、ピーク料金対策、再生可能エネルギー契約や予算作成を支援します。

• 複数拠点のエネルギー見積もり比較
• 料金プランとピーク料金の見直し
• 再生可能エネルギー契約・証書の評価

Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.

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

Use when reviewing a CSS architecture for specificity issues, setting up a design system, or migrating a large codebase from utility-first to a layered architecture.

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

Use when reviewing utility functions, component props, or template strings that format numbers, prices, or dates to check whether Intl APIs are used correctly.

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