「routing」の検索結果

Use when working with Celery — celery worker management, task monitoring, queue routing, Flower dashboard analysis, and task result tracking.

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

Use when working with Gcp Cloud Logging — google Cloud Logging log analysis, log-based metrics, sink management, exclusion filters, and log routing configuration via gcloud CLI.

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

Use when working with Azure Front Door — azure Front Door routing rules, WAF policy management, health probe configuration, cache management, and CDN analytics via Azure CLI.

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

Use when working with Mariadb — mariaDB Galera cluster status, MaxScale routing, ColumnStore engine analysis, performance schema tuning, and replication health.

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

Use when working with Aws Eventbridge — aWS EventBridge event bus management, rule analysis, target health monitoring, and schema registry exploration. Covers event pattern matching, rule invocation metrics, dead-letter queue analysis, cross-account event routing, and event replay.

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

Fertig, Damir! ✅ Das 3-Tier-Routing ist eingerichtet und **live verifiziert**.

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

Latest research insight: Adaptive LLM routing under budget constraints

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

Operate as an agentic engineer using eval-first execution, decomposition, and cost-aware model routing.

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

Write, configure, and deploy Netlify Edge Functions (Deno runtime at the network edge) in TypeScript/JavaScript. Use when adding request/response manipulation at the edge — auth middleware, geolocation redirects, A/B testing and personalization, content localization, redirects/rewrites, SSR at the edge, or transforming responses — or when configuring path routing, response caching, or edge error handling. Triggers on tasks like "add auth middleware", "geo-based redirect", "A/B testing at the edge", "rewrite requests", or editing files in netlify/edge-functions.

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

Write, configure, and deploy Netlify serverless functions in TypeScript, JavaScript, or Go. Use this when adding an API endpoint or backend route, adding a contact form handler, wiring auth or Identity signup/login hooks, building streaming or AI-proxy responses, scheduling cron jobs, running long background jobs (batch processing/scraping), reacting to deploy or form events, setting up rate limiting or region/memory config, or reading environment variables and secrets inside a function. Covers file locations, the Request/Context/Response handler shape, path routing, config options, and local testing with netlify dev.

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

Map tasks to specialist agents. Use when choosing which agent for a job, comparing agent capabilities, or routing to React/Next.js/Playwright/docs/code-quality experts. Keywords: which agent, best agent for this, delegate to expert, agent capability mapping.

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

Expert en API gateways (Kong, Traefik, nginx, rate limiting, auth, routing, plugins)

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

Agent Orchestrator v2 IA — Expert en orchestration multi-agents (tool routing, mémoire, planning, ReAct, orchestration de workflows IA)

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

Measurement-driven model router for Claude Code. Routes Haiku/Sonnet/Opus per task class, logs every routed task with real $ numbers, and A/B tests cheaper tiers before you trust the savings.

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

Next.js App Router principles. Server Components, data fetching, routing patterns.

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

LLM Agent engineering: pattern selection (12-mode matrix), data simulation, convergence iteration. Covers intent routing, function calling, ReAct, MCP, prompt chaining, guardrails, evaluation.

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

Diagnose App Store submission blockers and operate review health with asc, including readiness validation, repair routing, status monitoring, cancellation, and retry decisions. Use when validation fails, a version is not in a valid state, review status is unclear or stuck, or a failed submission must be repaired and retried. For staging, upload, publication, and submission execution, use asc-release-flow.

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

Implement SwiftUI navigation patterns including NavigationStack, NavigationSplitView, sheet presentation, tab-based navigation, and deep linking. Use when building push navigation, programmatic routing, multi-column layouts, modal sheets, tab bars, universal links, or custom URL scheme handling.

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

When the user wants to set up, optimize, or scale Apple Search Ads (ASA) campaigns — including keyword bidding, match types, campaign structure, Creative Product Sets, CPP routing, and ROAS optimization. Use when the user mentions "Apple Search Ads", "ASA", "Search Ads", "Search tab ads", "Today tab ads", "CPT", "TTR", "Search Match", "exact match", "broad match", "CPP in ads", "ASA bidding", or "Search Ads budget". For Meta/Google UAC/TikTok paid UA, see ua-campaign.

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

Create media playback experiences using AVKit. Use when adding video players with AVPlayerViewController, enabling Picture-in-Picture, routing media with AirPlay, using SwiftUI VideoPlayer views, configuring transport controls, displaying subtitles and closed captions, or integrating AVFoundation playback with system UI.

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

Support audio accessory features like automatic switching using AudioAccessoryKit. Use when implementing automatic audio routing for connected accessories, managing audio accessory sessions, registering device capabilities and placement, providing connected audio source identifiers, or configuring audio accessories connected to iOS devices.

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

Choose OpenRouter models and routers, query live catalog data, use structured outputs and batch inference, and debug routing with metadata. Use when working with OpenRouter APIs, openrouter/auto, openrouter/free, model discovery, pricing, providers, batch jobs, or structured JSON responses.

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

Use when: ticket lifecycle, state transitions, ready for QA, changes requested, QA passed, role-based workflow policy, Developer to QA handoff, or relay routing across delivery agents.

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

Use when: remote team, delegate, delegated lane, delegated implementation, delegated QA, or non-sensitive ticket routing to the remote team's implementation lane.

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