인터페이스는 현지화되어 있으며, Skill 소개와 설명 문서는 선택한 언어로 AI가 자동 번역합니다. 코드·명령어·경로·전문 용어는 원문을 유지하며 원작자 문서가 우선합니다.
Skills 둘러보기
디자인 및 창작 · SKILL.md

applied-ai-architect-commercial-enterprise

applied-ai-architect-commercial-enterprise

Guides applied AI solution architecture for commercial (B2B SaaS, multi-tenant product) and enterprise (internal copilots, regulated corp data) contexts—reference patterns for RAG, agents, and copilots, platform and model selection, data boundaries, identity, observability, cost at scale, and POC-to-production hardening with security and governance gates. U…

Independent GitHub snapshot · Automated classification · Original documentation governs

Skill 문서

GitHub

name: applied-ai-architect-commercial-enterprise description: | Guides applied AI solution architecture for commercial (B2B SaaS, multi-tenant product) and enterprise (internal copilots, regulated corp data) contexts—reference patterns for RAG, agents, and copilots, platform and model selection, data boundaries, identity, observability, cost at scale, and POC-to-production hardening with security and governance gates. Use when designing customer-facing AI features, enterprise knowledge assistants, vendor LLM integration architecture, AI ADRs for commercial or IT stakeholders, or mapping AI components to SSO/DLP/residency requirements—not for implementing RAG code (ai-engineer), generic multi-service ADRs without AI (senior-system-architecture), AI policy registers (ai-risk-governance), or contract redlines (commercial-counsel). For engineering management of vertical AI product squads (hiring, roadmap, launch governance), use engineering-manager-vertical-ai-products. Labeling PM: product-management-human-data-platform—not this skill.

Applied AI Architect — Commercial & Enterprise

When to Use

  • Design end-to-end AI architecture for a B2B product feature or internal copilot
  • Choose between RAG, fine-tuning, agents, or workflow orchestration for a use case
  • Define multi-tenant isolation, data boundaries, and customer data handling for AI
  • Map enterprise requirements: SSO, audit logs, residency, DLP, human oversight
  • Compare cloud AI platforms (managed endpoints, private networking, quotas)
  • Author AI-specific ADRs for engineering, security, and procurement
  • Plan POC → pilot → production with eval, safety, and ops gates

When NOT to Use

  • Write application code, prompts, or eval harnesses → ai-engineer, prompt-engineer
  • General non-AI integration ADRs → senior-system-architecture
  • Context packing and token budgets → ai-context-engineer
  • Memory store implementation → ai-memory-developer
  • AI risk tiering and policy documents → ai-risk-governance
  • SOC 2 evidence packs → compliance-engineer
  • Token cost improvement program → ai-token-improvement-plan-engineer
  • AI ops cadence and release governance → ai-lead-ops
  • Business case and operating model → business-consultant

Related skills

NeedSkill
Build and ship RAG/agentsai-engineer
Cross-service platform ADRssenior-system-architecture
Governance and use-case classificationai-risk-governance
Security architecture and controlscybersecurity, information-security-engineer
Data platform for embeddings/warehousedata-architect
Product tenant isolationproduct-infrastructure-security-engineer
Red-team before launchai-redteam
Commercial contract termscommercial-counsel

Core Workflows

1. Classify context: commercial vs enterprise

LensCommercial (product)Enterprise (internal IT)
UsersCustomer tenantsEmployees, partners
DataCustomer content + configCorp IP, HR, regulated data
IdentityProduct auth + tenant IDIdP (Entra/Okta), groups
IsolationStrong multi-tenancyNetwork/VPC, private endpoints
BuyingSKU, usage meteringEA, private offer, on-prem option

See references/commercial_vs_enterprise.md.

2. Shape the solution

  1. Job — user outcome in one sentence; success metric
  2. Pattern — Q&A RAG, task agent, workflow automation, codegen assist
  3. Data — sources, freshness, PII, retention, who may see what
  4. Model — capability vs cost; routing; fallback
  5. Control plane — prompts, tools, policies, human approval points
  6. Plane separation — ingestion ≠ inference ≠ logging (scale independently)

See references/reference_architectures.md.

3. Non-functional requirements

Document targets for:

  • Latency (p95 first token, end-to-end task)
  • Availability and DR for inference path
  • Cost per tenant/session and guardrails
  • Auditability (prompt, retrieval IDs, model version—no secrets in logs)
  • Safety (tier, blocked topics, escalation)
  • Compliance (residency, retention, subprocessors)

See references/enterprise_nfr_integration.md.

4. Platform and vendor selection

Score options on: data handling, private link, model catalog, SLAs, metering, exit strategy.

See references/platform_selection.md.

5. AI ADR and review

For one-way doors (vendor, data leaves region, autonomous agents):

  • Options, NFR impact, security, cost model
  • Migration and rollback

See references/ai_architecture_decision.md.

Pair with senior-system-architecture for org-wide integration standards.

6. POC → production path

StageArchitecture focus
POCSingle tenant, manual eval, no prod data
PilotTenant isolation, observability, limited users
GASLOs, rate limits, on-call, eval in CI, red-team for tier-2+

See references/poc_to_production.md.

When to load references

  • Commercial vs enterprise → references/commercial_vs_enterprise.md
  • RAG, agent, copilot patterns → references/reference_architectures.md
  • SSO, DLP, logging, residency → references/enterprise_nfr_integration.md
  • Cloud AI platform choice → references/platform_selection.md
  • AI ADR template → references/ai_architecture_decision.md
  • Production hardening → references/poc_to_production.md
저장한 Skills