frontend-dev-guidelines

Structure Next.js app router projects by standardizing file organization across app/, components/, and features/ directories. This enforces server component defaults, clear routing patterns, and reusable modules to deliver a cohesive, scalable codebase for team onboarding.

Configure TypeScript strictness by applying explicit props, strict types, and reusable utilities across your Next.js project. This enforces typing discipline and quality across teams, preventing runtime errors and ensuring scalable frontend development practices.

Implement consistent styling with Tailwind and Shadcn/ui by adopting standardized UI conventions and theming. This approach enforces accessible component patterns and reusable design systems across your Next.js application for a unified frontend experience.

Use server components as the default in Next.js to optimize performance, leveraging client components only when necessary. The guidelines enforce server component defaults and clear routing patterns to ensure proper rendering strategies and accessibility.

Yes, the frontend guidelines integrate with existing Next.js features by establishing a project baseline through recommended app router layouts, components directories, and typing conventions applied directly to your sample feature modules.