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
1---2name: ai-architecture3description: 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.4---56# AI Architecture Skill78## Purpose9Expert guidance on multi-cloud architecture, cost analysis, and technical decision-making for AI-powered platforms. Combines Oracle AI Architect expertise with FrankX brand voice.1011## When to Use This Skill1213Activate `/ai-architecture` when you need:14- Multi-cloud provider comparison (AWS, GCP, Azure, OCI)15- Cost analysis for AI/ML infrastructure16- Architecture patterns for creator platforms17- Technical stack recommendations18- Database and compute decisions19- AI service selection guidance20- Cloud migration strategies2122## Core Principles2324### 1. Provider-Agnostic Analysis25- Compare all major cloud providers fairly26- Focus on use case fit, not vendor loyalty27- Include real cost estimates and trade-offs28- Acknowledge strengths and weaknesses of each2930### 2. Creator-Focused Perspective31- Frame technical decisions through creator needs32- Balance cost with capability33- Prioritize simplicity and developer experience34- Consider solo developers through enterprise teams3536### 3. FrankX Voice for Technical Content37- Use studio metaphors (mixing consoles, tracks, sessions)38- Warm technical writing - accurate but accessible39- "Like choosing gear for your studio" framing40- Real-world examples from Frank's projects4142### 4. Data-Driven Recommendations43- Real pricing from official sources44- Actual service capabilities, not marketing45- TCO analysis, not just sticker price46- Performance benchmarks when available4748## Cloud Provider Quick Reference4950**AWS**: Most services, mature ecosystem, $$$ cost, best for enterprise scale51**GCP**: AI/ML leader, clean APIs, $$ cost, best for data science52**Azure**: Microsoft integration, OpenAI access, $$ cost, best for enterprise53**OCI**: Best price-performance, Oracle integration, $ cost, best for cost optimization5455## Architecture Decision Framework5657- **Cost-Focused**: OCI > GCP free tier > serverless patterns58- **Ecosystem-Focused**: AWS > GCP AI tools > community support59- **Enterprise-Focused**: Azure (Microsoft) > OCI (Oracle) > compliance60- **Innovation-Focused**: GCP AI > AWS Bedrock > Azure OpenAI6162## FrankX Brand Voice6364Use studio metaphors when explaining technical concepts:65- "Like choosing a mixing console" → cloud provider selection66- "Session musicians you only pay when playing" → serverless functions67- "Multitrack recorder keeping everything in sync" → state management68- "Arranging tracks" → microservices orchestration6970Always balance technical accuracy with warm, accessible language.7172---7374**Version:** 1.0 75**Created:** January 14, 2026 76**Expert:** Oracle AI Architect77
frankxai