Scaffold New Next.js Page

VerifiedSafe

Creates a new Next.js page file with a dashboard or auth route group, optional accompanying component, and proper patterns for authentication, organization context, and loading/error states. Helps when adding a new page to the Colophony dashboard while maintaining consistency and best practices.

Sby Skills Guide Bot
DevelopmentIntermediate
6/2/2026
Claude CodeCursorWindsurf
#nextjs-scaffold#dashboard-page#page-template#auth-component

Recommended for

Automated summary

Scaffolds a new Next.js page for the Colophony dashboard with authentication and organization context.

Strengths

  • Quick scaffolding with ready-to-use templates
  • Includes auth protection and loading/error states
  • Option to create accompanying component
  • Follows project conventions

Limitations

  • Specific to Colophony project structure
  • Requires project knowledge for customization
  • Does not handle advanced form validation
When to use it

When you need to add a new page to the Colophony dashboard following project standards.

When not to use it

For pages that don't follow the dashboard layout or need custom styling.

Security analysis

Safe
Quality score90/100

The skill only scaffolds new Next.js pages and components by generating static template code into the project file structure. It does not execute any external commands, network requests, or destructive actions. There is no obfuscated or risky payload.

No concerns found

How this analysis is made

Examples

Create dashboard page
/new-page settings/privacy
Create auth page
/new-page --auth reset-password
Create page with component
/new-page --with-component reports

name: new-page description: Scaffold a new Next.js page with proper patterns for the Colophony dashboard.

/new-page

Scaffold a new Next.js page with proper patterns for the Colophony dashboard.

What this skill does

  1. Creates a new page file in apps/web/src/app/
  2. Optionally creates an accompanying component
  3. Sets up proper auth protection and organization context
  4. Includes loading and error states

Usage

/new-page settings/privacy          # Create page at /settings/privacy
/new-page organizations             # Create page at /organizations
/new-page --auth reset-password     # Create auth page (no sidebar)
/new-page --with-component reports  # Create page + component

Options

  • --auth - Create in (auth) route group (centered, no sidebar)
  • --with-component - Also create a component file
  • --editor - Require editor role
  • --admin - Require admin role

Instructions for Claude

When the user invokes /new-page [options] <name>:

1. Determine the route group

  • If --auth flag: Use apps/web/src/app/(auth)/<name>/page.tsx
  • Otherwise: Use apps/web/src/app/(dashboard)/<name>/page.tsx

2. Create the page file

For dashboard pages:

'use client';

import { ProtectedRoute } from '@/components/auth/protected-route';
import { <Name>Content } from '@/components/<name>/<name>-content';

export default function <Name>Page() {
  return (
    <ProtectedRoute requireEditor={/* true if --editor */}>
      <<Name>Content />
    </ProtectedRoute>
  );
}

For auth pages:

import { <Name>Form } from '@/components/auth/<name>-form';

export default function <Name>Page() {
  return <<Name>Form />;
}

3. If --with-component, create the component

Dashboard component at apps/web/src/components/<name>/<name>-content.tsx:

'use client';

import { trpc } from '@/lib/trpc';
import { useAuth } from '@/hooks/use-auth';
import { useOrganization } from '@/hooks/use-organization';
import { Card, CardContent, CardHeader, CardTitle } from '@/components/ui/card';
import { Skeleton } from '@/components/ui/skeleton';

export function <Name>Content() {
  const { user } = useAuth();
  const { currentOrg } = useOrganization();

  // TODO: Add your tRPC query here
  // const { data, isLoading, error } = trpc.<router>.<method>.useQuery({...});

  return (
    <div className="space-y-6">
      <div>
        <h1 className="text-2xl font-bold"><Name></h1>
        <p className="text-muted-foreground">
          TODO: Add description
        </p>
      </div>

      <Card>
        <CardHeader>
          <CardTitle>TODO: Card Title</CardTitle>
        </CardHeader>
        <CardContent>
          {/* TODO: Add content */}
          <p>Content goes here</p>
        </CardContent>
      </Card>
    </div>
  );
}

Auth component at apps/web/src/components/auth/<name>-form.tsx:

'use client';

import { useState } from 'react';
import { useRouter } from 'next/navigation';
import Link from 'next/link';
import { useForm } from 'react-hook-form';
import { zodResolver } from '@hookform/resolvers/zod';
import { z } from 'zod';
import { Button } from '@/components/ui/button';
import { Input } from '@/components/ui/input';
import {
  Card,
  CardContent,
  CardDescription,
  CardFooter,
  CardHeader,
  CardTitle,
} from '@/components/ui/card';
import {
  Form,
  FormControl,
  FormField,
  FormItem,
  FormLabel,
  FormMessage,
} from '@/components/ui/form';
import { Alert, AlertDescription } from '@/components/ui/alert';

const formSchema = z.object({
  // TODO: Add form fields
});

type FormData = z.infer<typeof formSchema>;

export function <Name>Form() {
  const router = useRouter();
  const [error, setError] = useState<string | null>(null);

  const form = useForm<FormData>({
    resolver: zodResolver(formSchema),
    defaultValues: {},
  });

  const onSubmit = async (data: FormData) => {
    setError(null);
    try {
      // TODO: Add form submission logic
      router.push('/');
    } catch (err) {
      setError(err instanceof Error ? err.message : 'An error occurred');
    }
  };

  return (
    <Card className="w-full max-w-md">
      <CardHeader>
        <CardTitle>TODO: Title</CardTitle>
        <CardDescription>TODO: Description</CardDescription>
      </CardHeader>
      <CardContent>
        <Form {...form}>
          <form onSubmit={form.handleSubmit(onSubmit)} className="space-y-4">
            {error && (
              <Alert variant="destructive">
                <AlertDescription>{error}</AlertDescription>
              </Alert>
            )}

            {/* TODO: Add form fields */}

            <Button type="submit" className="w-full">
              Submit
            </Button>
          </form>
        </Form>
      </CardContent>
      <CardFooter>
        <Link href="/login" className="text-sm text-muted-foreground hover:underline">
          Back to login
        </Link>
      </CardFooter>
    </Card>
  );
}

4. Create directory if needed

Ensure the directory structure exists before creating files.

5. Summary

Inform the user:

  • What files were created
  • What TODOs need to be filled in
  • Remind to add navigation links if needed (sidebar, header)

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/scaffold-new-next-js-page-mmbizkur/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/scaffold-new-next-js-page-mmbizkur' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/scaffold-new-next-js-page-mmbizkur/download' --output '.skill-downloads/scaffold-new-next-js-page-mmbizkur/SKILL.md.part' && mv '.skill-downloads/scaffold-new-next-js-page-mmbizkur/SKILL.md.part' '.skill-downloads/scaffold-new-next-js-page-mmbizkur/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/scaffold-new-next-js-page-mmbizkur/SKILL.md' && test -s '.skill-downloads/scaffold-new-next-js-page-mmbizkur/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/new-page' && cp -R '.skill-downloads/scaffold-new-next-js-page-mmbizkur' '.claude/skills/new-page'

Cursor
test -f '.skill-downloads/scaffold-new-next-js-page-mmbizkur/SKILL.md' && test -s '.skill-downloads/scaffold-new-next-js-page-mmbizkur/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/new-page' && cp -R '.skill-downloads/scaffold-new-next-js-page-mmbizkur' '.cursor/skills/new-page'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/scaffold-new-next-js-page-mmbizkur'

openskills read 'scaffold-new-next-js-page-mmbizkur'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/scaffold-new-next-js-page-mmbizkur/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills