「usage」の検索結果

Evolutionary file renaming with wrapper files. Enables renames without hard breaks — references are organically updated through usage.

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

Evolutionary file renaming with wrapper files, plus the terse MOVED-stub standard for whole folder/file moves. Enables renames without hard breaks — references are organically updated through usage.

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

Use Cua's cloud sandboxes via cua.ai. Requires CUA_API_KEY. Cloud sandboxes are isolated VMs run by trycua with billing per usage. Use when the user wants no local Docker/QEMU, wants Windows/macOS guests without Apple Silicon, or explicitly asks for cloud.

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

Use Gemini as a third external reviewer alongside two other vendors: diff review with an APPROVE or REQUEST_CHANGES verdict, and QA-breaker duty in the post-build test ritual. Headless over REST with a CLI fallback, and verdicts go to a shared usage journal. Triggers: "/gemini review", "gemini opinion on this diff".

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

Make a WooCommerce plugin HPOS-compatible (High-Performance Order Storage, default-on in WC 10.x) — declare via FeaturesUtil::declare_compatibility on before_woocommerce_init, replace $wpdb->postmeta / WP_Query order code with wc_get_orders + WC_Order::get_meta / update_meta_data, gate runtime branches on OrderUtil::custom_orders_table_usage_is_enabled, build admin hook names dynamically with OrderUtil::get_order_admin_screen (HPOS = woocommerce_page_wc-orders, legacy = shop_order). Use when scaffolding an order-touching plugin, auditing existing code for HPOS readiness, or fixing post-WC-10 silent breakage. Triggers on shop_order, get_post_meta with order context, FeaturesUtil, OrderUtil, custom_order_tables, before_woocommerce_init.

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

Picks the right WordPress storage primitive for plugin data: options, user/post/term/comment meta, transients, site options, site transients, or custom tables. Covers grouped settings, autoload management, transient TTL rules, serialized/JSON blob trade-offs, multisite storage caveats, and naming conventions. Use when scaffolding settings, choosing persistence for plugin-owned data, or auditing update_option/get_option/get_post_meta/set_transient/autoload usage.

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

Design and review Action Scheduler jobs in WordPress plugins using Action Scheduler 3.9.x public APIs - async, single, recurring, and cron-expression actions; action_scheduler_init load timing; hook/args/group naming; unique and priority parameters; idempotent callbacks; chunked workloads; activation/deactivation cleanup; WooCommerce-bundled or standalone dependency usage; admin and WP-CLI debugging; queue runner limits; and safe operational troubleshooting. Use when a plugin schedules background jobs with as_enqueue_async_action, as_schedule_single_action, as_schedule_recurring_action, as_schedule_cron_action, as_get_scheduled_actions, or integrates with WooCommerce background queues.

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

Review and implement WordPress query-cache usage on WP 6.9+, especially direct interaction with query cache groups now using salted cache helpers. Covers wp_cache_get_salted, wp_cache_set_salted, wp_cache_get_multiple_salted, wp_cache_get_last_changed, affected query groups like post-queries, term-queries, user-queries, comment-queries, site-queries, and why plugins should usually use WP_Query APIs instead of writing query cache entries directly. Use when optimizing expensive reads, persistent object cache behavior, or cache invalidation bugs.

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

Manage NV oOS Pro Schedules — create, update, delete, list, dry-run, view run history, and plan schedules from workflows. Covers all 7 Pro Schedule Manager MCP tools with usage patterns, cross-references, and operational troubleshooting. Use when creating recurring tasks, debugging schedule failures, pausing vs deleting schedules, converting Action Scheduler jobs to managed schedules, or bridging workflow outputs to timed execution.

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

Generates client SDK code, API wrapper libraries, request/response models, and language-specific usage patterns for any REST API.

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

Automate Anthropic Admin tasks via Rube MCP (Composio): API keys, usage, workspaces, and organization management. Always search tools first for current schemas.

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

Build AI phone agents with AgentPhone API. Use when the user wants to make phone calls, send/receive SMS, manage phone numbers, create voice agents, set up webhooks, or check usage — anything relate

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

Use when the user asks to "draft an influencer contract", "review these agreement terms", or "build a partnership template"; produces a full influencer agreement framework (scope, compensation, usage rights, exclusivity, FTC disclosure), a clause-by-clause review with red flags, and a negotiation cheat sheet. Not for outreach negotiation before a deal exists — use outreach-manager. 达人合同/合作协议条款审查

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

Detects N+1 query patterns (relation access inside loops without eager loading), full-table get()/all() loads, and unsafe chunk()/cursor() usage in Laravel Eloquent code.

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

Detect i18n/locale keys that are removed from source but remain in locale files, or keys added to locale files without source usage.

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

Check task processing statistics to see how much data and how many docs are moving. Use when checking throughput, diagnosing a stalled task, verifying data movement, or reporting on task activity. Use when user says "is data flowing", "how much data", "check throughput", "how many documents", "task not processing", "data not arriving", "stats", "bytes processed", "stalled capture", "no data in destination", "data volume", "task report", "usage report", or "how much data did we process".

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

Master ShellCheck static analysis configuration and usage for shell script quality. Use when setting up linting infrastructure, fixing code issues, or ensuring script portability.

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

Convert a regular/single-user app into a multi-tenant SaaS — add authentication, organizations/teams, role-based permissions (RBAC), plans & billing (Stripe / HYP-היפ / license keys / usage metering), invites and onboarding. Use when the user wants to "turn this into a SaaS", "add login/orgs/teams", "add plans and payments", "add user roles/permissions", "make this multi-tenant", "הפוך לסאאס", "להוסיף התחברות / ארגונים / הרשאות / מסלולים ותשלום".

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

Control FriendlyBet operating cost, free-tier viability, provider/API cost, GitHub Actions/Supabase/Vercel usage, documentation hygiene, company memory updates, playbook maintenance, and skill validation. Use when evaluating cost, operational burden, tooling, internal docs, company memory, or whether agent profiles should become full skills.

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

Govern FriendlyBet agent values, professional standards, anti-hallucination behavior, truthfulness, risk reporting, AI resource discipline, feedback loops, skill improvement, performance reviews, decision-rights hygiene, and team quality. Use when creating, reviewing, promoting, correcting, or retiring agents; reducing hallucinations or mistakes; reviewing AI/tool usage; handling agent incidents; or aligning work with Eyal's philanthropic user-first approach.

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

Reduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.

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

Use when working with Cube Dev — cube.dev semantic layer management — monitor deployments, data models, pre-aggregations, query performance, and API health. Use when inspecting cube schemas, debugging slow queries, reviewing pre-aggregation builds, or auditing API usage.

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

Use when working with Descope — descope authentication and identity management platform covering users, tenants, access keys, flows, and audit logs. Use when analyzing user authentication patterns, monitoring tenant health, reviewing access key usage, managing Descope flows and roles, or auditing login activity.

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

Use when working with Convex — convex backend platform management covering project inventory, table schemas, function deployments, scheduled job status, index configuration, environment variable auditing, and usage metrics. Use for comprehensive Convex project health and resource optimization.

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