nextjs_specialist
Next.js 15 App Router, Server Components, SSR/SSG optimizasyonu ve modern Next.js best practices.
moai-domain-frontend
>
moai-lang-typescript
>
moai-library-nextra
>
whop-dev
Build Next.js apps for the Whop platform. For empty repos, guides users from idea to deployed app through discovery and setup. For existing projects, provides best practices for authentication, payments, webhooks, and UI. Triggers on "build me a Whop app", @whop/sdk, verifyUserToken, checkAccess, checkout flows, webhook handling, Experience/Dashboard pages, Frosted UI. Delegates to companion skills (frontend-design, vercel-react-best-practices, supabase-postgres-best-practices, web-design-guidelines) for design, performance, and database.
moai-domain-frontend
>
moai-lang-typescript
>
moai-library-nextra
>
shadcn-ui
shadcn/ui best practices for Next.js applications including component composition, Radix UI patterns, Tailwind integration, Server/Client boundaries, and preventing component duplication. Use when working with shadcn/ui components, reviewing frontend code, or when questions involve shadcn, Radix UI, component libraries, or React patterns.
Implementing Next.js with Supabase
Guides implementation of Next.js 15 App Router features with Supabase SSR. Helps choose between Server/Client Components, select correct Supabase client, and follow security patterns. Use when building pages, components, or API routes.
test-driven-development
Use when implementing any feature or bugfix in the Culinary Advisor Next.js project - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first