Skip to main content
Next.jsApp Routeradvanced

Next.js Edge Middleware & Session Gatekeeper

Optimized for Claude, Chatgpt • Verified Prompt Template

Design lightweight edge middleware for route protection, JWT validation, multi-tenant rewrites, and security headers.

Compatibility & Specs

Compatible AI Models
ClaudeChatGPT
Last UpdatedApr 1, 2026
Customizable Variables3 parameters

How to Use This Prompt

Follow this 3-step workflow to extract high-signal responses from any compatible AI model.

01

1. Tailor the Parameters

Use the interactive customizer above to substitute the bracketed placeholders with your exact context, requirements, and constraints.

02

2. Send to AI Model

Copy the prompt and paste it into Claude, ChatGPT, Gemini, or Copilot. These models follow structured multi-step constraints reliably.

03

3. Review and Iterate

Review the output against the verified benchmark below. Follow up in the conversation to stress-test edge cases or refine tone.

Prompt Variables & Parameters

Reference breakdown of every dynamic variable embedded in this prompt template.

PlaceholderParameter NameTypeStatusDescription & Guidance
[routing_requirements]Routing RequirementstextareaRequiredProtected paths, public paths, and dynamic rewritesDefault: 1. Protect `/dashboard/*`, `/workbench/*`, and `/settings/*`; 2. Allow public access to `/`, `/prompts/*`, `/categories/*`, `/api/webhooks/*`; 3. Preserve requested URL in query param `?returnTo=` on redirect.
[auth_mechanism]Authentication MechanismtextRequiredHow session tokens are validatedDefault: HTTP-only secure session cookie containing a signed JWT verified via JOSE and Web Crypto
[security_needs]Security & Multi-Tenant NeedstextOptionalSpecial security headers or subdomain mappingDefault: Strict security headers (HSTS, X-Content-Type-Options, Frame-Options DENY) and rate-limit header passthrough

Example Output & Parameters Breakdown

Inspect verified benchmark AI responses and review how parameters, system constraints, and input variables calibrate generation.

Parameters & Variable Breakdown

3 Inputs
[routing_requirements]
1. Protect `/dashboard/*`, `/workbench/*`, and `/settings/*`; 2. Allow public access to `/`, `/prompts/*`, `/categories/*`, `/api/webhooks/*`; 3. Preserve requested URL in query param `?returnTo=` on redirect.
[auth_mechanism]
HTTP-only secure session cookie containing a signed JWT verified via JOSE and Web Crypto
[security_needs]
Strict security headers (HSTS, X-Content-Type-Options, Frame-Options DENY) and rate-limit header passthrough

Verified AI Benchmark Response

Grounded Output
### Production `middleware.ts` Implementation ```typescript import { NextResponse } from 'next/server'; import type { NextRequest } from 'next/server'; import { jwtVerify } from 'jose'; const SECRET_KEY = new TextEncoder().encode(process.env.JWT_SECRET_KEY || 'default-dev-secret'); const PROTECTED_PREFIXES = ['/dashboard', '/workbench', '/settings']; export async function middleware(request: NextRequest) { const { pathname } = request.nextUrl; // 1. Check if path requires authentication const isProtected = PROTECTED_PREFIXES.some((prefix) => pathname.startsWith(prefix)); if (isProtected) { const token = request.cookies.get('session_token')?.value; if (!token) { const loginUrl = new URL('/login', request.url); loginUrl.searchParams.set('returnTo', pathname); return NextResponse.redirect(loginUrl); } try { // Edge-compatible JWT verification using Web Crypto (jose) await jwtVerify(token, SECRET_KEY); } catch (err) { // Expired or invalid signature const loginUrl = new URL('/login', request.url); loginUrl.searchParams.set('returnTo', pathname); const response = NextResponse.redirect(loginUrl); response.cookies.delete('session_token'); return response; } } // 2. Attach Strict Security Headers const response = NextResponse.next(); response.headers.set('X-Frame-Options', 'DENY'); response.headers.set('X-Content-Type-Options', 'nosniff'); response.headers.set('Referrer-Policy', 'strict-origin-when-cross-origin'); response.headers.set('Strict-Transport-Security', 'max-age=63072000; includeSubDomains; preload'); return response; } export const config = { matcher: ['/((?!_next/static|_next/image|favicon.ico|api/webhooks).*)'], }; ```

Best Use Cases

Scenarios and roles where this prompt produces maximum leverage.

Next.js full-stack teams protecting private dashboard routes with sub-millisecond edge latency
Architects preventing unauthorized access without spinning up heavy Node.js server runtimes
Developers adding mandatory enterprise security headers across all web responses

Tips for Best Results

Techniques to elevate response fidelity

  • •Specify your exact runtime and dependency versions (e.g. Next.js 15, React 19, TypeScript 5.4) to eliminate outdated syntax hallucinations.
  • •Ask the model to enumerate potential runtime failure modes, concurrency issues, or null boundary states before generating code.
  • •Request idiomatic, type-safe solutions with clear unit test skeletons rather than monolithic scripts.

Common Mistakes to Avoid

Frequent failure modes and anti-patterns

  • •Pasting large unformatted code dumps without indicating the specific function or error you want analyzed.
  • •Deploying AI-generated code directly to production without verifying memory safety, edge cases, and security vulnerabilities.
  • •Omitting architectural constraints (such as SSR vs. client component boundaries or database indexing).

