Workshops: Agentic Coding by Tech Stack
Agentic Coding in TypeScript & Node.js Monorepos: Workshop
In a TypeScript monorepo, one prompt can touch a dozen packages, and an agent that runs every build and test for every change is slow, expensive and easily confused. This workshop shows teams working with Nx, Turborepo or pnpm workspaces how to scope Claude Code, OpenAI Codex, GitHub Copilot or Cursor to the right packages, use the project graph for fast verification and carry out cross-package changes safely.
Who is this workshop for?
- TypeScript and Node.js developers in monorepos with several apps and shared libraries
- Platform and developer experience teams maintaining Nx, Turborepo or pnpm setups
- Full-stack teams sharing types and code between frontend, backend and tooling
- Maintainers of internal packages consumed by many applications
- Tech leads who see agents struggle with the size of their repository
What you will take away
- Structure agent context with a root file plus nested CLAUDE.md or AGENTS.md files for each app and package.
- Use affected commands and task filters so agents only build, lint and test what a change actually touches.
- Plan cross-package changes, such as breaking changes in a shared library, and execute them in reviewable steps.
- Enforce module boundaries and dependency rules so agents cannot create forbidden imports.
- Fix typical Node.js pitfalls in agent output, such as ESM and CommonJS mix-ups and misplaced dependencies.
Agenda
Module 1
Monorepo context for agents
- Root rules plus nested files per package
- How Claude Code, OpenAI Codex, GitHub Copilot and Cursor pick up instruction files
- Exercise: let the agent generate a dependency map of the workspace
Module 2
Fast, scoped verification
- nx affected, Turborepo filters and pnpm --filter
- Local and remote caching in the agent loop
- Documented commands per package
Module 3
Cross-package changes
- Exercise: change a shared library's API and update all consumers
- TypeScript project references and path aliases
- Versioning internal packages, for example with Changesets
Module 4
Boundaries and dependencies
- Module boundary rules and tags
- Dependencies in the right package.json, one version policy
- Preventing duplicated utilities across packages
Module 5
Node.js specifics
- ESM, CommonJS and TypeScript module resolution
- Shared types plus runtime validation at service boundaries, for example with Zod
- Several agents working in one monorepo without conflicts
Why monorepos overwhelm agents
A monorepo concentrates everything in one place, which is ideal for humans with good search tools and a mental map. An agent starts each session without that map: it reads the wrong package, copies a helper that already exists in a shared library or runs the complete test suite after a one-line change.
The fix is structure: clear entry points, nested instructions and verification commands that follow the project graph. That is exactly the structure we build for your repository during the workshop.
Breaking changes, done in order
Cross-package refactorings are where agents save the most time and, without a prescribed order, do the most damage. We practise a sequence that keeps every intermediate step green.
- Add the new API next to the old one
- Migrate consumers package by package, each in its own commit
- Run affected builds and tests after every step
- Remove the old API only when nothing uses it any more
Tool-neutral and repository-specific
Whether you use Nx, Turborepo, plain pnpm workspaces or a mix, we adapt the exercises to your setup. The workshop runs remotely or on-site with your repository or a sanitised copy, in English or German, and can be followed by coaching sessions for your platform team.
Frequently asked questions
Does this also work with npm or Yarn workspaces?
Yes. Scoped context, filtered tasks and staged cross-package changes work with any workspace tool. We use the commands of the package manager you already have.
Should every package get its own instruction file?
Not necessarily. Large or unusual packages benefit from their own file; small ones are covered by the root file. We help you find a structure that stays maintainable.
How is this different from a general large-codebase workshop?
This day is specific to the TypeScript and Node.js ecosystem: workspace tools, the project graph, module resolution and package publishing. General context-management techniques appear only where they apply directly.
Workshop
Get in touch
Is your monorepo ready for agents that touch more than one package at a time?
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 in TypeScript & Node.js Monorepos: Workshop · 1 day
More workshops
- Workshops: Agentic Coding by Tech StackAgentic Coding for Flutter & Dart: Workshop for App Teams
- Workshops: Agentic Coding by Tech StackReact Native & Expo with Coding Agents: From Code to Store
- Workshops: Agentic Coding by Tech StackSAP ABAP & BTP Development with AI Agents: Workshop
- Workshops: Agentic Coding by Tech StackSalesforce Development with AI Agents: Apex & LWC Workshop
- Workshops: Agentic Coding by Tech StackSQL & Databases with AI Coding Agents: Hands-On Workshop
- Workshops: Agentic Coding for Roles & IndustriesRolling Out Coding Agents Org-Wide: Workshop for Platform & DevEx
