37건 · 관련도순
Audit commercial lease compliance systems -- CAM reconciliation accuracy (pro-rata share, caps, admin fees), lease abstraction completeness, critical date tracking and deadline alerting, clause compliance monitoring (insurance certificates, permitted use, co-tenancy).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan, create, and configure production-ready Google Kubernetes Engine (GKE) clusters using the golden path Autopilot configuration. Covers Day-0 checklist, Autopilot vs Standard, networking (private clusters, VPC-native, Gateway API), security (Workload Identity, Secret Manager, RBAC hardening), observability, scaling, cost optimization, and AI/ML inference. WHEN: create GKE cluster, provision GKE environment, design GKE networking, secure GKE, optimize GKE cost, GKE autoscaling, GKE inference, GKE upgrade, GKE observability, GKE multi-tenancy, GKE batch, GKE HPC, GKE compute class.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert guide for Backend.AI distributed computing platform. Automatically activates when users ask about: - Backend.AI architecture, components (Manager, Agent, Storage Proxy, Webserver, App Proxy) - Features (session scheduling, Sokovan orchestrator, multi-tenancy, resource allocation) - APIs (REST, GraphQL), authentication, RBAC authorization - Container runtime (kernels, jail sandbox, hook library, virtual folders) - Accelerator support (CUDA, ROCm, TPU, NPU, Graphcore IPU) - Client SDKs (Python, Java, JavaScript, PHP) - Setup, requirements (Python 3.13+, Docker, PostgreSQL, Redis, etcd) - How WebUI connects to/interacts with Backend.AI backend - Plugin interfaces, development setup, infrastructure Use when user mentions "Backend.AI", "backend.ai", "Sokovan", component names, or asks about the backend platform this WebUI connects to. allowed-tools: WebFetch, Read
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Derive an execution roadmap from a project's vision/spec docs by first principles, then diff that fresh derivation against the existing roadmap to prove the task ORDER is correct. Use this whenever the user wants to review, validate, re-derive, or sanity-check an execution roadmap or delivery plan; asks whether the tasks/epics are "in the right order"; suspects a task is scheduled before its prerequisite (a producer-after-consumer / dependency-inversion error like "OpenAPI after the web client that consumes it", OR a cross-cutting inherited default like observability/auth/tenancy scheduled after the feature work that inherits it — a seam-after-consumer error); wants to find missing tasks, circular dependencies, or over-fragmented epics; or wants to compact a plan to raise velocity. Also trigger on "review the roadmap", "re-derive the plan from the spec", "is this the right build order", "check the dependency graph of our epics", "which task should come first". It reads the vision + spec corpus, decomposes actors → use-cases → modules → epics → typed tasks, identifies cross-cutting inherited-default seams, builds a real dependency graph with hard + soft (seam) edges (deterministic helper), breaks cycles, topologically orders, compacts, and emits a derived roadmap PLUS a delta report against the current one — it never blindly overwrites a hand-crafted roadmap.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when working with the multi-tenant architecture — customer DB switching, FQDN routing, tenant isolation, or cross-tenant operations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Load when working on Tier 0 Sovereign (payments, money, orders), Tier 1 Security (auth, tenancy, migrations), or Tier 2 Privacy (PII, erasure) tasks to enforce advanced model tier, Invariant-Breaker adversarial tests, and zero-PII telemetry validation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Map and attack the authentication, authorization, session, tenant, federation, and machine-identity boundaries of a system, proving whether access controls actually hold rather than whether they appear to. Use whenever work touches login, sessions, tokens, roles, permissions, multi-tenancy, password reset, invitations, OAuth/OIDC/SAML, API keys, service accounts, webhooks, admin impersonation, or any question of "can this actor do or see this thing." Prefer this over a generic security pass for identity-heavy surfaces. Part of the audit suite; inherits the shared constitution while its own job is proving or disproving access boundaries.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Security audit: OWASP Top 10, multi-tenancy, injection, auth, XSS, dependencies.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
ABP Framework cross-cutting patterns including authorization, background jobs, distributed events, multi-tenancy, and module configuration. Use when: (1) defining permissions, (2) creating background jobs, (3) publishing/handling distributed events, (4) configuring modules.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Inngest イベント駆動 Durable Execution リファレンス。バックグラウンドジョブ、長時間ワークフロー。 createFunction, step.run, step.sleep, step.waitForEvent, step.waitForSignal, step.invoke, step.sendEvent, step.sleepUntil, step.fetch, step.ai.infer, step.ai.wrap, step.metadata, inngest.send, serve, connect, checkpointing, Inngest CLI。 concurrency, throttle, debounce, rate-limit, batching, priority, idempotency, singleton, multi-tenancy フロー制御。 Realtime（channels, topics, publish, subscribe, subscription tokens, useRealtime）、 Agent Evals（scoring, group.experiment）、MCP（Dev Server / Cloud）。 デプロイ先 Next.js, Express, Hono, Cloudflare Workers, Vercel, Netlify, DigitalOcean, Render。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
ABP Framework cross-cutting patterns including authorization, background jobs, distributed events, multi-tenancy, and module configuration. Use when: (1) defining permissions, (2) creating background jobs, (3) publishing/handling distributed events, (4) configuring modules.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert Kubernetes architect specializing in cloud-native infrastructure, advanced GitOps workflows (ArgoCD/Flux), and enterprise container orchestration. Masters EKS/AKS/GKE, service mesh (Istio/Linkerd), progressive delivery, multi-tenancy, and platform engineering. Handles security, observability, cost optimization, and developer experience. Use PROACTIVELY for K8s architecture, GitOps implementation, or cloud-native platform design.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.