「concurrency」の検索結果

Write safe concurrent Go code with goroutines, channels, and context. Use when implementing concurrency with goroutines, channels, or context in Go.

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

Use when you need to design, review, or improve REST APIs with Quarkus REST (Jakarta REST) — including resource classes, HTTP methods, status codes, request/response DTOs, Bean Validation, exception mappers, optional runtime OpenAPI exposure (SmallRye), contract-first generation from OpenAPI, content negotiation, pagination, sorting and filtering, API versioning, idempotency (Idempotency-Key), optimistic concurrency (ETag / If-Match), HTTP caching (Cache-Control), API deprecation (Sunset / Deprecation headers), RFC 7807 Problem Details, ISO-8601 for time in contracts, and security-aware boundaries. This should trigger for requests such as Review or improve JAX-RS resources in a Quarkus project; Design HTTP APIs with validation and error handling on Quarkus; Add API versioning, idempotency, ETag concurrency, or deprecation headers; Implement pagination, sorting, or RFC 7807 Problem Details error responses; Improve Quarkus REST resources and exception mappers. Part of Plinth Toolkit

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

Async Python patterns via asyncio and aiohttp for I/O-bound concurrency. Use when adding async APIs, handling concurrent I/O, or debugging async code.

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

API reference: Swift Concurrency. async/await, Task, TaskGroup, actors, AsyncSequence, AsyncStream, continuations.

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

Use when adding retries, backoff, or concurrency limits to Spring Boot 4 / Spring Framework 7 code with core Retryable and ConcurrencyLimit support. Covers enablement, backoff, proxy limits, and behavior after retries are exhausted.

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

Build robust TypeScript applications with Effect — type-safe error handling, concurrency, dependency injection, and streaming. Use when someone asks to "handle errors without try-catch", "type-safe error handling in TypeScript", "dependency injection without classes", "concurrent TypeScript", "Effect library", "replace try-catch with typed errors", or "functional programming in TypeScript". Covers Effect, Layer, Schedule, Stream, and Schema.

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

Go concurrency patterns for high-throughput web applications including worker pools, rate limiting, race detection, and safe shared state management. Use when implementing background task processing, rate limiters, or concurrent request handling.

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

Swift 6.2 Approachable Concurrency — single-threaded by default, @concurrent for explicit background offloading, isolated conformances for main actor types.

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

Choosing the right concurrency abstraction in .NET - from async/await for I/O to Channels for producer/consumer to Akka.NET for stateful entity management. Avoid locks and manual synchronization unless absolutely necessary.

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

Coordinate safely with a peer interactive session sharing the same git worktree — check first whether a separate worktree removes the problem, then declare path and branch scope before the first edit, survive a contended index lock, and review the whole branch before opening a PR. Activate when starting work in a repository that may already be occupied, when a git command fails with `index.lock: File exists`, when `guard:snapshot` refuses because a snapshot already exists, or when a commit turns out to contain a file this session never edited. When one session leads and the other supports, divide the labour by shape and re-derive every reported number against a named revision before citing it. Distinct from subagent concurrency: a peer session cannot be bracketed, because no baseline exists from before its edits.

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

Use when choosing kernel spinlocks versus mutexes, using RCU, seqlocks, completions, or memory barriers, or debugging scheduling-while-atomic. Not for userspace atomics: use concurrency-debugging.

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

Use when handling Django transactions and concurrency - atomic, select_for_update, on_commit, upserts, M2M ordering

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

Foundational theory for process-oriented concurrency through synchronous message-passing, applicable to multi-agent coordination and parallel decomposition

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

Expert SwiftUI guidance for macOS apps — covers writing and reviewing code with runtime-level understanding of observation, concurrency, performance, and platform integration. Use when user asks to "build a SwiftUI view", "review my SwiftUI code", "fix observation issues", "bridge AppKit", "architect state management", "debug view updates", or works on any macOS SwiftUI project — building features, reviewing existing code, debugging view updates or performance, fixing concurrency issues, architecting state management, bridging AppKit, or making design decisions. Do NOT use for iOS/iPadOS-only SwiftUI, UIKit bridging, or basic Swift language questions. Focuses on non-obvious traps and deep patterns, not basics.

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

