菜单
Acme Corp platform map — repository inventory, microservice architecture, service dependencies, and naming conventions. Consult this skill when you need to find which repo owns a service or understand the system topology.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when designing chaos experiments, implementing failure injection frameworks, or conducting game day exercises. Invoke for chaos experiments, resilience testing, blast radius control, game days, antifragile systems.
Use when designing cloud architectures at a strategic level — migration planning (6Rs), Well-Architected reviews, disaster recovery strategies, landing zones, or cost optimization. Not for hands-on IaC implementation (see terraform or pulumi-best-practices) or CI/CD automation (see devops). Invoke for architecture decisions, multi-account strategies, serverless design.
Use when reviewing pull requests, conducting code quality audits, or identifying security vulnerabilities. Invoke for PR reviews, code quality checks, refactoring suggestions.
Use when investigating slow queries, analyzing execution plans, or optimizing database performance. Invoke for index design, query rewrites, configuration tuning, partitioning strategies, lock contention resolution.
Use when investigating errors, analyzing stack traces, or finding root causes of unexpected behavior. Invoke for error investigation, troubleshooting, log analysis, root cause analysis.
Use when setting up CI/CD pipelines, containerizing applications with Docker, or automating deployments with GitOps. For Kubernetes-exclusive work see kubernetes, for Terraform/Pulumi IaC see terraform or pulumi-best-practices, for cloud strategy see cloud-architecture. Invoke for GitHub Actions, Docker, ArgoCD, deployment automation.
| name | acme-platform |
| description | Acme Corp platform map — repository inventory, microservice architecture, service dependencies, and naming conventions. Consult this skill when you need to find which repo owns a service or understand the system topology. |
| Repository | Domain | Language | Description |
|---|---|---|---|
acme-corp/api-gateway | Platform | Go | API gateway — routes traffic to backend services |
acme-corp/user-service | Users | Go | User management, authentication, profiles |
acme-corp/billing-service | Billing | Python | Subscription management, invoicing, payments |
acme-corp/notification-service | Comms | Go | Email, SMS, push notifications |
acme-corp/web-app | Frontend | TypeScript/React | Customer-facing web application |
acme-corp/admin-portal | Frontend | TypeScript/Vue | Internal admin dashboard |
acme-corp/infra | Platform | Terraform | Infrastructure as Code — AWS resources |
acme-corp/helm-charts | Platform | Helm | Helm charts for all services |
acme-corp/ci-cd | Platform | TypeScript | GitHub org management, team sync |
web-app → api-gateway → user-service → PostgreSQL
→ billing-service → PostgreSQL, Stripe API
→ notification-service → SES, SNS
| Environment | AWS Account | EKS Cluster | Purpose |
|---|---|---|---|
| Development | 123456789012 | acme-dev | Development and testing |
| Staging | 123456789013 | acme-staging | Pre-production validation |
| Production | 123456789014 | acme-prod | Production workloads |
acme-corp/<service-name> (kebab-case)<account>.dkr.ecr.<region>.amazonaws.com/<service-name>:<tag><service-name> in namespace <service-name>user-service, billing-service, etc.)<type>/<ticket-or-description> (e.g., feat/ACME-123-add-auth)