'isolation' 검색 결과

Agent Context Isolation

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

Plans and configures multi-tenancy on GKE. Covers namespace isolation, RBAC planning for teams, resource quotas, LimitRanges, network isolation, and cost allocation. Use when designing GKE multi-tenancy, configuring GKE namespaces, setting up resource quotas, or isolating GKE teams. Don't use for single-tenant cluster configuration or general deployment instructions (use gke-basics or gke-app-onboarding instead).

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

Give an AI agent its own real browser over MCP tool calls - launch, navigate, click, fill, screenshot, extract text, run JS - with a kernel-level real-device fingerprint and a persistent profile, so the session stays logged in between runs and pages see one coherent device instead of a headless build. No Playwright or SDK code to write. Use when an agent should operate a site itself, when a computer-use / browser-use setup needs a captured real fingerprint rather than a synthetic one, when agent sessions keep losing their login, or when comparing hosted agent-browser services. Also for 'MCP browser', 'browser MCP server', 'let my agent browse the web', 'agent browser control', 'browser-use MCP', 'computer use browser', 'Browserbase alternative', 'Steel browser alternative', 'headless browser detected'. Node (npx) or Python; Windows x64, macOS Intel + Apple Silicon, Linux x64 / arm64. SDK and REST reference is anti-detect-browser; account isolation is multi-account-isolation.

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

Drive Chromium from standard Playwright APIs with a real-device fingerprint applied in the kernel, one persistent isolated profile per identity, and a per-profile proxy whose exit IP sets timezone and WebRTC - JavaScript (npm 'anti-detect-browser') or Python (PyPI 'antibrow'). Use when sessions must stay logged in across runs and stay separate, when a scraper or agent is blocked by an incoherent headless fingerprint, when checking ads or pricing from another region, when a page must be reached as a phone rather than a desktop, when automation mints a profile per task, when running several of your own accounts from one machine, or when testing how your own bot detection scores a real device. Also for 'antibrow', 'fingerprint browser', 'multi-account browser', '防关联', '多账号', '安卓模拟', 'Android profile', 'mobile fingerprint', 'temporary profile', 'CreepJS', 'residential proxy', 'browser-use', 'crawl4ai'. MCP control is browser-mcp-agent; isolation is multi-account-isolation.

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

Checks isolation (APIs/DB/FS/Time/Random/Network), determinism (flaky, order-dependent), and 7 anti-patterns.

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

Runtime enforcement of file system boundaries and tool access restrictions. Blocks unauthorized operations and logs violations. Activate on 'enforce scope', 'access control', 'boundary enforcement', 'tool restrictions', 'runtime security'. NOT for validation (use dag-permission-validator) or isolation management (use dag-isolation-manager).

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

Validates permission inheritance between parent and child agents. Ensures child permissions are equal to or more restrictive than parent. Activate on 'validate permissions', 'permission check', 'inheritance validation', 'permission matrix', 'security validation'. NOT for runtime enforcement (use dag-scope-enforcer) or isolation management (use dag-isolation-manager).

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

Comprehensive backend development guide for Langfuse's Next.js 14/tRPC/Express/TypeScript monorepo. Use when creating tRPC routers, public API endpoints, BullMQ queue processors, services, or working with tRPC procedures, Next.js API routes, Prisma database access, ClickHouse analytics queries, Redis queues, OpenTelemetry instrumentation, Zod v4 validation, env.mjs configuration, tenant isolation patterns, or async patterns. Covers layered architecture (tRPC procedures → services, queue processors → services), dual database system (PostgreSQL + ClickHouse), projectId filtering for multi-tenant isolation, traceException error handling, observability patterns, and testing strategies (Jest for web, vitest for worker).

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

Manages git worktrees for parallel agent isolation. Creates isolated worktrees for parallel agents on parallel/{name}-{timestamp} branches, merges results with conflict detection, prunes stale metadata, and reports health status. NOT for user-initiated feature branches — use git worktree directly for that.

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

Expert-level mechanical vibrations covering free and forced vibration, damping, resonance, modal analysis, vibration isolation, and rotating machinery.

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

Flags where a P&ID draft raises a process safety question and points to the candidate evidence an engineer would review (HAZOP register, relief study, SIL assessment, isolation philosophy), as questions and quoted passages with UNKNOWN for missing documents, plus safety functions, relief devices and isolation requirements carried over as stated. Never rates, sizes, classifies, resolves or declares protection adequate. Use when the user asks to "write the process safety flags", "produce the process safety section of the P&ID enrichment", "list which protection questions this P&ID raises" or "map the HAZOP and relief study evidence to the draft" after gate G2, once the piping and instrumentation sections exist. Do not use for proposing loops, alarms or trips from the control philosophy, use instrumentation-and-control-enrichment instead; do not use for checking identifiers, use tagging-and-numbering. Drafts for human review; never approves, authorises or signs off.

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

