Agent skill · Security

Enterprise AI Patterns

Production-grade AI architecture patterns for enterprise - security, governance, scalability, and operational excellence

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill enterprise-ai-patterns-frankxai-ai-architect --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 24 KB
Bundled scripts: none
Version: 1.1.0
Path: skills/ai-llm/enterprise-ai-patterns-frankxai-ai-architect/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

Review
written from the skill's own SKILL.md · Aug 5, 2026

What it does

The skill positions the agent as an expert in enterprise-grade AI architecture patterns and provides structured patterns across pillars such as Security, Governance, Scale, and Operations. It outlines concrete patterns including an AI Gateway Architecture, Model Registry & Governance, AI Observability Stack, Prompt Management System, and AI Security Layers. Each pattern includes purpose statements, architecture diagrams, and implementation details for reference.

How it works

  • Pattern 1: AI Gateway Architecture adds a centralized entry point for AI services with authentication, rate limiting, routing, logging, caching, and a fallback mechanism. It includes a Python implementation sketch that demonstrates rate limiting, cache checks, provider routing, and a fallback path on provider failure.
  • Pattern 2: Model Registry & Governance describes a central catalog of approved models with metadata, ownership, lineage, and access control, plus an explicit lifecycle with states: DEVELOPMENT, STAGING, APPROVED, PRODUCTION, DEPRECATED, ARCHIVED.
  • Pattern 3: AI Observability Stack defines dashboards, alerting, and a data layer with metrics for latency, throughput, quality, and cost, including metrics like p50_latency_ms, p95_latency_ms, p99_latency_ms, and tokens_consumed.
  • Pattern 4: Prompt Management System treats prompts as code in a version-controlled repository, with a repository layout, CI/CD pipeline steps, and a template example for prompts with system_prompt, variables, examples, and tests.
  • Pattern 5: AI Security Layers presents a defense-in-depth model with three layers: PERIMETER (gateway, rate limiting, IP allowlisting, WAF), INPUT VALIDATION (injection detection, sanitization, length limits, content filtering), and MODEL SECURITY (incomplete text in provided excerpt but indicates continuation of security controls).

When to use it

Use when designing or auditing an enterprise AI program to ensure security, governance, scalability, and reliable operations. Triggers include terms like enterprise AI, production AI, AI governance, AI at scale, and enterprise patterns.

What it can touch

The skill declares support for tools labeled in the material as part of its architecture; it includes a concrete Python implementation sketch for the AI Gateway Pattern. The content references providers (OCI GenAI, Azure OpenAI, AWS Bedrock) and logging/monitoring components (Prometheus, Loki, Jaeger).

Caveats

Licensing is MIT. The material presents architectural patterns and example code sketches; it does not guarantee deployment outcomes and assumes enterprise context and integration with specified providers and observability stacks. The content is limited to the patterns described and does not include full production-ready code for all patterns.

From the SKILL.md

# Enterprise AI Patterns You are an expert in enterprise-grade AI architecture patterns. You help organizations build AI systems that are secure, scalable, governable, and operationally excellent. ## Enterprise AI Architecture Principles ### The Five Pillars ``` ┌─────────────────────────────────────────────────────────────────┐ │ ENTERPRISE AI PILLARS │ │ │ │ ┌───────────┐ ┌───────────┐ ┌───────────┐ ┌───────────┐ │ │ │ SECURITY │ │ GOVERNANCE│ │ SCALE │ │ OPERATIONS│ │ │ │ │ │ │ │ │ │ │ │ │ │ - IAM │ │ - Policies│ │ - Auto │ │ - Monitor │ │ │ │ - Encrypt │ │ - Audit │ │ - Distrib │ │ - Alert │ │ │ │ - Network │ │ - Lineage │ │ - Multi- │ │ - Incident│ │ │ │ - Data │ │ - Quality │ │ region │ │ - SRE │ │ │ └───────────┘ └───────────┘ └───────────┘ └───────────┘ │ │ │ │ ┌───────────┐ │ │ │ COST │ │ │ │ │ │ │ │ - FinOps │ │ │ │ - Optimize│ │ │ │ - Budget │ │ │ └───────────┘ │ └─────────────────────────────────────────────────────────────────┘ ``` ## Pattern 1: AI Gateway Architecture ### Purpose Centralized entry point for all AI services with security, routing, and observability. ### Architecture ``` ┌─────────────────────────────────────────────────────────────────┐ │ AI GATEWAY PA

What's inside
Steps it walks through
  1. Enterprise AI Architecture Principles
  2. The Five Pillars
  3. Pattern 1: AI Gateway Architecture
  4. Purpose
  5. Architecture
  6. Implementation
  7. Pattern 2: Model Registry & Governance
  8. Model Lifecycle
  9. Pattern 3: AI Observability Stack
  10. Key Metrics
  11. Pattern 4: Prompt Management System
  12. Prompt Template
  13. Pattern 5: AI Security Layers
  14. Defense in Depth
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the Enterprise AI Patterns skill do?

Production-grade AI architecture patterns for enterprise - security, governance, scalability, and operational excellence

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill enterprise-ai-patterns-frankxai-ai-architect --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going