Workshops: Agentic Coding by Tech Stack

Agentic Coding with React & Next.js: Workshop for Dev Teams

Coding agents write React code at high speed, but they often mix up App Router and Pages Router patterns, scatter 'use client' across the component tree and fetch data in effects. In this workshop your team learns to steer Claude Code, Cursor, GitHub Copilot or OpenAI Codex so they produce idiomatic, tested code that respects your server/client boundary.

Who is this workshop for?

  • React and Next.js developers in product teams
  • Frontend leads who define component and data-fetching conventions
  • Full-stack teams building with Server Components and Server Actions
  • Teams moving from the Pages Router to the App Router
  • Agencies delivering several React projects in parallel

What you will take away

  • Write a project rules file that tells agents which router, data-fetching patterns and component conventions your codebase uses.
  • Have agents build server and client components with a deliberate boundary instead of defaulting to client-side rendering.
  • Generate Server Actions and route handlers that validate input and check authorisation on every call.
  • Make Vitest or Jest, React Testing Library and Playwright the agent's feedback loop for every change.
  • Review agent-generated React diffs quickly with a checklist for hooks, re-renders, caching and bundle size.

Agenda

  1. Module 1

    React projects through an agent's eyes

    • Why older training data leads to outdated React patterns
    • Claude Code, Cursor, GitHub Copilot and OpenAI Codex in a Next.js repository
    • Exercise: let the agent map your routes, layouts and data flow
  2. Module 2

    Conventions as context

    • CLAUDE.md, AGENTS.md or Cursor rules for components, styling and state
    • Pointing agents to current framework documentation instead of their memory
    • ESLint, strict TypeScript and the rules of hooks as automatic correction
  3. Module 3

    Server components and data fetching

    • Exercise: a feature built from server components with a small client island
    • Caching and revalidation rules for your Next.js version
    • Server Actions, route handlers or an external API – when to use which
  4. Module 4

    Tests as the feedback loop

    • Component tests with React Testing Library
    • Playwright smoke tests for critical user flows
    • Mocking fetch calls and server data without brittle snapshots
  5. Module 5

    Review, performance and handover

    • Checklist for agent diffs: effects, keys, memoisation, bundle impact
    • Avoiding duplicated components and stray dependencies
    • Team workflow: from ticket to reviewed pull request

Where agents typically go wrong in Next.js

Most agent mistakes in React projects are not syntax errors. They are architectural drift: the code compiles, looks fine in a demo and later costs performance, security or maintainability.

  • 'use client' at the top of a page just so a single button works
  • Data fetched in useEffect although a server component could load it directly
  • Pages Router APIs such as getServerSideProps showing up in an App Router project
  • A new date or form library installed although the project already uses one
  • Secrets placed in NEXT_PUBLIC_ environment variables, which end up in the browser bundle

Security at the server/client boundary

Server Actions and route handlers are reachable over the network like any other endpoint, even if they look like ordinary functions in the code. We show how to make agents add input validation, authentication and authorisation by default, and how to keep server-only code and credentials out of client bundles.

If your source code must not leave the company, we work in a sandbox repository that mirrors your architecture.

Tailored to your setup

We work with your stack as it is: App Router or Pages Router, Vercel or self-hosted, Tailwind or CSS Modules, Redux, Zustand or TanStack Query. Plain React with Vite works just as well. The day is led by neooutput AI Code Engineers, remotely or on-site, in English or German.

Frequently asked questions

Is this workshop only for Next.js?

No. Most exercises work with any React setup, including Vite-based single-page apps. Next.js-specific modules are adapted if you do not use Next.js.

How is this different from your frontend workshop?

The frontend workshop focuses on design systems, design-to-code and UI quality across frameworks. This day goes deep into React and Next.js architecture: rendering boundaries, data fetching, Server Actions and testing.

Do you also cover v0 and other UI generators?

Briefly. Tools such as v0 from Vercel are useful for quick UI drafts. We show how to bring their output into an existing codebase so it follows your conventions instead of creating a parallel component world.

Workshop

Get in touch

Want coding agents to write React code your senior developers would approve?

Tell us roughly how many people will join and pick dates that work – we will get back to you within 24 hours with a proposal for content, format and schedule.

Prefer to talk first?

15 minutes, free and without obligation – with our AI Trainers and AI Code Engineers.

Book a call for free (opens in new tab) +49 761 519 751 50 (24/7)

Request a training / workshop

Workshop: Agentic Coding with React & Next.js: Workshop for Dev Teams · 1 day

Dates that work for you (optional)

Suggestions about 2 weeks ahead – pick as many as you like

Reply usually within 24 hours · jocapps is ISO 27001 certified · Privacy