マルチテナント前提の設計差分から、テナント分離（データ/権限/リソース/障害影響）の抜けや越境リスクを検出

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

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.

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

テストは存在するがアサーションが実質何も検証しておらず、実装が壊れても落ちない（常に PASS する）構造を diff-time で検出する。Check 1 missing assertion（テスト本体にアサーションが無い）、Check 2 tautological assertion（定数同士・入力自身・mock の戻り値自身を assert し SUT に依存しない）、Check 3 nonexistent expected literal（assertDontSee / assertNotContains 等の期待文字列が対象ファイルに実在しない）、Check 4 stale expected value（同一 diff で対象の出力が変わったのに期待値が据え置き）、Check 5 unscoped expectation（汎用的な属性・クラスを応答全体に対して assert し対象要素にスコープされていない）、Check 6 swallowed failure（例外の握り潰しや到達しない位置のアサーションで判定が成立しない）、の 6 Check を対象とする report-only。テストの有無は test-existence、未テスト経路の量は coverage-gap、非決定性は flaky-test、命名は test-naming、JS/TS の un-awaited resolves / rejects は vitest-mock-isolation、tdd-ledger artifact ベースの RED/GREEN 検証は plangate-tdd-evidence、.only / .skip / xit / @ts-ignore と空の catch は heuristic-review.mjs の決定論検出器へ委譲する

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

Resolve Swift concurrency compiler errors, adopt approachable concurrency (SE-0466), and write data-race-safe async code. Use when fixing Sendable conformance errors, actor isolation warnings, or strict concurrency diagnostics; when adopting default MainActor isolation, @concurrent, nonisolated(nonsending), or Task.immediate; when designing actor-based architectures, structured concurrency with TaskGroup, or background work offloading; or when migrating from @preconcurrency to full Swift 6 strict concurrency.

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

Use when you need to write or improve integration tests for Quarkus — including @QuarkusTest, Dev Services for automatic container provisioning, Testcontainers via QuarkusTestResourceLifecycleManager, WireMock for external HTTP stubs, @QuarkusIntegrationTest for black-box testing against packaged artifacts, REST Assured, data isolation strategies (@TestTransaction vs @BeforeEach cleanup), and Maven Surefire/Failsafe three-tier split (*Test, *IT, *AT). This should trigger for requests such as Add or improve integration tests in a Quarkus project; Configure Testcontainers or Dev Services for Quarkus tests; Add WireMock stubs for external HTTP dependencies in Quarkus integration tests; Set up @QuarkusIntegrationTest for packaged artifact or native binary testing; Fix test data isolation or configure Maven Surefire/Failsafe split. Part of cursor-rules-java project

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

Validates versioned permission requests against a grant scope and records comparison evidence. Activate on 'validate permissions', 'permission check', 'inheritance validation', 'permission matrix', 'security validation'. NOT for runtime enforcement (use dag-scope-enforcer) or isolation management (use dag-isolation-manager).

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

Runtime enforcement of file system boundaries and tool access restrictions. Blocks unauthorized operations and logs violations. Activate on 'enforce scope', 'access control', 'boundary enforcement', 'tool restrictions', 'runtime security'. NOT for validation (use dag-permission-validator) or isolation management (use dag-isolation-manager).

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

Generates Bulkhead pattern for PHP 8.5. Creates resource isolation with semaphore-based concurrency limiting and thread pool isolation. Includes unit tests.

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

Create safe, deterministic git worktrees for large or risky workstreams. Use when tasks are complex enough to warrant isolation from the main working tree.

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

Ensures tenant isolation at query and policy level using Row Level Security, automated testing, and security audits. Prevents data leakage between tenants. Use for "multi-tenancy", "tenant isolation", "RLS", or "data security".

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

원격 환경이나 Docker에서 설치, 연동, 실제 사용자 작업을 테스트합니다. 코드 신뢰도에 따른 환경 선택부터 장애 조사와 실행 후 정리까지 다룹니다.

• 깨끗한 환경에서 패키지 설치 테스트
• 실제 서비스와의 연동 검증
• macOS, Windows, WSL2 동작 확인

AI 에이전트가 외부 정보를 읽고 도구나 파일을 조작할 때의 보안 대책을 정리합니다. 권한, 저장 경로, 접속 대상, 인증 정보 처리를 검토하고 실제 동작으로 검증합니다.

• 에이전트의 보안 대책 검토
• 사용자와 작업 영역 간 데이터 격리 확인
• 인증 정보 정리와 출력 제한 검증

Windows 데스크톱 앱을 직접 조작하는 자동 테스트를 만듭니다. 화면 요소 식별, 표시 대기, 실패 기록과 CI 연동을 다룹니다.

• Windows 앱 조작 테스트 작성
• 결과가 불안정한 GUI 테스트 조사
• 화면 요소에 안정적인 식별자 추가