moai-domain-backend
Provides backend architecture and scaling guidance; use when the project targets server-side APIs or infrastructure design decisions.
Provides backend architecture and scaling guidance; use when the project targets server-side APIs or infrastructure design decisions.
Define, review, and scaffold Go service directory structures using hexagonal (ports-and-adapters / “jexagonal”) architecture and Go best practices. Use when creating or refactoring Go services, deciding package boundaries, organizing cmd/internal/api/config/deploy/migrations, or choosing layouts for common service types (HTTP REST API, gRPC API, async worker/consumer, scheduled job, CLI, multi-binary repos).
Best practices for containerizing applications with Docker.
Validate that newly designed or implemented features conform to existing architectural patterns, design decisions (ADRs), and technical standards. Includes pattern validation, ADR compliance checking, technology stack verification, and conformance scoring. Use when reviewing feature plans, validating wave designs, verifying post-implementation code, checking architectural drift, or any architecture compliance validation.
Test-driven development workflow for writing reliable, maintainable code
Design multi-container applications with Docker Compose. Covers service orchestration, networking, volumes, environment configuration, health checks, and production deployment patterns. Use when defining local development stacks or deploying multi-service applications.
Core project principles, architecture guidelines, and tech stack for the Junta monorepo application.
Apply Clean Architecture with Domain-Driven Design and Hexagonal (Ports & Adapters) patterns to backend services. Use when designing APIs, microservices, domain models, repositories, or when user mentions DDD, Clean Architecture, Hexagonal, ports and adapters, bounded contexts, aggregates, or scalable backend structure. Language-agnostic - works with Go, Rust, Python, TypeScript, Java, and any backend language.
Architecture patterns and strategies for multi-cloud deployments to avoid vendor lock-in.
Core project principles, architecture guidelines, and tech stack for the Junta monorepo application.
Approved libraries, bundle optimization, and security best practices for dependencies. Use when adding new packages, optimizing bundle size, or ensuring secure dependency management.
Docker, Docker Compose, and Kubernetes patterns for containerization and orchestration
Decompose large features into small, reviewable PRs with dependency analysis. Use when implementing features that touch 10+ files or multiple components.
Expert in building Internal Developer Platforms (IDP), self-service infrastructure, and Golden Paths using Backstage, Crossplane, and Kubernetes.
Complete patterns for containerizing applications with Docker: Dockerfiles, multi-stage builds, layer optimization, security best practices, and production-ready configurations for Python/FastAPI and Node.js/Next.js apps.
FastAPI and AWS SAM/Lambda patterns for building production-ready REST APIs. Use when creating API endpoints, implementing serverless functions (Lambda), configuring API Gateway, designing REST APIs, adding error handling, writing API tests, or working with OpenAPI specifications. Includes Pydantic models, CloudWatch logging, and pytest patterns.
Vercel deployment management for frontend apps: CLI, env vars, config, troubleshooting, rollback.
Setup automated deployment with GitHub Actions, ghcr.io, and Portainer webhooks. Supports Traefik reverse proxy and multi-service Docker Compose. Use when user wants to setup CI/CD, deployment, or Portainer integration.
Vercel CLI expert for serverless deployment. Use when users need to deploy apps, manage domains, env vars, or Vercel projects.
Vite SPA deployment to various platforms. Use when deploying React SPAs.
Serverless deployment patterns for Node.js. Use when deploying to serverless platforms.
Build production-quality Terraform infrastructure code following established style guides and best practices. Use when creating new Terraform code, setting up Terraform projects, modules, or when user mentions building/creating infrastructure, terraform, HCL, terraform modules, or .tf files. Also use when reviewing or validating existing Terraform code against standards. Applies organizational standards using progressive disclosure - loads detailed references only as needed.