web-nextjs

Conventions for building web projects with Next.js, Tailwind CSS, Supabase, and Vercel. Next.js organizes pages and server code, Supabase provides data storage and sign-in, and Vercel hosts the site.

In plain words
What is it for?
Use it when building or extending a web project with the listed tools, including pages, forms, dashboards, authentication, and deployment.
Why use it?
It gives agents a shared folder structure and standard ways to handle pages, reusable components, data connections, private pages, and configuration settings.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/sso-ss/vibe-ship-it/web-nextjs
Any agent
npx skills add sso-ss/vibe-ship-it --skill web-nextjs
Clone the repo
git clone --depth 1 https://github.com/sso-ss/vibe-ship-it

Made for: Claude Code, Codex.

Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,223 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00026 $0.01223
Opus 5 $0.00013 $0.00611
Sonnet 5 $0.00005 $0.00245
Haiku 4.5 $0.00003 $0.00122

Measured yesterday against content hash 7694ca071d0f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

web-nextjs scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/platforms/web-nextjs/SKILL.md · 161 lines

How it starts

The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Web Platform: Next.js

The default web stack. Next.js App Router + Tailwind CSS + Supabase + Vercel.

Project Structure

Explain to the designer as:

"Your project is organized into folders. Think of each folder as a room with a specific purpose."

src/
  app/                    ← Pages (each folder = a page on your site)
    page.tsx              ← Home page (yourdomain.com/)
    layout.tsx            ← The wrapper around every page (nav, footer)
    about/
      page.tsx            ← About page (yourdomain.com/about)
    contact/
      page.tsx            ← Contact page (yourdomain.com/contact)
    dashboard/
      page.tsx            ← Dashboard (yourdomain.com/dashboard)
    login/
      page.tsx            ← Login page (yourdomain.com/login)
    actions.ts            ← Server actions (code that saves data)
  components/             ← Reusable pieces (navigation, footer, cards)
  utils/
    supabase/
      server.ts           ← Server-side database connection
      client.ts           ← Browser-side database connection
  middleware.ts           ← Page protection (bouncer for private pages)

public/                   ← Static files (images, favicon)
.env.local                ← Secret settings (database keys, API keys)

Key Conventions

Server vs Client Components

Don't explain "server components" and "client components" in those terms. Say:

  • Default (server): "This code runs on the server before the page is sent to the visitor. Good for loading data from the database."
  • 'use client': "This code runs in the visitor's browser. Needed when things are interactive — forms, buttons that do stuff, anything that changes on screen."

Rule of thumb:

  • Page shows data from database → server component (default, no directive)
  • Page has interactive elements (forms, modals, toggles) → add 'use client' at the top

Server Actions

Explain as: "Code that runs when someone submits a form."

'use server'

export async function doSomething(formData: FormData) {
  // This runs on the server, not in the visitor's browser
  // Safe to access the database here
}

Read the full file on GitHub · 161 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 161 lines · 26 tokens per session scan A 7694ca071d0f

Subscribe to this mod's changes

web-nextjs is a skill published in the GitHub repository sso-ss/vibe-ship-it (10 stars, last pushed 4mo ago), licensed MIT. It adds 26 tokens to every session and 1,223 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens