new-page

Scaffold Next.js App Router pages with Supabase auth and tRPC prefetch.

2|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/PlazaCC/antes-da-tela --skill new-page-plazacc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-page
Source: https://github.com/PlazaCC/antes-da-tela/tree/main/.agents/skills/new-page
Command: npx skills add https://github.com/PlazaCC/antes-da-tela --skill new-page-plazacc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually creating new Next.js App Router pages requires repetitive boilerplate for server components, authentication checks, metadata, and tRPC prefetching, leading to inconsistent implementations and wasted developer time.

Core Features & Use Cases

  • Server Component page (page.tsx) with automatic metadata and Supabase auth redirect.
  • Loading skeleton (loading.tsx) to improve perceived performance.
  • Error boundary (error.tsx) client component for graceful failure handling.
  • tRPC prefetch scaffold placeholder for server‑side data fetching.
  • Public page option: simply remove the auth check for unrestricted routes.

Quick Start

Use the new-page skill with the argument "dashboard" to generate a protected dashboard page under app/dashboard/.

Frequently Asked Questions about new-page

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

FAQPage Schema
How do I scaffold a Next.js App Router page with Supabase auth and tRPC prefetch?

Scaffolding a Next.js App Router page with Supabase auth and tRPC prefetch generates server-component page.tsx, loading.tsx, and error.tsx files with built-in metadata and authentication redirects automatically.

What's the best way to add a protected route in Next.js using tRPC and Supabase?

Adding a protected route in Next.js using tRPC and Supabase uses a scaffold to create server components with automatic auth redirects and tRPC prefetch placeholders, ensuring consistent protected page implementation.

Can I generate a public Next.js page without the Supabase auth redirect?

Generating a public Next.js page without the Supabase auth redirect removes the authentication check from the scaffolded server component, allowing unrestricted public access to the route.

Does the Next.js page scaffold include loading and error boundaries?

The Next.js page scaffold includes loading.tsx for loading skeletons and error.tsx as a client component error boundary to handle graceful failures and improve perceived performance.

Why do I need tRPC prefetch placeholders in Next.js server components?

tRPC prefetch placeholders in Next.js server components enable server-side data fetching setup, allowing you to inject fetched data into the initial render and avoid client-side waterfall requests.