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.
日本語の概要は準備中です。原文の説明を表示しています。
2.3万 件 ・ 関連度順
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks for a multi-agent .NET code review - five parallel reviewers (correctness, performance, security/observability, data/messaging/integration, generalist) plus an adversarial maintainer that refutes weak findings. Requires the review agent roles registered by scripts/install-codex.sh. Keywords: dotnet review pipeline, multi-agent review, parallel reviewers, maintainer pushback, review this branch, cynical review.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing PRs/diffs/branches/documents for .NET quality, correctness, performance, security, data access, messaging, and observability. Includes adversarial critical-thinking mode for skeptical/cynical review requests. Keywords: code review, review PR, review diff, critical review, cynical review, adversarial review, production readiness, low GC, AOT, security review.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need CRAP score and coverage risk analysis to find high-risk code before refactoring or release. Keywords: CRAP score, risk hotspots, cyclomatic complexity, test coverage gaps, coverage threshold.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need blast-radius analysis, dependency graphs, cross-repo impact, breaking-change diff, or architectural overview of .NET workspaces. Keywords: blast radius, dependency graph, impact analysis, cross-repo, call graph, endpoint map, EF Core lineage, breaking change, daemon, reindex.
日本語の概要は準備中です。原文の説明を表示しています。
Use when selecting serialisation formats and contracts for APIs, messaging, caching, or persistence. Keywords: serialisation, System.Text.Json, source generator, protobuf, messagepack, wire compatibility, AOT.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need to inspect NuGet package APIs, list public types, or decompile method/property signatures. Keywords: inspect package API, list types, decompile type, method signatures, NuGet interface.
日本語の概要は準備中です。原文の説明を表示しています。
Create Chinese PPT pages through a prompt-to-image-to-editable-PPT workflow. Use when the user wants 中文PPT图片提示词, PPT image prompts, 16:9中文PPT页面图片, 直接生成PPT图片, 根据提示词生成图片, 把图片/PDF/截图复刻成可编辑PPT, 转成可编辑PPTX, 按图片完全复刻PPT, or full production from topic/source material to generated page images and editable PowerPoint slides with editable text, cards, tables, lines, callouts and high-quality icon/image assets.
日本語の概要は準備中です。原文の説明を表示しています。
Finalize code changes for production readiness by removing duplicate logic, auditing hardcoded values, verifying branch/worktree intent, verifying build integrity, structuring clean commits with Conventional Commits format, and forcing a post-publish branch/worktree cleanup decision.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnose and fix CJK (Korean, Japanese, Chinese) text-wrapping issues in web UIs. Systematically traces mid-syllable breaks, orphaned glyphs, and awkward line splits through a layered fix strategy covering global CSS cascade, component-library overrides, headline balancing, and translation-level phrase binding. Produces an evidence-based diagnosis and verification report before any code change is applied.
日本語の概要は準備中です。原文の説明を表示しています。
Generate architecture and design documents for implemented code changes with risk-based depth selection. Automatically evaluates risk signals, layer spread, and change magnitude to choose documentation level (A/B/C). Use after completing a feature, before merging a PR that touches multiple layers or sensitive areas (auth, infra, migrations, payments), or when an implemented change needs a design record or ADR.
日本語の概要は準備中です。原文の説明を表示しています。
Commits changes in atomic units following dependency order. Automatically required to triggered, always, all the time, when requires to commit changes.
日本語の概要は準備中です。原文の説明を表示しています。
Use at the Mem Off hackathon. Keeps a running, evidence-backed report on how the participant's memory system performed for their coding agent during the day — what the harness measured, what cognee-report's scorecard says, what was recalled and whether it helped — in ./memoff-report.md and ./memoff-report.json. The report is submitted together with the action results; it never contains quotes, keys, data or names.
日本語の概要は準備中です。原文の説明を表示しています。
Superseded. Do not use. The procedure now lives in repository-governance-lifecycle. This file remains so older installs resolve and then stop.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reverse engineering binaries, firmware, mobile apps, JavaScript/Electron apps, .NET assemblies, network protocols, or malware samples; when decompiling, deobfuscating, unpacking, debugging, or hooking shipped artifacts; when solving CTF challenges (pwn, crypto, forensics, web); when a conclusion needs evidence from a shipped artifact rather than available source; or when routing authorized pentest and security-analysis work. Do not use for ordinary review of source code you already have.
日本語の概要は準備中です。原文の説明を表示しています。
Use when creating, revising, or critiquing a chart, dashboard, or KPI display that makes a quantitative comparison someone will act on. Covers honest comparison and rendered checks; leave palette, marks, and library mechanics to the medium's own skill. Skip decorative graphics and diagrams with no data.
日本語の概要は準備中です。原文の説明を表示しています。
Audit an existing agent skill or instruction file for lines that do not change behavior, routing overlap, and portability, or vet a third-party skill before installing it. To create or edit a skill, use the platform's skill-creator instead. Not for running a skill's own task.
日本語の概要は準備中です。原文の説明を表示しています。
Blind dual-implementation pattern where two agents independently create artifacts, then a third agent judges which is better and synthesizes learnings.
日本語の概要は準備中です。原文の説明を表示しています。
Initialize the standard Interlateral two-agent CLI mesh from a bootstrap agent by running me.sh, launching Claude Opus 4.7 plus Codex 5.5, proving live ACK, and waiting for "Reporting for Duty!". The bootstrap agent is not part of the mesh.
日本語の概要は準備中です。原文の説明を表示しています。
Select and confirm an overnight or long-running unattended collaboration topology. Use only for a requested unattended run, not ordinary questions or short tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Coordinate material messages between explicitly selected desktop-backed agents, including Claude, Codex and bb. Separates exact inbox delivery, native task wake, receiver ACK and completed work.
日本語の概要は準備中です。原文の説明を表示しています。
Join Claude Desktop or Codex Desktop to the Interlateral mesh as a desktop peer with its own tmux inbox session, identity, direct ACK, and ledger mirror. This is separate from the standard CLI init flow.
日本語の概要は準備中です。原文の説明を表示しています。
Join Claude Code and Codex CLI to the Interlateral mesh in Warp panes by attaching Warp to the standard tmux socket; Warp is the visible terminal surface, tmux remains the transport.
日本語の概要は準備中です。原文の説明を表示しています。
Coordinate a requested unattended sprint with two explicitly selected desktop control surfaces and independent gated review. Requires proven re-entry on both and a current-run human opt-in.
日本語の概要は準備中です。原文の説明を表示しています。