「inventory」の検索結果

Independent quality assurance for one SDD Composy task in qa_required: CA coverage, unit/integration/E2E, accessibility, responsiveness, environment, and evidence inventory, producing the QA report and requesting evidence_required. Use when a task finished execution — 'rodar o QA da task', 'testar a TASK-003', 'validar a implementação'. Do NOT use for code review (sdd-review), the final verdict (sdd-verify), or test runs outside an SDD task.

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

Inventory, archive, and summarize PWDEV Flow project history safely. Use when the user asks to find stale artifacts, archive completed work, clean the Flow workspace without deletion, or generate a changelog from verified history.

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

Apply DESIGN, canon, and modules to every page in the inventory, producing a deployable static HTML site. Three render branches (approved page, template-applied sibling, unique render). Per-page, incremental, idempotent, content-preserving by default.

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

Crawl an existing website (capped, multi-page) and seed stardust/current/ with PRODUCT.md, DESIGN.md, DESIGN.json, a per-page inventory, and the consolidated brand surface.

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

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

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

Azure API Center Management SDK for Python. Use for managing API inventory, metadata, and governance across your organization.

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

Azure API Center SDK for .NET. Centralized API inventory management with governance, versioning, and discovery.

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

Recipe for THE DOOR LAW (every record the UI names opens; every detected problem ships its fix) and THE INVENTORY LAW. Use before building or fixing a surface that names a record or flags a problem (cell, row, dialog, badge, warning, id, count), or on 'no link to X', 'why can't I click this', 'dead end', EntityRef, peek. NOT for page chrome (use core-route-headers).

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

Locate CCSPlayerPawn::SetModelFromClass in CS2 server.dll / libserver.so via IDA Pro MCP and emit a fresh, minimal-unique signature or offset for the WeaponPaints gamedata entry "CCSPlayerPawn::SetModelFromClass" (symbol CCSPlayerPawn_SetModelFromClass). Shortlist via callers of CBaseModelEntity::SetModel inside pawn model-selection code: this variant takes the pawn's class model. The body resolves a cached model precache handle from the player class and calls SetModel. Distinguish from SetModelFromLoadout by the ABSENCE of loadout/inventory item lookups in the call chain. Trigger: CCSPlayerPawn_SetModelFromClass, CCSPlayerPawn::SetModelFromClass

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

Find and identify the CCSPlayer_ItemServices_GiveNamedItem virtual function, the CCSPlayer_WeaponServices_Weapon_GetSlot helper, and the CBasePlayerPawn_RemovePlayerItem helper in CS2 binary using IDA Pro MCP. Use this skill when reverse engineering CS2 server.dll or libserver.so to locate GiveNamedItem by RTTI-walking the CCSPlayer_ItemServices vtable, then to locate the other two by decompiling the already-known CCSPlayer_ItemServices_GiveDefaultItems anchor and matching its callees' argument shapes and inventory-slot bookkeeping semantics. Trigger: CCSPlayer_ItemServices_GiveNamedItem, CCSPlayer_WeaponServices_Weapon_GetSlot, CBasePlayerPawn_RemovePlayerItem

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

需要予測、安全在庫最適化、補充計画、プロモーション効果推定のための体系化された 専門知識。数百のSKUを管理する15年以上の経験を持つデマンドプランナーの知見に 基づく。予測手法の選択、ABC/XYZ分析、季節変動管理、ベンダー交渉フレームワーク を含む。需要予測、安全在庫設定、補充計画、プロモーション管理、在庫水準最適化 時に使用。

Azure API Center SDK for .NET. Centralized API inventory management with governance, versioning, and discovery.

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

Azure API Center Management SDK for Python. Use for managing API inventory, metadata, and governance across your organization.

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

Discovers all projects in a .NET solution, classifies each for Oracle-to-PostgreSQL migration eligibility, and produces a persistent master migration plan. Use when starting a multi-project Oracle-to-PostgreSQL migration, creating a migration inventory, or assessing which .NET projects contain Oracle dependencies.

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

Shopify Admin & Storefront GraphQL APIs via curl. Products, orders, customers, inventory, metafields.

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

Apply DESIGN, canon, and modules to every page in the inventory, producing a deployable static HTML site. Three render branches (approved page, template-applied sibling, unique render). Per-page, incremental, idempotent, content-preserving by default.

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

Crawl an existing website (capped, multi-page) and seed stardust/current/ with PRODUCT.md, DESIGN.md, DESIGN.json, a per-page inventory, and the consolidated brand surface.

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

Discover a single-page-app's hidden backend API from its public JS bundle, then test that API for broken access control / missing authentication. One of the highest-yield web plays in modern recon — SPAs ship their entire backend route map to the browser, and the API behind them is frequently missing the auth middleware the login page implies. Built from an authorized engagement where this play found an unauthenticated financial API that an ASM scan reporting hundreds of 'Criticals' completely missed. Use whenever a target serves a JS-heavy SPA (React/Vue/Angular/Next), an 'app'/'console'/'dashboard'/'portal' subdomain, or any `*api*` host shows up in recon. Leaked build artifacts (source maps / .env / .git / asset-manifest) are owned by hunt-source-leak; API version-inventory and behavioral diffing by hunt-shadow-api; this skill owns mapping a live SPA's backend routes from its JS bundle and testing them for broken access control / missing auth.

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

Guides the practical path from 'we have no design system' or 'we have a mess' to a real, functional design system. Component inventory, design token extraction, headless UI adoption (Radix, React Aria, Headless UI), migration order of operations, and the assessment-to-rollout pipeline. Activate on 'design system from scratch', 'bootstrap design system', 'no design system', 'design system migration', 'headless UI adoption', 'component audit', 'design token extraction', 'design system strategy'. NOT for building specific components once a system exists (use design-system-creator), not for generating token files/configs (use design-system-generator).

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