Frequently Asked Questions About This Prompt

Technical guidance on model compatibility, parameter substitution, iteration techniques, and commercial usage.

Q1.Which AI models work best with the "Next.js Edge Middleware & Session Gatekeeper" prompt?

This prompt is thoroughly tested and compatible with Claude, Chatgpt. For multi-step reasoning, architectural planning, and code refactoring, Claude 3.7/3.5 Sonnet and ChatGPT-4o provide the highest constraint adherence. For large-document synthesis, Google Gemini 2.5 Pro is also recommended.

Q2.How do I customize the parameters in this prompt template?

This template features 3 customizable parameter(s): [routing_requirements], [auth_mechanism], [security_needs]. Replace each bracketed placeholder with your project's specific details, constraints, or code before submitting to your AI model. You can also use our interactive workbench on this page to populate and copy the completed prompt in one click.

Q3.Can I use this prompt and its outputs for commercial projects?

Yes. All prompts published on Beautiful AI Prompt are 100% free for both personal and commercial use. You hold full ownership of all code, copy, strategies, or imagery generated by your selected AI model when running this prompt.

Q4.How does this prompt prevent AI hallucinations and ensure output accuracy?

This template enforces explicit negative constraints, few-shot parameter boundaries, and schema requirements (such as tabular comparisons or step-by-step logic). This suppresses speculative drift and forces the AI model to ground its response in your provided inputs.

Part of Curated Collections

This prompt is sequenced as part of these goal-oriented workflows

View all collections

Related AI Prompts

Complementary workflows in Next.js

View all Next.js prompts
Next.jsintermediate

Next.js App Router Performance & Cache Auditor

Audit Next.js routes for static pre-rendering, cache invalidation, and Core Web Vitals optimization.

[Copy & Paste Template]3 parameters

›You are a Next.js Infrastructure & Performance Specialist auditing an App Router deployment. Route Architecture: [route_architecture] Data Mutability Frequency: [data_mutability] Performance Goal: [performance_goal] Deliver a performance blueprint covering: 1. Static vs. Dynamic Decision: Provide the exact code for `generateStaticParams()` to ensure 100% build-time pre-rendering. 2. Caching Strategy: Define the interplay between the Next.js Data Cache, Full Route Cache, and Router Cache. 3. Core Web Vitals Optimization: Actionable instructions to reduce LCP < 1.0s and ensure Cumulative Layout Shift (CLS) = 0.00. 4. Asynchronous Request APIs (Next.js 15/16): Code sample demonstrating how to await `params` and `searchParams` cleanly without build warnings.

claudechatgptperplexity
#nextjs#turbopack#caching
Codingadvanced

OWASP Security Vulnerability & Dependency Auditor

Inspect code modules for injection vulnerabilities, insecure deserialization, broken access controls, and auth flaws.

[Copy & Paste Template]2 parameters

›You are a Principal Application Security (AppSec) Engineer and Certified Penetration Tester. I need a comprehensive security code audit of the following code snippet against modern threat vectors (including the OWASP Top 10). Application Context & Environment: [application_context] Source Code to Audit: [source_code] Deliver an authoritative security audit report: 1. Executive Threat Summary: High-level risk score (Critical / High / Medium / Low) with immediate remediation priority. 2. Vulnerability Findings Matrix: For each security flaw identified, detail: (A) OWASP Category, (B) Vulnerable Lines, (C) Exploit Scenario (how an attacker would weaponize this), (D) Severity Score. 3. Secure Refactored Code: Drop-in replacement code resolving every vulnerability with parameterized queries, input sanitization, safe deserialization, and strict authorization guards. 4. Security Unit Test: Provide an automated test demonstrating that the exploit payload is safely neutralized.

claudechatgptgemini
#security-audit#owasp#vulnerability-scanning
Next.jsadvanced

Next.js Server vs. Client Component Boundary Decision Matrix

Audit page trees to push 'use client' directives to the leaves, minimize JS bundles, and maximize server streaming.

[Copy & Paste Template]3 parameters

›You are a Principal Next.js Framework Architect and React 19 Core Specialist. I am designing or refactoring a page in the Next.js App Router, and I need an authoritative audit of my Server vs. Client Component boundaries. Next.js Version: [nextjs_version] Page Description & User Interactions: [page_description] Data Sources & Sensitive Tokens: [data_sources] Deliver the Server/Client Boundary Blueprint: 1. Component Boundary Hierarchy Tree: Visual ASCII tree mapping out which components must be Server Components (RSC) vs. which must be Client Components (`'use client'`). 2. 'Push to the Leaves' Strategy: How to refactor interactive widgets (e.g. search input, favorite button, modal toggle) into tiny leaf client components while keeping heavy data fetching on the server. 3. Composition via Children Pattern: Code example demonstrating how to pass Server Components as `children` into Client Component wrappers without turning the children into client bundles. 4. Bundle Size & Security Audit: Verify that database credentials, secret API keys, and heavy server libraries (like Prisma or markdown parsers) are physically excluded from client JavaScript bundles.

claudechatgptgemini
#nextjs#server-components#client-components