Workshops: Agentic Coding by Tech Stack
Agentic Coding for Angular Enterprise Apps: Workshop
Angular codebases in large companies often contain several generations of the framework at once: NgModules next to standalone components, RxJS-heavy services next to signals. Coding agents reproduce whichever pattern they saw last. This workshop shows Angular teams how to give agents a clear target architecture so they write consistent code and speed up upgrades instead of adding to the mix.
Who is this workshop for?
- Angular developers in enterprise and in-house product teams
- Frontend architects responsible for Angular guidelines
- Teams maintaining large Nx or Angular CLI workspaces
- Teams moving from NgModules to standalone components or from RxJS state to signals
- Owners of long-lived business applications such as portals, back-office tools or configurators
What you will take away
- Define a target architecture for agents: standalone or modules, signals or RxJS, inject() or constructor injection, new control flow or structural directives.
- Have agents generate components, services and forms that pass your lint rules and unit tests on the first or second attempt.
- Use agents to find and fix typical RxJS problems such as nested subscriptions and missing unsubscribes.
- Plan framework upgrades step by step with ng update and official migration schematics while the agent handles the follow-up work.
- Set up reviews that keep agent-generated Angular code readable for its long-term maintainers.
Agenda
Module 1
Angular and agents: the starting point
- Which generations of Angular patterns your codebase contains
- Claude Code, GitHub Copilot, Cursor and JetBrains AI Assistant in Angular projects
- Exercise: agent-generated architecture overview of one feature area
Module 2
A target architecture agents can follow
- Rules files with examples of a good component, service and store
- Choosing between signals, RxJS and NgRx – and writing it down
- Angular CLI generators and schematics instead of hand-written boilerplate
Module 3
Building features
- Exercise: a reactive form with validation, service and tests
- Template control flow, OnPush and change detection pitfalls
- Keeping lazy loading and routing conventions intact
Module 4
RxJS and signals
- Detecting nested subscriptions, memory leaks and race conditions
- Interop between observables and signals
- When an agent should leave working RxJS code alone
Module 5
Upgrades and migrations
- Running ng update version by version with the agent fixing the fallout
- Official migrations for standalone components and the new control flow syntax
- Test coverage as a safety net before the first upgrade step
Why Angular needs explicit rules for agents
Angular has evolved considerably while keeping older APIs working for a long time. That is good for stability, but it means an agent finds several valid ways to do the same thing, in its training data as well as in your repository. Without explicit rules it mixes them, and code reviews turn into style debates.
Together we write a short, example-based target architecture that agents and new team members alike can follow.
Upgrades without a big bang
Many enterprise teams postpone Angular upgrades because each major step touches hundreds of files. Agents change that equation: the Angular CLI and official schematics handle the mechanical part, and the agent works through the remaining compiler errors, failing tests and deprecated APIs in small, reviewable commits.
- One major version per step, never several at once
- A green test suite before and after every step
- Third-party libraries checked for compatibility first
- Mechanical and manual changes in separate pull requests
Enterprise context
Angular often powers internal business applications with long maintenance cycles and strict data protection requirements. We work in your repositories or a sandbox copy and explain which data the tools send to their providers and how business plans differ from personal accounts. Remotely or on-site, in English or German.
Frequently asked questions
We still have AngularJS code. Does this workshop help?
Yes, but differently. Moving from AngularJS to Angular is closer to a rewrite than an upgrade. Agents help analyse the old code, document behaviour and port features one by one.
Do you cover Nx workspaces?
Yes. Many Angular enterprise projects run in Nx. We show how to scope agents to individual libraries and use affected commands so they only build and test what changed.
Which test setup do you use?
Yours. Whether you run Karma and Jasmine, Jest, Vitest or Playwright for end-to-end tests, we connect the agent to your existing commands so it can verify its own changes.
Workshop
Get in touch
Shall we help your agents write Angular code that fits your architecture?
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 for Angular Enterprise Apps: Workshop · 1 day
More workshops
- Workshops: Agentic Coding by Tech StackAgentic Coding with Vue & Nuxt: Hands-On Workshop
- Workshops: Agentic Coding by Tech StackAgentic Coding for Python: Django & FastAPI Workshop
- Workshops: Agentic Coding by Tech StackAgentic Coding with Java & Spring Boot: Enterprise Workshop
- Workshops: Agentic Coding by Tech StackAgentic Coding for .NET & C#: Workshop for Dev Teams
- Workshops: Agentic Coding by Tech StackAgentic Coding with Go: Workshop for Idiomatic Go Services
- Workshops: AI Tools at WorkLegally Sound AI Image Generation: Workshop for Teams
