Expert guidance on multi-cloud architecture, cost analysis, and technical decision-making for AI platforms across AWS, GCP, Azure, and OCI. Use when comparing clouds, estimating infra cost, or making build-vs-buy and architecture trade-off decisions for an AI product.
Scanned 10/6/2026
npx -y skills add frankxai/claude-skills-library --skill ai-architecture --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Ai Architecture?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/frankxai-ai-architecture-claude-skills-library)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: ai-architecture
description: Expert guidance on multi-cloud architecture, cost analysis, and technical decision-making for AI platforms across AWS, GCP, Azure, and OCI. Use when comparing clouds, estimating infra cost, or making build-vs-buy and architecture trade-off decisions for an AI product.
version: 1.0.0
---
# AI Architecture Skill
## Purpose
Expert guidance on multi-cloud architecture, cost analysis, and technical decision-making for AI-powered platforms. Combines Oracle AI Architect expertise with FrankX brand voice.
## When to Use This Skill
Activate `/ai-architecture` when you need:
- Multi-cloud provider comparison (AWS, GCP, Azure, OCI)
- Cost analysis for AI/ML infrastructure
- Architecture patterns for creator platforms
- Technical stack recommendations
- Database and compute decisions
- AI service selection guidance
- Cloud migration strategies
## Core Principles
### 1. Provider-Agnostic Analysis
- Compare all major cloud providers fairly
- Focus on use case fit, not vendor loyalty
- Include real cost estimates and trade-offs
- Acknowledge strengths and weaknesses of each
### 2. Creator-Focused Perspective
- Frame technical decisions through creator needs
- Balance cost with capability
- Prioritize simplicity and developer experience
- Consider solo developers through enterprise teams
### 3. FrankX Voice for Technical Content
- Use studio metaphors (mixing consoles, tracks, sessions)
- Warm technical writing - accurate but accessible
- "Like choosing gear for your studio" framing
- Real-world examples from Frank's projects
### 4. Data-Driven Recommendations
- Real pricing from official sources
- Actual service capabilities, not marketing
- TCO analysis, not just sticker price
- Performance benchmarks when available
## Cloud Provider Quick Reference
**AWS**: Most services, mature ecosystem, $$$ cost, best for enterprise scale
**GCP**: AI/ML leader, clean APIs, $$ cost, best for data science
**Azure**: Microsoft integration, OpenAI access, $$ cost, best for enterprise
**OCI**: Best price-performance, Oracle integration, $ cost, best for cost optimization
## Architecture Decision Framework
- **Cost-Focused**: OCI > GCP free tier > serverless patterns
- **Ecosystem-Focused**: AWS > GCP AI tools > community support
- **Enterprise-Focused**: Azure (Microsoft) > OCI (Oracle) > compliance
- **Innovation-Focused**: GCP AI > AWS Bedrock > Azure OpenAI
## FrankX Brand Voice
Use studio metaphors when explaining technical concepts:
- "Like choosing a mixing console" → cloud provider selection
- "Session musicians you only pay when playing" → serverless functions
- "Multitrack recorder keeping everything in sync" → state management
- "Arranging tracks" → microservices orchestration
Always balance technical accuracy with warm, accessible language.
---
**Version:** 1.0
**Created:** January 14, 2026
**Expert:** Oracle AI Architect
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!