Use when choosing .NET concurrency patterns for async I/O, queues, pipelines, or thread safety. Keywords: async/await, channels, dataflow, Rx, lock contention, producer consumer, parallel processing.

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

Implements BLoC (v9.x) event-driven state management for Flutter with unidirectional data flow using the flutter_bloc package. Use when implementing Bloc/Cubit classes, mapping Events to States, consuming state with BlocBuilder/BlocListener/BlocConsumer, applying event transformers (restartable/droppable/sequential) for concurrency control, setting up BlocProvider/MultiBlocProvider DI, integrating Freezed for sealed union types and exhaustive pattern matching, or testing with blocTest. Ideal for enterprise apps requiring business logic separation, precise concurrency control (search debouncing, form deduplication), or event replay debugging.

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

Use when working with Aws Lambda — aWS Lambda function analysis, invocation metrics, cold start analysis, layer management, and concurrency tracking. Covers function configuration review, error rate analysis, duration percentiles, provisioned concurrency utilization, and deployment package optimization.

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

Expert en développement Elixir/Phoenix avancé (OTP, GenServer, Ecto, LiveView, concurrency)

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

Expert en concurrence (threads, async/await, mutex, channels, race conditions)

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

Master Go concurrency with goroutines, channels, sync primitives, and context. Use when building concurrent Go applications, implementing worker pools, or debugging race conditions.

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

Modern Swift concurrency with async/await, actors, TaskGroup, Sendable, and proper actor isolation for thread-safe iOS development

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

Delegate reading large or multiple files to the `bulk-read` command, which sends the files to a cheaper reader model and returns only its answer. Use when a question needs the content of a file over about 350 lines or of several files at once, when a PreToolUse guard denied an unbounded read, or when the user says "bulk read", "一括読み込み", or "まとめて読んで". Do NOT use for files you are about to edit, for subtle correctness reasoning such as concurrency bugs, or for short files that fit a bounded read.

Use when you need to design, review, or improve REST APIs with Quarkus REST (Jakarta REST) — including resource classes, HTTP methods, status codes, request/response DTOs, Bean Validation, exception mappers, optional runtime OpenAPI exposure (SmallRye), contract-first generation from OpenAPI, content negotiation, pagination, sorting and filtering, API versioning, idempotency (Idempotency-Key), optimistic concurrency (ETag / If-Match), HTTP caching (Cache-Control), API deprecation (Sunset / Deprecation headers), RFC 7807 Problem Details, ISO-8601 for time in contracts, and security-aware boundaries. This should trigger for requests such as Review or improve JAX-RS resources in a Quarkus project; Design HTTP APIs with validation and error handling on Quarkus; Add API versioning, idempotency, ETag concurrency, or deprecation headers; Implement pagination, sorting, or RFC 7807 Problem Details error responses. Part of cursor-rules-java project

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

Inngest イベント駆動 Durable Execution プラットフォームリファレンス。 サーバーレス環境での長時間ワークフロー、バックグラウンドジョブ、スケジュールタスク実装。 createFunction, step.run, step.sleep, step.sleepUntil, step.waitForEvent, step.waitForSignal, step.invoke, step.sendEvent, step.fetch, step.ai.infer, step.ai.wrap, inngest.send, serve, connect。 concurrency, throttle, debounce, rate-limit, batching, priority, idempotency, singleton フロー制御。 Realtime（channels, topics, publish, subscribe, useRealtime, subscription tokens）による進捗配信。 Agent Evals, scoring, group.experiment, MCP dev server などエージェント運用機能。 Next.js / Express / Hono / Cloudflare Workers / Vercel / Netlify / DigitalOcean / Render デプロイ対応。