architecture-patterns

Architecture patterns provide decision trees that map your requirements—like data-fetching needs, state complexity, or API design—to standardized Next.js, TypeScript, and database patterns. This Skill guides you through the trade-offs to pick the optimal pattern for your use case.

Common data-fetching patterns include Server Components, React Query, and Server-Sent Events (SSE), each suited to different scenarios. This Skill provides decision guidance and quick-reference code examples for efficient data fetching based on your performance and real-time requirements.

This Skill provides recommended API patterns and templates for building endpoints consistently. It covers design principles, routing conventions, and integration with your TypeScript and Next.js stack to ensure robust, maintainable endpoints.

Yes. These patterns apply to data fetching, form handling, authentication, state management, and database queries across Next.js applications. Consistent pattern usage across your codebase reduces complexity and speeds up code reviews and feature implementation.

This Skill indexes state-management patterns for React 19 and TypeScript, plus database patterns for Drizzle ORM. Each pattern includes decision guidance to help you pick between approaches based on your data structure, performance needs, and application complexity.

Standardized patterns reduce decision-making time, prevent suboptimal implementations, and ensure consistency across your team's codebase. They provide proven solutions for common scenarios, making code reviews faster and onboarding new developers easier.