「concurrent」の検索結果

Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious.

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

Apply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first; serialize structurally only when one shared writer is a real invariant.

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

Use when a coding task needs a concurrent checkout, unrelated dirty state blocks safe branch switching, or the user or repository explicitly requires a worktree.

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

Scaffold an isolated CLOUD dev box per agent (via crabbox + Daytona) for any codebase — the parallel-safe counterpart to dev-local-setup. Each agent gets its own full stack (own DB + dev server) and an in-box browser for e2e, so concurrent loops never collide on ports/state. Sets up the snapshot image, .crabbox.yaml, an idempotent setup.sh (also boots the stack locally), and a cbx.sh wrapper. Use when the user says "set up crabbox", "give each agent its own box", "add cloud testing", "make this repo testable in the cloud / on Daytona", "parallel-test this", or when setup-codebase-harness needs true per-agent isolation.

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

Use when positioning an AISTATS submission against AI, machine-learning, statistics, and uncertainty literature, including arXiv preprints, workshop versions, concurrent submissions, prior conference versions, PMLR archival status, and the two-community citation coverage that AISTATS reviewers expect.

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

Use when positioning an ACM CCS submission against the security big-four and specialist literature, including arXiv preprints, prior CCS/S&P/USENIX/NDSS papers, concurrent disclosures, CVE and advisory records, and the attack-and-defense lineage that a SIGSAC program committee expects to see credited.

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

Use when positioning an ACL submission against the NLP literature, covering ACL Anthology citation practice, arXiv-versus-published version citation, concurrent LLM-era preprints, prior-cycle ARR resubmission overlap, anonymity-preserving self-citation, and the fast-moving baseline problem in computational linguistics.

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

Use when positioning an AAMAS submission against multiagent, game-theory, and reinforcement-learning literature spread across AAMAS, AAAI, IJCAI, NeurIPS, ICML, EC, and JAAMAS, including arXiv and workshop versions, concurrent submissions, prior conference versions, and the cross-community citation coverage AAMAS reviewers expect.

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

Resolve Swift concurrency compiler errors, adopt approachable concurrency (SE-0466), and write data-race-safe async code. Use when fixing Sendable conformance errors, actor isolation warnings, or strict concurrency diagnostics; when adopting default MainActor isolation, @concurrent, nonisolated(nonsending), or Task.immediate; when designing actor-based architectures, structured concurrency with TaskGroup, or background work offloading; or when migrating from @preconcurrency to full Swift 6 strict concurrency.

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

Implements concurrent Go patterns using goroutines and channels, designs microservices with gRPC or REST, optimizes performance with pprof, and enforces idiomatic Go.

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

Swift 6.2 concurrency updates including default MainActor inference, @concurrent for background work, isolated conformances, and approachable concurrency migration. Use when adopting Swift 6.2 concurrency features or fixing data-race errors.

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

Use multiple Claude agents to investigate and fix independent problems concurrently

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

Use when the user runs /gsd-workstreams or asks to list, create, switch, status, progress, complete, or resume parallel workstreams for concurrent milestone work. The active one is tracked in the GSD_WS variable.

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

Implement concurrency and non-blocking I/O in modern PHP. Use when implementing concurrent requests, async processing, or non-blocking I/O in PHP.

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

Write safe, structured concurrent code with Kotlin Coroutines. Use for suspend functions, coroutine scopes, cancellation, and coroutine leaks; defer Java Virtual Threads, Android WorkManager/Fragment lifecycle, Compose state hoisting, and Detekt/tooling configuration.

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

Define transaction boundaries, locking, and consistency guarantees for multi-step writes. Use when designing atomic operations, retries, idempotency, or concurrent write behavior.

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

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

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

Read before a js eval cell that installs a package, spawns a server or PTY, or starts a long run, and before any bun -e, script, server, CLI, test, bundle, or package-management work: this session's eval js kernel runs Bun 1.4+ (this skill is present only when it does). Bun 1.4 ships builtins that replace 15+ npm deps — check here BEFORE installing sharp, puppeteer/playwright (scraping), marked, node-cron, node-pty, concurrently, serve-static, tar, json5, fast-xml-parser, string-width. Triggers: eval js, bun, Bun.serve, bun test, bun build, bun install, bun run, image resize, headless browser, markdown render, cron, PTY.

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

Use when you need to apply functional programming principles in Java — including writing immutable objects and Records, pure functions, functional interfaces, lambda expressions, Stream API pipelines, Optional for null safety, function composition, higher-order functions, pattern matching for instanceof and switch, sealed classes/interfaces for controlled hierarchies, Stream Gatherers for custom operations, currying/partial application, effect boundary separation, and concurrent-safe functional patterns. This should trigger for requests such as Improve the code with Functional Programming; Apply Functional Programming; Refactor the code with Functional Programming; Refactor Java code to use streams or Optionals safely; Improve immutability and pure functions in Java. Part of Plinth Toolkit

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

Spawns multiple AI coding agents to work on related GitHub issues concurrently using git worktrees. Use when breaking down a large feature into multiple issues, running parallel agents with --print flag, or managing wave-based execution of related tasks.

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

Run the code and documentation simplification passes together over one scope, launching every review agent concurrently before applying a single round of fixes. Use when the user asks to "simplify all", "simplify everything", "simplify code and docs", "clean up code and docs", "run both simplify skills", or "simplify code and docs in parallel".

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

Shared rules for test runs that drive the running app or run a test target: isolation from concurrent runs, stubs for infrastructure that cannot be stood up, provisioning privileged state, approval before writes to shared external systems, and cleanup of only what the run created. Not typically invoked directly.

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

Run the code and documentation simplification passes together over one scope, launching every review sub-agent concurrently before applying a single round of fixes. Use when the user asks to "simplify all", "simplify everything", "simplify code and docs", "clean up code and docs", "run both simplify skills", or "simplify code and docs in parallel".

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

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. Only runs when explicitly invoked; it does not trigger on its own.

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