35건 · 관련도순
Filter and summarise the cross-library KB audit log. Reports confidentiality events (attribution drops, synthesis aborts, dispatcher failures, no-evidence markers, cross-library promotions) over a date range, by event type, and by source handle.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when verification depends on agent runtime phases, queued input, tool-call lifecycle, save points, retry, abort, compaction, or branch behavior.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Read a Prisma Next structured error envelope and route to the right recovery — code, domain, severity, why, fix, meta. Use for error, exception, my emit failed, my query won't typecheck, my query crashed, my migration won't apply, MIGRATION.HASH_MISMATCH, BUDGET.ROWS_EXCEEDED, BUDGET.TIME_EXCEEDED, RUNTIME.ABORTED, PLAN.HASH_MISMATCH, CONTRACT.MARKER_MISSING, PN-RUN-3001, PN-RUN-3002, PN-RUN-3030, PN-MIG-2001, PN-CLI-4011, PN-SCHEMA-0001, drift, capability missing, planner conflict, prisma studio, EXPLAIN, query log, db.end, db.close, script won't exit, hangs, close connection, pool.end, client is closed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when developing plugins, tools, and extensions for OpenCode v1 - plugin contract, crash-prevention rules, ctx/event APIs, subagent lifecycle (abort races, compaction, orphan detection), MCP integration, testing patterns, or publishing to npm
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a task needs the judgment of a Commercial Diver — planning a surface-supplied or SCUBA-mode dive against no-decompression limits, sizing a bailout/reserve gas supply before descent, choosing wet vs. dry (habitat) underwater welding for a repair, scoping an underwater NDT inspection, or deciding whether to abort a dive against a safety threshold.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Automating post-sandbox-refresh cleanup via the `SandboxPostCopy` interface — the Apex class that runs ONCE after a sandbox refresh or clone completes, before users can log in. Used to mask emails, deactivate users, scrub integration endpoints, disable scheduled jobs, and reapply per-environment configuration the metadata copy doesn't carry. Covers the interface contract (`runApexClass` setting, `SandboxContext` parameter, single-execution semantics), the email-masking pattern that stops sandbox tests emailing production addresses, and the refresh runbook checklist. NOT for choosing sandbox type or refresh cadence — use admin/sandbox-strategy. NOT for re-seeding reference data after a refresh — use data/sandbox-refresh-data-strategies. Trigger keywords: SandboxPostCopy, runApexClass, SandboxContext, Test.testSandboxPostCopyScript, RunAsAutoProcUser, Automated Process user, CronTrigger, System.abortJob, sandbox email masking, post-refresh runbook.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when monitoring, diagnosing, or managing Batch Apex, Scheduled Apex, Queueable, and Flow scheduled jobs: Setup > Apex Jobs, AsyncApexJob queries, concurrent limits, failure detection, and notification patterns. NOT for writing the Batch or Schedulable class itself — use apex/batch-apex-patterns or apex/apex-scheduled-jobs. NOT for BatchApexErrorEvent alerting in code — use apex/scheduled-apex-failure-detection-and-monitoring. Trigger keywords: Setup > Scheduled Jobs, Apex Flex Queue, CronTrigger, CronJobDetail, FlowInterview, System.abortJob, System.schedule, CRON expression, Holding status, BLOCKED state, reschedule after sandbox refresh, scheduled job runbook.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply these opinionated JavaScript conventions whenever writing or reviewing JS or Node: ESM-first packaging, choosing between Promise combinators, error handling that doesn't swallow failures, AbortController for cancellation, keeping the event loop unblocked, and reaching for platform APIs before dependencies.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create and operate ChatDOC Studio knowledge bases through pd_router using a Bearer API key and JavaScript helpers. Use when Codex needs to upload one or more PDF/DOC/DOCX files, skip failed files without aborting the whole job, create a knowledge base from successful uploads, or call the ChatDOC Studio knowledge-base skill endpoints through `https://platform.paodingai.com/openapi/chatdoc-studio/...`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Execute a swarm plan wave by wave with filesystem isolation via git worktrees. For each wave, main context decides the scenario recipe + implementation contract for every task, then spawns one swarm-worker per task in parallel. Each worker executes its recipe and reports JSON status. Worktree merge-audit verifies write-set discipline before changes land on main. Aborts remaining waves on any audit or task failure.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Knowledge base from the NASA Probabilistic Risk Assessment Procedures Guide (NASA/SP-2011-3421, 2nd ed.). Use for quantitative PRA of aerospace and safety-critical systems: the risk triplet and scenario logic stack (MLD, ESD, event trees, fault trees, minimal cut sets), Bayesian data collection and parameter estimation, aleatory/epistemic uncertainty modeling and common-cause failure (Alpha Factor, beta-factor, CCBE), human reliability analysis (THERP, CREAM, NARA, SPAR-H), context-based software risk (CSRM), physics-based and structural/phenomenological models (stress-strength, limit states, FORM/SORM, NASGRO, range safety), uncertainty propagation and importance measures (F-V, RAW, Birnbaum, DIM), and launch-abort modeling with worked PRA examples. This is the QUANTITATIVE engine beneath NASA's risk doctrine — for the qualitative RIDM/CRM decision framework use the nasa-risk pack. Thin on programme management, organisational risk governance, and non-aerospace regulatory contexts; aerospace-focused and anchored to the 2011 second edition.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.