'exceptions' 검색 결과

Ionic, covalent, and metallic bonding, Lewis structures, VSEPR theory, molecular geometry, polarity, and intermolecular forces. Covers octet rule and exceptions, formal charge, resonance, sigma/pi bonds, orbital hybridization, electronegativity-driven bond classification, VSEPR electron-domain and molecular geometries, dipole moments, and the four intermolecular force types (London dispersion, dipole-dipole, hydrogen bonding, ion-dipole). Use when predicting molecular shapes, bond properties, or physical behavior from molecular structure.

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

This skill should be used when the user asks to "add docstrings", "write error handling", "use naming conventions", "handle exceptions", or when writing new Python code for StreamFlow that requires docstring format, naming conventions, exception handling, or async cleanup patterns.

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

Java coding standards for Spring Boot services: naming, immutability, Optional usage, streams, exceptions, generics, and project layout.

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

从 MAS（clock_domains / io_timing / path_exceptions）派生 Synopsys SDC 时序约束文件，OpenSTA 语法校验。触发场景：(1) bba-guru-synthesis 综合前；(2) post-PD timing fail 修订约束；(3) 显式 /bb-create-sdc。

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

Use when writing Cortex-M NVIC ISRs, configuring priorities, handling HardFault, tail-chaining, or measuring interrupt latency. Not for the vector table itself: use baremetal-startup.

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

Use when configuring MCU sleep/stop/standby, WFI, STM32 PWR, nRF sleep, clock gating, wake-up EXTI sources, or measuring current draw. Not for the wake ISR: use interrupts-and-exceptions-baremetal.

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

Apply one governed bounded Proto UI dependency update after pui-deps establishes the exact manifest, lockfile, consumers, compatibility evidence, and rollback boundary. Use for ordinary package or toolchain updates whose intended compatibility is already fixed. Route unresolved public compatibility, security disclosure, publication, release, or provenance exceptions to their dedicated decision path.

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

Draft standard operating procedures with scope, roles, steps, controls, exceptions, and review cadence. Use when a recurring business process needs clear repeatable instructions.

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

Format recurring KPI snapshots, exception flags, and owner follow-ups for weekly operations reviews. Use when the work is routine packaging of operational metrics and exceptions. Do not use for root cause analysis, process redesign, or full performance diagnosis.

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

Detects insecure network communication in mobile apps (Android/iOS). Trigger on: cleartext HTTP, TLS misconfiguration, certificate pinning bypass, hostname verification disabled, allowCleartextTraffic, NSAllowsArbitraryLoads, ATS exceptions, custom TrustManager, ALLOW_ALL_HOSTNAME_VERIFIER, TLS 1.0/1.1, weak cipher suites, certificate pinning absent, Network Security Configuration, onReceivedSslError, SSLSocket, OkHttp, NSURL, URLSession, certificate transparency, HSTS, MITM. Covers MASVS-NETWORK-1 (TLS required) and MASVS-NETWORK-2 (certificate validation).

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

Design Invocable Apex actions that return deterministic, agent-friendly errors instead of surfacing raw exceptions to the LLM. NOT for authoring the action itself — @InvocableMethod schema, labels, security context — use agentforce/custom-agent-actions-apex. NOT for the Apex tests that force each error branch — use agentforce/agent-action-unit-tests.

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

Update tests when changing APIs — no exceptions

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

Opinionated house conventions for NestJS backends — module boundaries and layering, provider wiring and injection scopes, guards/interceptors/pipes/filters, DTOs and validation, domain exceptions, config, and the Nest 11 / Express 5 behaviour that compiles cleanly and fails at runtime. Use whenever the code is NestJS (`@nestjs/*` in package.json, or `@Module`/`@Injectable`/`@Controller`/`@Cron` in the file), including when the question sounds like plain TypeScript, an OOP refactor, a code review, or an ops problem — the Nest-specific answer differs from the generic one. Typical asks: scaffolding a module, adding a controller, provider, or endpoint, wiring an enhancer, a boot-time DI or circular-import failure, a response leaking entity fields despite `@Exclude()`, a cron job firing on every replica, upgrading NestJS, or reviewing a Nest diff. Not for plain Express or Fastify, Angular, frontend, SQL, or CI.

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

