Next Ts Playbook

Operational playbook for Next.js App Router + TypeScript + Tailwind — server/client boundary placement, caching decisions, hydration failure catalog, build-based verification. Read in full at the start of every task on this team.

49 stars 3 forksFrontend & Design Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add toffyui/ccteams

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add toffyui/ccteams --skill next-ts-playbook
Manual install
git clone --depth 1 https://github.com/toffyui/ccteams.git /tmp/ccteams
mkdir -p ~/.claude/skills
cp -r /tmp/ccteams/teams/next-ts/skills/next-ts-playbook ~/.claude/skills/next-ts-playbook

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Next.js App Router Playbook

This is the literal procedure to follow for any change in a Next.js (App Router)
+ TypeScript + Tailwind project. The single most expensive class of mistake in
this stack is putting code on the wrong side of the server/client boundary —
so the loop forces you to locate that boundary before you write anything.

## Operating loop

1. **Pin the versions before anything else.** Read `package.json` for the
   `next` and `react` versions and skim `next.config.(js|mjs|ts)` for
   redirects, rewrites, `images.remotePatterns`, and experimental flags.
   Caching defaults flipped between majors (see decision tree C) — advice
   that is correct for 14 is wrong for 15.
2. **Map the route segment.** For the route you're touching, list which of
   `page.tsx`, `layout.tsx`, `loading.tsx`, `error.tsx`, `not-found.tsx`,
   `route.ts` exist (`ls app/<segment>/`). A `route.ts` and a `page.tsx`
   cannot coexist in the same segment. Note whether `loading.tsx`/`error.tsx`
   are missing — async pages without them hang blank or crash the segment.
3. **Locate the change on the RSC/client boundary.** Before writing, record
   the baseline: `grep -rn '"use client"' app/ src/ 2>/dev/null | wc -l`.
   Decide which side your change lives on using decision tree A. Every
   `"use client"` you add must be justified in your report.
4. **Read two sibling files** (a neighboring page and a neighboring
   component) and mirror their naming, import style, and data-fetching
Read the full skill on GitHub

Details

Skill name
next-ts-playbook
Path
teams/next-ts/skills/next-ts-playbook/SKILL.md
License
MIT
Repo updated
31 August 2026

FAQ

What does the Next Ts Playbook skill do?

Operational playbook for Next.js App Router + TypeScript + Tailwind — server/client boundary placement, caching decisions, hydration failure catalog, build-based verification. Read in full at the start of every task on this team.

How do I install the Next Ts Playbook skill?

Claude Code plugin: /plugin marketplace add toffyui/ccteams. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Next Ts Playbook popular?

It lives in toffyui/ccteams, which has 49 GitHub stars and 3 forks.

Related skills

Choose Team

49

toffyui/ccteams

Pick and apply the best ccteams agent team for a described need using natural language — reads team metadata, selects the closest match, and applies it.

AI, LLMs & Agents

Debug Playbook

49

toffyui/ccteams

Operational playbook for systematic debugging — hypothesis ledgers, discriminating experiments, mechanism sentences, minimal fixes, sibling hunts. Read in full at the start of every bug investigation.

Software Development

Django Playbook

49

toffyui/ccteams

Operational playbook for Django + DRF — settings/version detection, ORM loading strategy, migration discipline, serializer field hygiene, timezone rules, and exact verification commands. Read in full at the start of every task on this team.

Software Development

Obsidian Canvas Create

62

ElliotJLT/Claude-Skill-Potions

Generates Obsidian .canvas files from intent. Takes a description of what you want to visualise and produces valid JSON Canvas — mind maps, flowcharts, kanban boards, research canvases, project overviews. Activates on "create canvas", "make a board", "visualise", "map out", "mind map", or when spatial organisation of ideas is needed.

Frontend & Design

Frontend Playbook

49

toffyui/ccteams

Operational playbook for framework-agnostic UI/UX/a11y — semantic-element-first markup, keyboard/focus verification, responsive layout checks, reuse of existing tokens over new CSS. Read in full at the start of every task on this team.

Frontend & Design

Replay UX Audit

48

amplitude/mcp-marketplace

Finds and analyzes Amplitude Session Replays to surface UX friction patterns across multiple sessions. Produces a ranked friction map showing where users struggle, hesitate, or abandon. Use when a PM or designer asks "where's the friction", "what's confusing users", "UX issues on this page", "why is this flow clunky", "audit the user experience", or wants qualitative evidence of usability problems in a specific feature or flow.

Frontend & Design12

Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.