'concurrency' 검색 결과

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Migration guide for Swift and iOS. Use when migrating ObservableObject to @Observable (iOS 17), enabling Swift 6/6.2 Strict Concurrency, fixing @MainActor/Sendable warnings, adopting Approachable Concurrency (Swift 6.2), or handling iPadOS 26 windowing system changes (UIRequiresFullScreen deprecation). Covers breaking changes and version upgrade tasks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guides concurrency and async decisions in Rust. Use when encountering Send/Sync errors (E0277), choosing between threads vs async, designing shared state, or debugging deadlocks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

How to write modern Swift well — modeling with value types, Swift 6 data-race safety and approachable concurrency (@concurrent, main-actor-by-default, actors, task groups), protocols and generics (some vs any), API design, performance and ARC, Swift Testing, macros, and the modern language features agents don't know about yet. Use when writing, reviewing, or migrating Swift, or when a concurrency error, a hang, a data race, a retain cycle, or a performance problem needs fixing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

C++ 코드 구현·검토·리팩터링에서 타입 사용, 메모리 관리, 예외 처리와 동시성을 점검합니다. 표준 지침에 따라 안전성과 코딩 방식의 일관성을 정리합니다.

• 모던 C++ 코드 작성
• 메모리 소유권과 자원 해제 검토
• 기존 C++ 코드 리팩터링

Claude Flow에서 여러 에이전트의 처리, 통신, 메모리 지연 원인을 분석하고 성능 보고서와 개선안을 만듭니다. 이전 실행 비교와 자동 최적화도 지원합니다.

• 여러 에이전트의 지연 원인 조사
• 변경 전후의 성능 비교
• 주간 성능 보고서 작성

Build and debug asynchronous Rust applications with Tokio, a runtime for scheduling work while operations wait. Apply patterns for task management, channels, error handling, cancellation, and concurrency limits when developing network services and other concurrent systems.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Build asynchronous network services
• Manage tasks and channel communication
• Design error handling and cancellation

Tune cognee ingestion speed, query response time, and LLM costs by adjusting concurrency, text chunk sizes, request limits, and model choices. Estimate ingestion costs before processing and assess options for background work and deployment scaling.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Estimating costs before importing documents
• Adjusting ingestion speed and request limits
• Reducing query response time

Investigate difficult bugs by adding temporary logs to the actual execution path and reproducing the reported behavior. Analyze JSONL logs, which store one structured event per line, then fix the cause, verify regression tests, and remove debugging artifacts.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating bugs that occur only during manual use
• Tracing event order in streaming or concurrent operations
• Checking whether passing tests cover the reported bug

Retrieve BigQuery execution records and resource metrics using the right tool for each task. The skill guides monitoring tool selection and SQL queries for performance investigations, capacity analysis, and reviews of billable compute and storage usage.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Retrieve execution details for a slow job
• Check compute capacity contention and queue delays
• Review reserved capacity and autoscaling limits

Research new models and API capabilities offered by providers behind Pipecat services. Produce dated reports for each service and local committed branches for clear updates, with review commands and separate publishing steps.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking providers for new models and API features
• Researching selected providers or service units
• Preparing local branches for clear updates

Triage incorrect MNN outputs and regressions by matching symptoms to focused debugging guides. Use backend comparisons, minimal reproductions, and controlled experiments to investigate memory issues, quantization, concurrency, numeric limits, caches, and inconsistent results across runs.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating garbled or degraded MNN output
• Comparing results across execution backends
• Tracking regressions after optimization changes

Write, review, and debug Rust applications, including ownership and borrowing rules that govern memory use. Covers trait-based APIs, explicit error handling, asynchronous work with tokio, and tests with Cargo validation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Resolve ownership, borrowing, and lifetime errors
• Design APIs with traits
• Implement asynchronous tasks with tokio