VladislavFurdak

Common pitfalls and fixes when building and running Next.js apps with Docker Compose on Windows/Linux. Covers .dockerignore, standalone output, port conflicts, init containers, volume mounts, and multi-platform builds.

Use right after shadcn init, before building screens — or on a Tailwind v4 App Router app that looks wrong for no obvious reason. Fixes six failures a green build misses — serif fallback fonts, content under a fixed sidebar, ignored theme tokens, hydration mismatches, vanishing navigation.

Use before writing any data layer or auth on a Next.js App Router app. Sets up Supabase with @supabase/ssr, the Next.js client — browser client, server client and session middleware, plus the local Docker stack, SQL migrations, generated types and how to deploy those migrations to a hosted project. No ORM. A plain supabase-js createClient is the wrong client here and breaks auth across the server/client boundary. Start local; a hosted project needs an account only the user can create.

Scaffolds a Next.js App Router project that shadcn/ui installs into cleanly, and repairs the upstream `shadcn init` bug that leaves such projects rendering in Times New Roman. Use BEFORE creating a Next.js app, ahead of the shadcn skill. Not for an app that already exists.

Chooses and installs a shadcn/ui theme that fits the product being built, from the twelve free shadcndesign themes, and loads the font each one needs. Use once a shadcn project exists and no visual direction has been given. Not for projects with an established brand or palette.

Designs and implements core business logic for ASP.NET web apps using Tactical and Strategic DDD. Use when user asks to "design an aggregate", "implement a use case", "model a bounded context", "create domain entities", "add domain events", "implement repository pattern", or build features with rich domain models, value objects, and Transactional Outbox. Does not use CQRS or Event Sourcing by default.

Design, scaffold, refactor, and review ASP.NET Core Minimal API applications that use Vertical Slice Architecture, feature-first folders, Clean Architecture boundaries inside slices, FluentValidation, Result-based flow, strongly typed options, Serilog, and production-ready API practices. Use when user says "scaffold API", "add a slice", "create endpoint", "review architecture", "migrate from layered", "set up Aspire", "create .slnx solution", "refactor to vertical slices", or "detect anti-patterns". Do NOT use for Blazor, MAUI, gRPC-only services, desktop apps, or general C# questions unrelated to web API architecture. Do not use MediatR or AutoMapper.