299건 · 관련도순
Generate audit-ready internal control design documents from As-Is business process inventories. Produces control IDs, assertion mappings, procedures, SoD analysis, KPIs, materiality thresholds, and implementation roadmaps. Use when building internal controls for new audit engagements, SOX/J-SOX compliance, or process improvement initiatives.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Conducts rigorous authoring and review of Playwright E2E tests. Enforces accessibility-first locators, web-first assertions, strict isolation, and DAMP architecture. Use when generating, refactoring, or reviewing any Playwright test code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
반복되는 null 검사를 Special Case(Null Object) 클래스로 대체하여 다형성으로 처리. "null 객체 패턴", "null 체크 반복 제거", "특수 케이스 클래스", "/introduce-special-case" 요청 시 사용. 단, 단순 전제 조건 명시는 /introduce-assertion, 타입별 분기 전반은 /replace-conditional-with-poly가 적합. /introduce-special-case [commit-ref]로 호출.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Operational guide for integrating the NV oOS Complete purchase flow (vendor checkout API client) into standalone WordPress plugins — docs-hub 0.5.3 (stack added in PR #6963, shipped 0.5.2 → 0.5.3) and nvoos-content-graph 1.0.10 (live). Covers the vendor API contract (session/verify/health, nvoos-oos-complete product, 424/502 error passthrough), the five-class client stack (config, vendor client, license store, installer, REST controller), the purchase-modal JS/CSS port recipe (class-prefix rename, keep-the-JS-identical trick), wp.org commerce compliance (External Services disclosure, WPORG-REVIEW-COMMERCE-NOTES.md, js.stripe.com service exception), and the checkout test conventions (direct controller calls, pi_ fixture rules, zero-HTTP assertions). Use when adding the Get NV oOS Complete upsell/checkout to a plugin, porting the commerce stack to a new standalone plugin, extending the purchase flow, or debugging a checkout integration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Refresh Claude Ads platform, API, policy, regulation, benchmark, issue, pull-request, fork, and repository evidence. Use for ads research refresh, expired refresh_due dates, stale API or platform claims, reverify-or-demote decisions, release-current claim validation, ecosystem review, current platform changes, or updating paid-media knowledge. When tools or sources are unavailable, still demote the stale claim for the current run and block dependent release-current assertions before requesting access.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Scaffolds eval.yaml test files for agent skills in the dotnet/skills repository. Use when creating skill tests, writing evaluation scenarios, defining assertions and rubrics, or setting up test fixture files. Handles eval.yaml generation, fixture organization, and overfitting avoidance. Do not use for running or debugging existing tests nor for skills authoring.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Detects Vitest test-isolation hazards: unrestored vi.spyOn/vi.mock without afterEach cleanup or restoreMocks config, un-awaited resolves/rejects assertions, and shared mutable module state across tests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Enforce TypeScript strictness by reducing any/unsafe assertions and ensuring null handling.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnose, fix, or validate SwiftUI animation and scroll behavior by temporarily instrumenting views with MotionEyes, capturing console traces over time, and comparing motion data to user intent or test expectations. Use when users report bugs such as wrong direction, premature fade, timing or easing mismatch, unexpected movement, missing movement, incorrect relative movement between views, scroll jumps, scroll restoration drift, content-offset desynchronization, or when they want to turn MotionEyes traces into focused assertions. Prefer XcodeBuildMCP log capture first and fallback to CLI log streaming; remove only agent-added MotionEyes instrumentation after validation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Verify device legitimacy and app integrity using DeviceCheck (DCDevice per-device bits) and App Attest (DCAppAttestService key generation, attestation, and assertion flows). Use when implementing fraud prevention, detecting compromised devices, validating app authenticity with Apple's servers, protecting sensitive API endpoints with attested requests, or adding device verification to a backend architecture.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze existing code and write comprehensive unit and integration tests for it. Detects the test framework, identifies untested code paths, and generates tests with proper mocking, edge cases, and assertions. Use when the user asks to add tests, improve coverage, or test a specific module.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Biological knowledge: query curated assertions and reference databases for genes, variants, pathways, regulation, cell types, reference atlases, perturbation-derived relationships, phenotypes, therapeutic targets, drugs, interactions, annotations, signatures, compounds, and predicted structures. Use for identifiers, marker sets, gene sets, associations, ontologies, database facts, and cross-database coverage.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Experimental data: discover and acquire raw or near-raw measurements, sample-level observations, and reusable datasets from sequencing, transcriptomics, single-cell, perturbation, proteomics, metabolomics, genomics, and structural-biology repositories. Use for study or sample metadata, matrices, reads, spectra, experimental structures, and downloadable research artifacts—not curated database assertions or reference marker collections.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Check whether a Playwright, Puppeteer, Selenium or CDP-driven browser presents a coherent fingerprint, using liarjs as a library against a Page you already have - navigator.webdriver, HeadlessChrome tokens, worker versus main-thread identity, patched-API integrity, WebGL versus WebGPU GPU identity. Use when asked whether an automated browser looks like a normal one, when a headless setup or a stealth plugin's effect needs measuring rather than assuming, or when an assertion on fingerprint quality belongs in a test suite.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Performs simple mutation testing to verify test coverage and assertions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Track the full Toulmin epistemic ancestry of every claim produced by a multi-agent swarm. Each agent output is tagged with an argument chain (claim / data / warrant / relationship) derived from SwarmTracer spans and LineageEdge records, so operators can zoom into any sub-claim and see precisely which agents asserted it, what triggered each assertion, and how contradictions propagated or were synthesised away. The SwarmTracer pattern — wrapping the SwarmAgentExecutor to capture spans, record messages, and build a lineage graph — is the concrete runtime substrate. Argumentative lineage lifts that graph into the Toulmin vocabulary so reasoning provenance is both machine-queryable and human-interpretable.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.