frontend

Design frontend architectures and component systems for SaaS products.

1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/lucaspedrozaem/saasskills --skill frontend-lucaspedrozaem
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend
Source: https://github.com/lucaspedrozaem/saasskills/tree/main/skills/frontend
Command: npx skills add https://github.com/lucaspedrozaem/saasskills --skill frontend-lucaspedrozaem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many SaaS teams struggle to choose the right frontend framework, structure projects for long-term maintainability, and balance rendering/performance trade-offs across marketing pages, dashboards, and internal tools. This Skill gives pragmatic architecture guidance, library recommendations, rendering strategies, and developer workflows so teams can ship reliable UIs with predictable performance and developer experience.

Core Features & Use Cases

  • Framework selection and rationale for Next.js, React (Vite), Vue/Nuxt, SvelteKit, and Remix with SaaS-specific trade-offs.
  • Project structure recommendations (Next.js App Router layout, components, lib, hooks, stores, types) to support scalability and team collaboration.
  • State management and data fetching patterns including React Query, Zustand, server vs client components, and URL-driven state.
  • Performance and bundle-size guidance: dynamic imports, icon and dependency auditing, image optimization, and Core Web Vitals targets.
  • Forms, validation, and testing standards (React Hook Form + Zod, Vitest, Testing Library, Playwright) for production readiness.
  • Real-world use case: scaffold a SaaS dashboard with auth, team scopes, billing flows, and component composition strategies.

Quick Start

Ask the agent to scaffold a Next.js App Router SaaS starter with Tailwind, React Query, authentication routes, a reusable component library, and performance-minded dynamic imports.

Frequently Asked Questions about frontend

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure a Next.js App Router project for a scalable SaaS frontend?

Structure a scalable SaaS frontend by organizing Next.js App Router projects into dedicated directories for layouts, components, lib, hooks, stores, and types. This separation supports team collaboration and long-term maintainability across growing SaaS products.

What's the best way to manage state and data fetching in a React SaaS dashboard?

Manage state and data fetching in a React SaaS dashboard using React Query for server state, Zustand for client state, and URL-driven state for filtering. This balances rendering performance and developer experience.

When should I use server components versus client components in Next.js?

Use server components versus client components in Next.js based on data fetching needs and interactivity requirements. Server components reduce bundle size and improve Core Web Vitals, while client components handle interactivity and browser APIs.

How do I optimize frontend bundle size and Core Web Vitals for a SaaS application?

Optimize frontend bundle size and Core Web Vitals using dynamic imports, auditing icon and dependency sizes, and implementing image optimization. These techniques reduce payload and improve loading performance for SaaS applications.

Does this approach support testing standards for production-ready SaaS UIs?

Yes, this approach supports production-ready SaaS UIs by integrating testing standards using Vitest, Testing Library, and Playwright. It also includes form validation with React Hook Form and Zod for comprehensive coverage.

Can I scaffold a SaaS dashboard with authentication and billing flows using React and Tailwind?

Yes, you can scaffold a SaaS dashboard with React and Tailwind that includes authentication routes, team scopes, and billing flows. It provides reusable component composition strategies and performance-minded dynamic imports.