Quanby-IT-Solutions

AWS infrastructure patterns for this monorepo. Infrastructure is managed in a separate turbo-infrastructure repo via Terraform modules. This app repo only contains deployment workflows (GitHub Actions) and a docker-compose for staging. Use when deploying to AWS, configuring CI/CD, or setting up GitHub environment variables.

CI/CD pipeline patterns for this monorepo using GitHub Actions. Staging deploys to EC2 via Docker Compose + Nginx. Production deploys to EC2 via ALB + ASG rolling instance refresh. Infrastructure is managed separately via Terraform in the turbo-infrastructure repo.

Docker containerization and deployment patterns for this Turborepo monorepo. Use when writing Dockerfiles, configuring docker-compose, optimizing images, or preparing production builds. Triggers on tasks involving containers, multi-stage builds, turbo prune, image optimization, or local orchestration.

Eloquent ORM + MySQL migration patterns for this monorepo. Use when defining models, writing migrations, setting up relationships, or seeding data in apps/laravel/. Triggers on tasks involving database tables, foreign keys, indexes, model factories, or seeders.

Error handling, logging, and observability patterns for this monorepo. Use when implementing exception filters, error boundaries, structured logging, CloudWatch integration, or health checks. Triggers on tasks involving error responses, exception handling, log formats, monitoring, health endpoints, or observability.

Laravel 12 / PHP 8.4 backend conventions for this monorepo. Use when adding controllers, Form Requests, Resources, middleware, routes, or any work inside apps/laravel/. Triggers on tasks involving PHP, Artisan commands, service providers, or the Laravel app directory.

Next.js 16 App Router conventions for this monorepo. Use when creating pages, layouts, route handlers, server components, client components, or working in apps/web/. Triggers on tasks involving routing, SSR, RSC, server actions, metadata, fonts, or Next.js configuration.

Orval code generation + TanStack Query patterns for the @repo/api-client package. Use when regenerating TypeScript hooks from openapi.json, implementing the custom fetcher, or consuming generated hooks in apps/web. Triggers on tasks involving orval.config.ts, api-client generation, customFetcher, TanStack Query hooks from the Laravel API, or @repo/api-client imports.

Better Auth authentication patterns for this monorepo. Use when implementing login, signup, session management, OAuth, auth guards, or working with @repo/auth. Triggers on tasks involving authentication, authorization, sessions, cookies, auth middleware, or user identity.

oRPC contract-first API design for this monorepo. Use when creating API endpoints, defining schemas, implementing controllers, building frontend hooks, or working with @repo/contracts, @orpc/contract, @orpc/server, @orpc/nest, or @orpc/client. Triggers on tasks involving API routes, Zod schemas for contracts, type-safe RPC, or end-to-end type safety.

AWS infrastructure patterns for this monorepo. Infrastructure is managed in a separate turbo-infrastructure repo via Terraform modules. This app repo only contains deployment workflows (GitHub Actions) and a docker-compose for staging. Use when deploying to AWS, configuring CI/CD, or setting up GitHub environment variables.

CI/CD pipeline patterns for this monorepo using GitHub Actions. Staging deploys to EC2 via Docker Compose + Nginx. Production deploys to ECS Fargate. Infrastructure is managed separately via Terraform in the turbo-infrastructure repo.

Security patterns and hardening practices for this monorepo. Use when implementing authentication, configuring CORS, validating input, handling secrets, securing API endpoints, or reviewing code for vulnerabilities. Triggers on tasks involving security, auth guards, env validation, CORS, CSP, rate limiting, or OWASP compliance.

Docker containerization and deployment patterns for this Turborepo monorepo. Use when writing Dockerfiles, configuring docker-compose, optimizing images, or preparing production builds. Triggers on tasks involving containers, multi-stage builds, turbo prune, image optimization, or local orchestration.

Drizzle ORM with PostgreSQL patterns for this monorepo. Use when creating database tables, writing queries, defining relations, running migrations, or working with @repo/db. Triggers on tasks involving database schema, SQL queries, table definitions, foreign keys, indexes, or the db package.

Error handling, logging, and observability patterns for this monorepo. Use when implementing exception filters, error boundaries, structured logging, CloudWatch integration, or health checks. Triggers on tasks involving error responses, exception handling, log formats, monitoring, health endpoints, or observability.

Better Auth authentication patterns for this monorepo. Use when implementing login, signup, session management, OAuth, auth guards, or working with @repo/auth. Triggers on tasks involving authentication, authorization, sessions, cookies, auth middleware, or user identity.

oRPC contract-first API design for this monorepo. Use when creating API endpoints, defining schemas, implementing controllers, building frontend hooks, or working with @repo/contracts, @orpc/contract, @orpc/server, @orpc/nest, or @orpc/client. Triggers on tasks involving API routes, Zod schemas for contracts, type-safe RPC, or end-to-end type safety.

CI/CD pipeline patterns for this monorepo using GitHub Actions. Staging deploys to EC2 via Docker Compose + Nginx. Production deploys to ECS Fargate. Infrastructure is managed separately via Terraform in the turbo-infrastructure repo.

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.