'isolation' 검색 결과

A strict code reviewer, pair programmer, debugger, and mentor for Python, Bash, Google Apps Script, JavaScript, and Swift/Apple platforms. Use when writing, reviewing, debugging, planning, or securing code, or for senior-level rigor, a security review, or mentoring. Mode triggers — REVIEW: (critique + refactor), EXPLAIN: (teach), MVP:/PROTOTYPE: (lean-but-safe), DEBUG: (root-cause), AUDIT: (report-first); default is pair-programming. Drives a spec→plan→TDD→verify loop with a deterministic-first, verify-before-asserting (anti-hallucination) discipline. Enforces a security floor (secrets, injection, input validation, isolation, least privilege, authn) and a backup/continuity floor on a phase-aware rigor ladder (Prototype→MVP→Production) — cheap ≠ insecure. Covers testing & fuzzing, SAST/secret-scan/type-check/supply-chain gates, multi-tenant data protection, resilience & DR, scalability, CI/CD, cloud/containers/DBs, and accessible UI — deep references read on demand.

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

Use the AWF (Agentic Workflow Firewall) to run commands with network isolation and domain whitelisting. Provides L7 HTTP/HTTPS egress control for AI agents.

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

Design memory provenance and tenant isolation.

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

Use when the diff stores, caches, indexes, exports, imports, migrates, soft-deletes or revokes access-controlled or multi-tenant data - policy vs query disagreement, bypass clients, tenant-less cache and object keys, signed links, derived copies (search, cache, logs, analytics), export/restore scope, migration defaults, and stale access after delete or revoke

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

Design and implement multi-tenant SaaS architectures with RLS, tenant isolation, and PostgreSQL / Desain dan implementasikan arsitektur SaaS multi-tenant dengan RLS, isolasi tenant, dan PostgreSQL.

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

Expert guide for Electron 33+ desktop application development — Electron Forge, context isolation, IPC security, native menus, auto-updates, and multi-window management / Panduan ahli pengembangan desktop Electron 33+.

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

Designs team Git workflows for branching, PRs, and releases. Use when choosing branching models, stacked PRs, merge queues, worktree isolation for agents, or collaboration rules.

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

Designs cross-session agent memory: point-in-time facts, consolidation, tenant isolation. Use when auditing user memory or Mem0/Zep. Not for repo context (dev-context-engineering).

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

Designs approval and sandbox policy for local coding agents: permission modes, isolation, network and destructive-command guards. Use when setting approvals. Not cloud sandboxes.

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

Creates and manages isolated Git worktrees for parallel agents, risky experiments, or long-running feature work while preserving the user's current checkout. Use before concurrent branch edits or when isolation makes rollback safer. Not for a trivial one-file change that is already isolated.

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

Designing database schemas, migrations, and multi-tenant architecture: RLS, tenant routing, provisioning, quotas, and isolation. Not for query-plan tuning (Tuner).

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

Seven-role depersonalised panel review of framework artefacts (KUD, criterion bank, LT definition, crosswalk, scope-and-sequence) in sequential-isolation mode. Gate rule mean>=88 AND no role<70.

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

Set up isolated git worktrees. Use when starting isolated work, or when ce-work/ce-code-review offers a worktree option; detect existing isolation first.

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

Twig coding standards and conventions for Craft CMS 5 templates. ALWAYS load this skill when writing, editing, or reviewing any .twig file in a Craft CMS project — even for small edits. Covers: variable naming (camelCase, no abbreviations), null handling (?? operator, ??? with empty-coalesce plugin), whitespace control ({%- trimming, NOT {%- minify -%}), include isolation (always use 'only'), Craft Twig helpers ({% tag %}, tag(), attr(), |attr filter, |parseAttr, |append, svg()), collect() for props and class collections, .implode(), comment headers with ========= separators on component files, and common pitfalls (snake_case, macros as components, hardcoded colors).

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

Reviews Swift code for concurrency safety, error handling, memory management, and common mistakes. Use when reviewing .swift files for async/await patterns, actor isolation, Sendable conformance, or general Swift best practices.

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

Pre-commit implementation analysis for Retail-Agentic-Commerce. Use before commits, after significant changes, or when validating Apps SDK tools, mock data, MCP communication, widget isolation, or implementation quality.

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

Security rules for operating as Clawdstein in The Agent Flywheel Hub Discord. Use when interacting with Discord users. This is a PUBLIC community server with strict data isolation.

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

Provides Kubernetes resource management, Helm chart patterns, service mesh configuration, and autoscaling strategies. Covers HPA, VPA, KEDA, operators, security contexts, and namespace isolation. Use when user mentions 'kubernetes', 'k8s', 'helm', 'istio', 'linkerd', 'service mesh', 'HPA', 'VPA', 'KEDA', 'pod security', 'resource quotas', 'operators'.

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

Auto-selects and enforces the strongest valid Python typing lane for the detected Python version and dependencies — no user input required. Use when adding or tightening type annotations, eliminating Any usage in internal code, designing boundary validators or parsers, choosing between stdlib typing (TypedDict, Protocol, dataclasses), Pydantic models, or Hypothesis property tests, addressing ty or mypy failures, or applying version-specific features (TypeIs, ReadOnly, PEP 695 generics, PEP 649 deferred evaluation). Enforces boundary isolation — raw payloads validated immediately at ingress and returned as typed internal objects.

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

Review pytest test effectiveness against authoritative contracts, relevant faults, behavior-preserving refactors, realistic boundaries, isolation, and diagnostics. Use for test-quality audits, coverage-gap reviews, regression-test changes, or mocking reviews; preserve existing project gates rather than inventing coverage targets.

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

Review test effectiveness against authoritative contracts, relevant fault detection, refactor tolerance, boundary fidelity, isolation, and diagnostic value. Use when auditing test quality, reviewing coverage gaps, improving regression protection, or assessing tests after a change.

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

Decompose a task into safe parallel sub-agent slices with explicit ownership, optional worktree isolation, per-worker plans, verification, and orchestrator-led integration. Use when the user explicitly asks for delegation, sub-agents, or parallel work and the task can be split into non-overlapping scopes.

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

Operate E2B agent sandboxes using the CLI. Use when user needs to run code in isolation, test packages, execute commands safely, or work with binary files in a sandbox environment. Keywords: sandbox, e2b, isolated environment, run code, test code, safe execution.

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

Аудит пользовательской инсталляции IWE. Запускает scripts/iwe-audit.sh + MCP healthcheck + smoke-test ритуала через sentinel-механику (контракт dry-run-contract.md), передаёт отчёт subagent'у в роли VR.R.002 Аудитор (context isolation) → verdict ✅/⚠️/❌ по 6 компонентам (Inventory, L1 drift, {{GOVERNANCE_REPO}}, L3 customizations, MCP, ритуал). Используй после restore из бэкапа, после update.sh, или при еженедельной сверке.

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