/vercel-routing

Make it your own.

In Claude Code, use the slash command and add your context. In Codex, select vercel-routing from the just-vibe skill picker, then send the same brief.

Version 0.11.0 also supports /jv vercel-routing, /just-vibe vercel-routing and /jv:vercel-routing in Claude. See shortcut setup and context examples.

What the agent does

1. Build a request table with host, path, method and expected handler, and inspect base paths.
2. Trace redirects, rewrites, filesystem and framework routing in effective precedence order with bounded read-only requests, comparing preview and production assumptions.
3. Identify loops, unmatched paths and the responsible rule.

Inputs

• URL/path, expected response, project, and deployment configuration.

Optional context: scope, references, constraints, successCriteria, environment, mode, budget.

Scope

Reads

Redirects, rewrites, headers, domains, and framework routing interactions.

Writes

Inspect/plan: inspect or propose; save requested artifacts only. Apply: edit the requested local implementation and perform relevant bounded checks while preserving unrelated work. Live data changes, remote actions and paid jobs require their resolved target and existing session authorization.

Mode

Inspect; URL/path, expected response, project, and deployment configuration. Apply for a requested routing configuration fix.

Prerequisites

Exact team/project/environment and deployment/revision when applicable; read access to relevant configuration/logs. Verify installed CLI/API support and framework behavior during implementation. Never print environment values or infer promotion authorization from a preview request.

Expected output

• Route matrix with observed status, location and content type, the responsible rule and cause, and a proposed configuration patch; apply mode makes a requested fix.

How the work is checked

• Redirect loops are identified; API routes are not swallowed by a catch-all SPA rewrite.

When to stop or clarify

• No DNS or custom-domain mutation implicitly. Distinguish framework behavior from platform configuration and unavailable network evidence.

Handling missing context

Infer

Read the linked project, team, framework, environment and deployment SHA from local config and supplied deployment evidence.

Assume

Diagnose locally with existing build scripts when deployment access is missing; do not infer a production target from a preview URL.

Ask

Resolve a missing deployment/team/environment before the dependent remote operation; names and scope suffice without exposing environment values.

Technical guidance

Evidence

Inspect framework routes, platform rewrites/redirects, domain target, base path and effective response headers.

Method

Follow one URL through each routing layer; check precedence and loops with redirect following bounded.

Pitfall

An SPA fallback returning HTML for JavaScript or API URLs can look like HTTP success while breaking clients.

Check

Test direct nested navigation, asset MIME types, API errors, query preservation and the intended redirect status/method behavior.

Situational decisions

When a catch-all rewrite returns HTML for API or asset paths: Narrow the rule and verify reserved paths plus direct nested navigation.

The coding agent follows this workflow using its available tools. Installation does not grant service access or guarantee an outcome. Read the compatibility notes.

Keep exploring