'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 등을 조사합니다. 후보를 비교해 채택, 확장, 조합 또는 직접 개발할지 판단하도록 돕습니다.

• 기능 추가 전에 기존 해결책 조사
• 의존성 추가 전 패키지 비교
• 외부 서비스 연동 도구 조사

Review conflicting CSS rules and organize styles with cascade layers, explicit groups that control override order. Define layers for resets, base styles, components, and utilities to make large stylesheets easier to reason about and maintain.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigate recurring CSS override conflicts
• Define style priority for a design system
• Migrate utility-first CSS into a layered structure

Process large email, document, and transcript archives by routing items to AI models according to their importance. Rule-based privacy checks run before model calls, while extracted information becomes linked knowledge pages with progress checkpoints.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Extract useful information from large email archives
• Organize decisions and advice from meeting transcripts
• Route reports to suitable models by importance

Design and review TypeScript code with safer types and readable structures. Covers strict compiler settings, generics for reusable typed code, type guards for checking unknown values, and utility types for transforming existing definitions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review TypeScript strict mode settings
• Design reusable functions with generics
• Replace unsafe assertions with type guards

Develop patent application drafts from an invention description, covering prior art searches, claims that define protection scope, specifications, and examiner-style review. Compile documents for China, the United States, or Europe, with human checkpoints throughout.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turning an invention description into application drafts
• Assessing prior art before drafting claims
• Preparing patent drafts for CN, US, or EP

Control which GSD skills are available without reinstalling. Switch preset profiles, enable or disable groups of skills, inspect the active selection and estimated token usage, or restore the profile chosen at installation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Switching the available skills for a particular workflow
• Hiding groups of skills that are not currently needed
• Checking enabled skills and estimated token usage

Check whether Apache Hudi table maintenance is keeping pace with incoming data. Runs a read-only utility, interprets its JSON report, and explains unhealthy or skipped checks with concrete next steps.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking Hudi table maintenance health
• Investigating delayed compaction or cleaning
• Finding why the active timeline keeps growing

Configure UnoCSS and style interfaces with utility classes, small reusable styling instructions. Use project settings to define custom rules, shortcuts, themes, and presets for features such as icons, typography, and attribute-based styling.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding UnoCSS to a Vite or Nuxt project
• Combining repeated styles into shortcuts
• Defining shared colors and responsive breakpoints

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.