09:13one minute later
The AI answers in seconds. It compiles, and the list shows up.
You would probably merge it. Most Angular on the internet looks like this, so this is what a model learns to write.
Angular 22 · TypeScript 6.0 · signals · NgRx SignalStore
Angular Philosophies is how I write Angular apps, written down: twelve chapters you can read, and the same advice as 132 rules your AI tool follows while it works. For Angular 22.
order-list.component.ts+377 review comments
Pick your tool. Every line installs the same rules.
The skill and an MCP server in one install. The skill loads when you do Angular work.
/plugin marketplace add tomavic/angular-philosophies
/plugin install angular-philosophies@angular-philosophiesA drop-in AGENTS.md at your project root, for Codex, Copilot, Gemini CLI and more.
curl -o AGENTS.md https://raw.githubusercontent.com/tomavic/angular-philosophies/main/ai/AGENTS.mdRun it from your project root. The rules land in .cursor/rules.
mkdir -p .cursor/rules && curl -sSL https://github.com/tomavic/angular-philosophies/archive/refs/heads/main.tar.gz | tar -xz --strip-components=3 -C .cursor/rules angular-philosophies-main/ai/cursorNo file access? Give it llms-full.txt, the whole guide in one file.
https://raw.githubusercontent.com/tomavic/angular-philosophies/main/ai/llms-full.txtIf your project has its own rules, write them above the generated ones. The project wins over the guide.
Twelve chapters, each ending with its rules. Short on time? Start with 03.
Structure
00PhilosophyBuild only what is needed, put each kind of code in one place, and make the right thing the easy thing.6 rules 01ArchitectureHow the workspace is divided into domains and layers, what may import what, and where new code goes.11 rules 02ComponentsStandalone, zoneless components with signal APIs, plain templates, and file naming.14 rulesState
03The signal store Start hereThe shape of a store: the facade rule, one store per view, who provides it.15 rules 04Data accessReading with resources, writing with mutations, and what a failed reload keeps.13 rules 05The toolkitWhich toolkit extensions to adopt, which to wait for, and which to avoid.8 rules 06Custom store featuresWriting your own store feature, and letting stores talk through events.8 rulesQuality
07Forms, routing, translations and right-to-leftReactive Forms, lazy routes, translations, and layouts that flip for Arabic.14 rules 08AccessibilityContrast you measure, keyboard and focus, meaning without colour.12 rules 09TestingHow to write a spec in seven steps, with fakes instead of stubs.15 rules 10Toolingpnpm, Nx, strict TypeScript, lint, format, commits and hooks.12 rules09:12Monday morning
You open Claude Code, Cursor or Copilot and type one line: an orders list with a search box and paging. The kind of page every app has ten of.
Add an orders list page with filters.
09:13one minute later
You would probably merge it. Most Angular on the internet looks like this, so this is what a model learns to write.
09:14two minutes in
Each comment quotes a rule from the guide, word for word, and says what goes wrong if you ignore it.
Angular Philosophiesline 4 · 1 of 7
Import through path aliases (@shop/..., @/...); never use ../../ across feature or library boundaries.
Three levels of ../ say where the file sits, not what it is. Move the feature and every import like this one breaks.
01 · ArchitectureAngular Philosophiesline 16 · 2 of 7
Inject dependencies with inject() in field initialisers; do not use constructors for injection.
One way to inject, everywhere: components, functions and store features all use inject(), and nothing depends on constructor order.
02 · ComponentsAngular Philosophiesline 11 · 3 of 7
Give every resource a defaultValue and { errorHandling: 'previous value' }; never write ?. or ?? on a resource value in a component.
So the template fills up with ?. and the empty state flashes before the first page arrives.
04 · Data accessAngular Philosophieslines 2, 16, 29, 30 · 4 of 7
Make a signalStore the facade, API layer and state layer for its slice; components never inject HttpClient or a data service.
Now the component owns the URL, the params and the error handling, and the next page will copy all three.
03 · The signal storeAngular Philosophieslines 3, 14, 28, 31, 34, 35 · 5 of 7
Never call .subscribe() in a component; use signals, resources or rxMethod.
Every subscribe is a leak waiting for a missed unsubscribe. This one already has to be closed in two places.
03 · The signal storeAngular Philosophieslines 19, 24, 27 · 6 of 7
Never add a load() method that a component must call after a filter changes; derive reads from state with resources.
Add a status filter tomorrow, forget one call, and the list quietly keeps showing the old result.
03 · The signal storeAngular Philosophieslines 22, 23 · 7 of 7
Reset page to 1 in every filter setter.
Search from page 3 and the server returns page 3 of the results. Usually empty, so the user thinks nothing matched. This one is a real bug.
03 · The signal storeOr the AI reads the guide before it writes the first line.
09:20eight minutes after the first prompt
The component shrinks to what a page is: a store and a template. Everything it did by hand moved into a store that reads from state. From 09:12 to 09:20: eight minutes, and nothing left to fix.
This is the store the AI writes when it follows the guide. The same code ships with the guide, and it is tested: it compiles under strict TypeScript and its tests pass.
The advice I would give you while you work, available to your AI tool while it works.