AI-assisted development

Angular with Claude and Codex – fast, without losing the architecture

Half the code in Angular teams is now generated. That is a gain only if the result still fits your architecture. We set up the guardrails – instructions, rules, reviews – so it does.

1-day workshop in your repository
Tool-independent guardrails
Remote or on site
German or English
Based near Zurich

Book the first call See the guardrails

For engineering leads

What you need to know before you say yes

What your team gets: The speed of Claude and Codex without the slow erosion of your architecture: an instructions file, rules in CI and a review checklist that catch generated code before it merges.
What it costs: One workshop day in your repository at the training rate (from CHF 2,400 for the whole team), or a half day on top of the audit. Consulting days from CHF 1,700.
Time from your team: One day with the developers who review the most. The guardrails are running when we leave – no follow-up project.
Why it’s low-risk: Tool-independent: the guardrails work with whatever your team uses next year. Free first call, fixed quote, NDA, your approved AI plans only.

Developer? Copy this into the request to your manager

I’d like to book a one-day AI guardrails workshop with Offering Solutions (Microsoft MVP, Google Developer Expert): instructions file for Claude/Codex, architecture rules in CI and a review checklist for AI-generated code, done in our own repository. From CHF 2,400 for the whole team, fixed quote after a free first call. Details: offering.solutions/ai-assisted-angular-development/

What changes

Three things that happen when a team switches on AI tools

More code, same reviewers
A developer with Claude or Codex produces two to three times the pull requests. The people who review them are the same two seniors as before – and they become the bottleneck, or they wave things through.
The architecture erodes quietly
AI tools write what is locally plausible: a service here, a subscription there, state in the component because that is the shortest path. Nothing is wrong in isolation; after six months the boundaries you drew are gone.
Nobody can say whether it fits
The team’s conventions live in people’s heads and in old pull-request comments. The tools don’t know them, so every generated file starts from the Angular defaults, not from your defaults.

What we set up

Four guardrails that keep generated code inside your architecture

Project instructions the tools read
A short, maintained instructions file (CLAUDE.md for Claude, AGENTS.md for Codex): your folder structure, state rules, naming, what to test, what never to generate. Written together with the team, versioned with the code.
- CLAUDE.md
- AGENTS.md
- Claude Code
- Codex
Architecture rules the build enforces
Module boundaries with Nx or ESLint, dependency rules between feature, domain and UI libraries, signal-first and standalone conventions as lint rules – so the generated code fails CI instead of code review.
- Nx boundaries
- ESLint
- Architecture tests
Reviews that scale with the volume
A review checklist for AI-generated changes, an agreement on what the author must check before opening a pull request, and AI review as a first pass that leaves the humans with the decisions, not the typos.
- Review checklist
- PR template
- AI review
A team agreement on what AI may touch
Where the tools help (tests, migrations, boilerplate, refactorings with a clear goal), where they need a human first (architecture, security, state design), and how to handle secrets, customer data and licences.
- Policy
- Security
- Data protection

How to work with us

Three ways in

AI guardrails workshop
1 day · remote or on site · your repository
With your team, in your code: we write the instructions file, add the first architecture rules to CI and agree on the review checklist. You leave with the guardrails running, not with slides.
Request the workshop
AI readiness as part of the audit
Half a day on top of the Angular Frontend Audit
We look specifically at the code the tools have produced in the last months: where it fits, where it has drifted, which rules would have caught it. Findings and rules go into the audit roadmap.
Angular Frontend Audit
Consulting days
From CHF 1,700 per day · 2–10 days
For teams that want to go further: prompts and agents for your migrations, test generation that follows your patterns, or a second opinion on how far to let the tools go.
Angular Consulting

Who you’ll work with

Fabian Gosebrink

Microsoft MVP, Google Developer Expert · Builds Angular applications with teams every week and has given 120+ conference talks on Angular, state management and architecture.

Uses Claude and Codex in client projects every day – and reviews the code they produce in 10–20 Angular code bases a year.

Meet the whole team →

FAQ

Questions teams ask first

Which tools do you work with?

Claude – Claude Code in the terminal and in the IDE – and OpenAI Codex, day to day. If your team uses something else, the guardrails still apply: an instructions file, lint rules and a review checklist work with whatever tool your team adopts next year.

Is this for teams that already use AI tools, or for teams that want to start?

Both. Teams that already use them usually come because reviews can’t keep up or the architecture has started to drift. Teams that want to start get the guardrails before the first generated pull request – which is cheaper.

What about our code and the AI providers?

We work with whatever your company has approved – business or enterprise plans that don’t train on your code, or none at all. The team agreement covers secrets, customer data and what may leave the repository; we sign an NDA as a matter of course.

Does AI review replace code review?

No. It replaces the first pass – style, obvious bugs, missing tests – so the human review has time for what matters: does this fit the architecture, is it the right change. The checklist makes that explicit.

How do you use AI yourselves?

Every day, for exactly the things above: migrations, tests, boilerplate, first drafts. This website was built that way. We also see where it goes wrong, which is why the guardrails exist.

Book the first call