「ownership」の検索結果

Build localized client XAML controls with correct lifecycle, culture refresh, resource references, ownership, and validation.

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

Spawn, initialize, replace, transfer, and delete entities without breaking lifecycle, transforms, containers, or ownership.

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

Review correctness, access, repository ownership, authority, localization, compatibility, resources, scope, and verification evidence.

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

Change projects, solution structure, CI, generated content, and packaging with repository-correct ownership and exact commands.

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

Port one complete feature family with provenance, current-API adaptation, repository ownership, localization, resources, and verification.

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

Plan, verify, implement, and deliver repository work through evidence-backed ownership and quality gates.

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

Write repository-consistent C# only after proving symbol access, ownership, and compatibility.

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

Implement complete SS14 features across ownership, ECS, networking, resources, localization, UI, and tests.

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

Move entities through containers, hands, slots, storage, equipment, and inventories without corrupting ownership or transforms.

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

Work with minds, sessions, bodies, roles, antagonists, objectives, ownership, and transfers safely.

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

Maintain entity references, ownership links, target relationships, deletion cleanup, and network-safe relation state.

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

Use this skill when the user asks about truck purchase financing, leasing options, factoring, fuel surcharge math, lease-purchase agreements, the total-cost-of-ownership (TCO) comparison between buying + leasing, and how owner-operators finance their first truck. Cover Section 179 + Bonus Depreciation tax treatment.

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

Use when a fleet manager or owner asks when to replace tractors and trailers, optimal trade cycle age, total cost of ownership analysis, residual value timing, dealer-vs-auction sale strategy, and how trade cycle affects driver retention and operating cost.

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

Use when a carrier asks about electric trucks — Tesla Semi, Freightliner eCascadia, Volvo VNR Electric, Peterbilt 579EV, range, charging, total cost of ownership, regulatory pushes (CARB ACT, ACF), incentives, infrastructure, depot vs en-route charging, and which routes/applications are EV-ready today.

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

Locate CCSPlayer_WeaponServices::DropWeapon in CS2 server.dll / libserver.so via IDA Pro MCP and emit a fresh, minimal-unique signature or offset for the WeaponPaints gamedata entry "CCSPlayer_WeaponServices::DropWeapon" (symbol CCSPlayer_WeaponServices_DropWeapon). This is a VIRTUAL function — emit the vtable slot, NOT a byte signature. Resolve the CCSPlayer_WeaponServices vtable via RTTI and identify the DropWeapon slot: the body takes a CBasePlayerWeapon handle/pointer, detaches it from the player, spawns the dropped weapon entity and transfers ownership. Verify by xrefs from weapon-drop commands (!!drop) and pickup logic. vtable slots commonly differ between platforms — never assume identical indices. Trigger: CCSPlayer_WeaponServices_DropWeapon, CCSPlayer_WeaponServices::DropWeapon

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

Explain an existing Convex app — data model + relationships, public vs internal functions, auth/ownership model, components, a request→data flow — read from the schema and function surface. Read-only.

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

Audit and harden a Convex app's authorization: identity-from-arg impersonation, missing per-document ownership checks, public queries leaking data by a client-supplied id, and writes into a parent/container the caller doesn't own. Scans for the 4 shapes, applies requireIdentity/requireOwner, verifies with tsc. TRIGGER on 'secure my app', 'audit auth/authz', 'who can access this data'. SKIP when there is no convex/ directory.

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

Use when adding or repairing Spark regression tests for asynchronous ownership, cancellation, persistence, restart recovery, or cross-surface projections. Not a coverage campaign, performance benchmark, source-text policy check, or full delivery review.

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

Rust のコードを書く・直す・レビューするときに使う。所有権、借用、Clone/Copy derive、文字列型 (`String`, `&str`, `Cow`, `'static str`) の選び方を、安易な複製や過剰な lifetime 固定に寄せず、実際のデータ所有者と呼び出し境界に合わせて判断するためのスキル。

Use this skill for internal i18n work in this repository. Covers locale ownership, provider wiring, lazy schema text contracts, and the maintenance surfaces that must stay in sync when package or playground translations change.

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

Maxim product turntable video — engineered for pre-ownership feeling via Endowment Effect + Visual Completion Bias. The structured rotation format that makes viewers mentally "hold" the product → purchase intent lift.

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

Govern Power Automate flows and Power Apps at scale using the FlowStudio MCP cached store. Classify flows by business impact, detect orphaned resources, audit connector usage, enforce compliance standards, manage notification rules, and compute governance scores — all without Dataverse or the CoE Starter Kit. Load this skill when asked to: tag or classify flows, set business impact, assign ownership, detect orphans, audit connectors, check compliance, compute archive scores, manage notification rules, run a governance review, generate a compliance report, offboard a maker, or any task that involves writing governance metadata to flows. Requires a FlowStudio for Teams or MCP Pro+ subscription — see https://mcp.flowstudio.app

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

Use when writing or applying a migration in site-os, adding a table or column, storing files, or when a migration fails with "must be owner of table" — covers the apply procedure, the postgres-ownership rule, money/rate units, and where files belong.

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

Evaluates and selects Threat Intelligence Platform (TIP) products based on organizational requirements including feed integration capability, STIX/TAXII support, workflow automation, analyst interface, and total cost of ownership. Use when conducting a TIP procurement, migrating between TIP solutions, or assessing whether the current TIP meets program maturity requirements. Activates for requests involving ThreatConnect, MISP, OpenCTI, Anomali, EclecticIQ, or TIP procurement decisions.

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