2.4천건 · 관련도순
Improve existing code through up to two optimization rounds, measuring execution time and memory use against a baseline. Verify that results remain correct, save the optimized code, and document changes, measured gains, and trade-offs in a report.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Inspect Claude Code execution traces in Braintrust, including tool calls and token usage. The guide explains event hooks, troubleshooting missing records, and matching separate parent and sub-agent traces using timestamps and metadata.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Record function entry and exit in C/C++ programs, with separate logs for each thread. Convert those logs into a Perfetto timeline to inspect call depth, execution order, and activity across threads.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Provides patterns for unit testing Spring `@Scheduled` and `@Async` methods using JUnit 5, CompletableFuture, Awaitility, and Mockito. Covers mocking task execution and timing, verifying execution counts, testing cron expressions, validating retry behavior, and simulating thread pool behavior. Use when testing background tasks, cron jobs, periodic execution, scheduled tasks, or thread pool behavior.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Instruments programs to record execution information for deterministic replay debugging. Use when debugging hard-to-reproduce bugs (race conditions, timing issues, intermittent failures, heisenbugs), reproducing production failures, or analyzing complex execution sequences. Records non-deterministic events (I/O, threading, randomness, time) to enable exact replay of program executions. Supports Python, JavaScript, Java, and C/C++ with both custom instrumentation and existing replay tools.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Performs abstract interpretation to produce summarized execution traces and high-level program behavior representations. Highlights key control flow paths, variable relationships, loop invariants, function summaries, and potential runtime states using abstract domains (intervals, signs, nullness, etc.). Use when analyzing program behavior, understanding execution paths, computing loop invariants, tracking variable ranges, detecting potential runtime errors, or generating program summaries without concrete execution.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Trade execution using price action setups, major trend reversal trading top and bottom, MTR failure continuation, strong bull and bear breakout trading, strong and weak channel trading strategies, trading range strategies, opening range swings, integration with gold.technical_setups for setup matching and execution planning
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Inngest expert for serverless-first background jobs, event-driven workflows, and durable execution without managing queues or workers. Use when "inngest, serverless background job, event-driven workflow, step function, durable execution, vercel background job, scheduled function, fan out, inngest, serverless, background-jobs, event-driven, workflows, step-functions, durable-execution, vercel, nextjs" mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
The Execution Trader's procedure for turning an approved ticket into one Hyperliquid action and reconciling it - the pre-send checklist, order construction rules, single-send discipline, unknown-result handling and the execution report. Use before and after every send, cancel, modify, leverage change or close.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Load, validate, and use DACP bundles as structured execution context. Detects .bundle/ companion directories, validates integrity (manifest schema, fidelity, provenance), loads typed data, and builds ExecutionContext for receiving agents. Scripts are NEVER auto-executed. Use when processing incoming DACP bundles, interpreting .bundle/ directories alongside .msg files, validating bundle integrity, or building execution context from bundle payloads.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Grooms a GitHub milestone for parallel execution — batch-grooms ungroomed items, assesses scope gaps, analyzes cross-item dependencies via Impact Radius overlap, builds conflict groups, assigns items to execution waves, and persists the dispatch plan via dispatch_create_plan MCP tool. Calls dispatch_wave_start per wave to register state. Use when preparing a milestone for /work-milestone execution. Pass the milestone number as the first argument. Requires milestone items assigned via /group-items-to-milestone.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Executes SAM Stage 5 — opens an attempt on a single ARTIFACT:TASK, dispatches it to a fresh stateless agent session, runs quality gates, and records an ARTIFACT:EXECUTION with implementation results and verification output on the task. Use when Stage 4 Task Decomposition is complete and tasks are ready for execution, when re-executing a task after Stage 6 returns NEEDS_WORK, or when dispatching a task to a language-appropriate specialist agent via the development harness pipeline.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structures IPO execution from organizational meeting through pricing with workstream coordination and timeline management. Use when managing IPOs, coordinating offering processes, or tracking ECM execution milestones.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Measures implementation shortfall with paper portfolio comparison, delay cost attribution, and execution quality assessment. Use when measuring implementation shortfall, analyzing execution quality, or attributing trading costs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan and freeze workflow execution by creating an Execution Contract, setting PLAN_FROZEN/CURRENT_ROLE, and updating PROJECT_STATE decisions and Top 3. Use when starting workflow delivery, re-planning after unfreeze, or when scope/constraints change before execution.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Cross-tool decision matrix for field-update automation in Salesforce — Before-Save Flow vs After-Save Flow vs Apex Trigger vs the deprecated Workflow Rule + Field Update. Covers the recursion / re-entrancy rules, governor cost per pattern (Before-Save flow is governor-free for the same record), the order-of-execution slot each tool occupies, and the Workflow-Rule-to-Flow migration playbook for field-update actions. NOT for the full record-save order of execution — use apex/order-of-execution-deep-dive. NOT for building the record-triggered Flow once the tool is chosen — use flow/record-triggered-flow-patterns. Trigger keywords: WorkflowFieldUpdate, reevaluateOnChange, onCreateOrTriggeringUpdate, doesRequireRecordChangedToMeetCriteria, failedMigrationToolVersion, Migrate to Flow, workflow-meta.xml, field update deprecated, double writer, second trigger pass.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Performs root cause analysis on DAG execution failures. Traces failure propagation, identifies systemic issues, and generates actionable remediation guidance. Activate on 'failure analysis', 'root cause', 'why did it fail', 'debug failure', 'error investigation'. NOT for execution tracing (use dag-execution-tracer) or performance issues (use dag-performance-profiler).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Executes DAG waves with controlled parallelism using the Task tool. Manages concurrent agent spawning, resource limits, and execution coordination. Activate on 'execute dag', 'parallel execution', 'concurrent tasks', 'run workflow', 'spawn agents'. NOT for scheduling (use dag-task-scheduler) or building DAGs (use dag-graph-builder).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Parses complex problems into DAG (Directed Acyclic Graph) execution structures. Decomposes tasks into nodes with dependencies, identifies parallelization opportunities, and creates optimal execution plans. Activate on 'build dag', 'create workflow graph', 'decompose task', 'execution graph', 'task graph'. NOT for simple linear tasks or when an existing DAG structure is provided.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Task claiming and ownership tracking for parallel agent execution. Agents claim tasks from a shared queue with file ownership enforcement. Use during parallel execution phases when multiple agents work simultaneously.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Parses and analyzes the Windows Amcache.hve registry hive to extract evidence of program execution, application installation, and driver loading for digital forensics investigations. Uses Eric Zimmerman's AmcacheParser and Timeline Explorer for artifact extraction, SHA-1 hash correlation with threat intel, and timeline reconstruction. Activates for requests involving Amcache forensics, program execution evidence, Windows artifact analysis, or application compatibility cache investigation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Parse Windows Prefetch files using the windowsprefetch Python library to reconstruct application execution history, detect renamed or masquerading binaries, and identify suspicious program execution patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Parse Windows Prefetch files to determine program execution history including run counts, timestamps, and referenced files for forensic investigation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
TanStack Pacer best practices for execution control in React — debouncing, throttling, rate limiting, queuing, and batching. Use when implementing search inputs, scroll handlers, API rate limits, task queues, bulk operations, or any scenario requiring controlled execution timing with reactive state.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.