Adopt better-result in an existing TypeScript codebase. Use when replacing try/catch, Promise rejection handling, null sentinels, or thrown domain exceptions with typed Result workflows.

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

Drafts a Notice of Removal under the Class Action Fairness Act (CAFA), 28 U.S.C. § 1332(d), transferring a state court class action to federal court. Covers minimal diversity, aggregate amount in controversy exceeding $5 million, 100+ class members, CAFA exceptions, unanimity, timeliness, and required exhibits. Use when a defendant needs to remove a state-filed class action to federal court within 30 days of service.

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

Design resilient React error handling with Error Boundaries, Sentry integration, recovery UI, retry patterns, and graceful degradation. Activate on: error boundary, crash recovery, Sentry, error fallback UI, retry logic, unhandled exceptions. NOT for: form validation errors (use form-validation-architect), API error codes (use api-architect).

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

Develop, challenge, and document Chisel processor microarchitecture designs before implementation. Use when discussing or writing design documents for processor pipelines, queues, issue logic, rename, ROB, LSU, caches, MSHRs, forwarding, wakeup, replay, flush, privilege, exceptions, or other cycle-accurate hardware mechanisms; when converting design conversations into stable Markdown specifications; or when reviewing a proposed Chisel CPU design for correctness, timing, area, verification cost, and cross-document consistency.

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

MANDATORY skill for ALL code generation. Enforces top-down composition, consistent abstraction layers, and proper module hierarchy. Apply every time you write or modify code — in any language — no exceptions.

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

Use when picking a failure-reporting strategy — exceptions vs Result types, recoverable vs not, retry / circuit-breaker / graceful degradation — decision framework only, catalogues externalized.

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

Pushing GitHub Actions changes, resolving push rejection, requesting upload exceptions.

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

Analyze a local codebase and infer the architecture it is actually using, including repo kind, best-fit dominant architecture, directly evidenced coexisting patterns, major subsystem exceptions, confidence, docs-vs-code drift, and repo-fit hints for downstream agents. Use when prompts ask what architecture a repo uses, whether it is really hexagonal or just layered, what subtle patterns shape a repo or slice, how a target slice fits a hybrid monorepo, whether documented architecture matches implementation, or when `/tw-tk` needs a repo-dialect preflight before making a minimal change.

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

Instrument browser/web apps with the Application Insights JavaScript SDK (@microsoft/applicationinsights-web). Use for Real User Monitoring (RUM) — page views, clicks, AJAX/fetch dependencies, exceptions, custom events...

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

Answers an employee's or manager's HR policy question strictly from the policy documents the user supplies or the agent can reach as knowledge: a DRAFT answer that quotes the governing clause with its document, version and clause reference, lists the conditions and exceptions the text states, returns UNKNOWN where the documents are silent and names the role to ask. Never invents a rule, fills a gap from general practice or decides an individual's case. Use when the user asks to check a policy, for example "what does the policy say about", "am I entitled to", "how many days of leave do I get", "what is the process for requesting", "does the handbook allow" or "which clause covers". Do not use for comparing two policy versions or briefing a change, use policy-change-briefing instead. Drafts for human review; never approves, authorises or signs off.

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

Reads an accounts payable exception list (mismatches, possible duplicates, missing or exhausted purchase orders, missing receipts, vendor or bank detail differences) with any invoice, purchase order and receipt data supplied, and returns a DRAFT action sheet: per line, the exception as stated, the facts as read, the difference where both sides exist, one proposed next action for the accounts payable clerk to perform, who or what it needs, and a draft query, with UNKNOWN wherever the data is silent. Use when the user asks to "review these invoice exceptions", "work through the AP exception queue", "what should I do with these blocked invoices", "propose next steps for the three-way match failures" or "sort out the duplicate and missing PO invoices". Do not use for a purchase order log screened for anomalies, use purchase-order-anomaly-review instead; for an expense claim against policy, use expense-policy-precheck. Drafts for human review; never approves, authorises or signs off.

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