Blog
Angular + AI, done right
Practical guides on cursor rules, Angular best practices, and getting AI code assistants to write Angular the way your team actually wants.
March 2026
Why Cursor writes bad Angular code (and how to fix it)
Cursor doesn't know your Angular version, your state management choice, or your team's conventions. Without explicit rules, it guesses - and guesses wrong. Here's what's happening and how a single file fixes it.
March 2026
What are Angular cursor rules and why your project needs them
Cursor rules are plain Markdown files that tell AI code assistants how to write code for your project. For Angular, they're the difference between generated code you keep and code you delete.
March 2026
Angular Signals vs RxJS: which should your cursor rules enforce?
Signals are simpler. RxJS is more powerful. Both are valid. The real question is which one your team should standardize on - and how to make sure Cursor follows that decision.
March 2026
From *ngIf to @if: Angular's built-in control flow explained
Angular v17 introduced @if, @for, and @switch as replacements for structural directives. Here's what changed, why it matters, and how to migrate without breaking things.
March 2026
Setting up Cursor IDE for Angular development
Cursor is powerful out of the box, but it doesn't know Angular conventions by default. A few configuration steps turn it from a generic code generator into an Angular-aware assistant.
March 2026
The case for strict TypeScript in every Angular project
Strict mode catches bugs before they reach production. It also makes AI-generated code safer. Here's why every Angular project should enable it and what to expect when you do.
March 2026
Angular standalone components: why NgModules are dead
Standalone components have been the default since Angular v17. If your project still uses NgModules for new features, you're writing more code than you need to.
March 2026
How AI code assistants are changing Angular development in 2026
AI assistants write Angular code faster than ever. The problem isn't speed - it's consistency. Teams that give their AI explicit rules ship better code than teams that don't.