page-generator

Generate Next.js App Router route files and page shells under src/app and src/features.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Adrienenjalbert/flex-carrer-hub --skill page-generator-adrienenjalbert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: page-generator
Source: https://github.com/Adrienenjalbert/flex-carrer-hub/tree/main/.agents/skills/page-generator
Command: npx skills add https://github.com/Adrienenjalbert/flex-carrer-hub --skill page-generator-adrienenjalbert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates consistent, production-ready Next.js App Router route files, page shells, and metadata-driven pages from a simple request, reducing manual coding time and aligning with project patterns.

Core Features & Use Cases

  • Scaffold new routes under src/app with thin route.tsx/page.tsx files
  • Create feature-owned page shells and composition under src/features
  • Reuse existing shells and metadata helpers to generate SEO-friendly metadata
  • Move page composition from src/app to feature-owned directories for better maintainability

Quick Start

Ask me to generate a new route or update an existing one, and I will output the minimal, production-ready files that follow the repository's patterns.

Frequently Asked Questions about page-generator

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

FAQPage Schema
How do I scaffold new Next.js App Router routes and pages automatically?

To scaffold Next.js App Router routes, provide a page request to generate thin route.tsx or page.tsx files under src/app, ensuring composition follows project conventions by moving logic into src/features directories.

How do I create dynamic routes in Next.js App Router with proper metadata?

Creating dynamic routes uses existing metadata helpers to generate SEO-friendly metadata for Next.js App Router pages, outputting minimal route shells that integrate with project-specific routing and composition patterns.

What is the best way to organize Next.js page composition for maintainability?

Organizing Next.js page composition involves moving logic from src/app into feature-owned directories under src/features, generating thin route files that delegate rendering to feature-level components for better maintainability.

Do I need to manually configure SEO metadata when generating Next.js pages?

You do not need to manually configure SEO metadata when generating Next.js pages; the process reuses existing metadata helpers to automatically output SEO-friendly metadata aligned with repository patterns.

Can I move existing page composition into feature-owned directories in Next.js?

You can move existing page composition into feature-owned directories by generating updated files that shift logic from src/app to src/features, maintaining thin route definitions while centralizing feature composition.