enterprise_skill

Overview

This skill provides an enterprise-grade blueprint for building high-traffic, highly available systems using microservices, Kubernetes, and Terraform. It combines AI-native methodology and Monorepo architecture patterns to streamline development, deployment, and operations at scale. Use the provided init, guide, and help actions to bootstrap projects, follow a 10-day AI-native cycle, and get infrastructure guidance.

How this skill works

The skill scaffolds a Turborepo monorepo with apps/, packages/, services/, infra/ and docs/ and generates base templates for Terraform and Kubernetes. It includes CLAUDE.md conventions, PDCA documentation categories, CI/CD patterns, and recommended tech stacks (Next.js, FastAPI, EKS, ArgoCD). Use the init action to create project structure, guide to view the enterprise development playbook, and help for infrastructure and operational best practices.

When to use it

• You need a microservices architecture for high traffic and availability
• You require Kubernetes (EKS) and Terraform infrastructure as code
• You want an AI-native, monorepo-driven development workflow
• You are a CTO, architect, or senior developer planning large systems
• You must integrate legacy systems or enforce multi-team conventions

Best practices

• Start with document-first design: write architecture and CLAUDE.md before code
• Organize a monorepo: apps/, packages/, services/, infra/ for unified context
• Use Terraform modules and Kustomize overlays for environment parity
• Adopt GitOps (ArgoCD) with CI validations and staged Argo syncs
• Enforce security rules: no hardcoded secrets, least-privilege IAM, Secrets Manager

Example use cases

• Init a new enterprise platform: enterprise init my-platform to scaffold Turborepo + infra templates
• Build backend microservices with FastAPI, separate DB schemas per service, and async messaging
• Provision EKS clusters and RDS via Terraform modules and connect ArgoCD for deployments
• Run a 10-day AI-native delivery cycle for rapid, repeatable releases with PDCA docs
• Migrate legacy services into a tiered language plan (Tier 1–4) with clear migration steps