angular-best-practices
Skill17 starsChanged 3 months agoMITView on GitHub
Official Angular v22 coding best practices — signals, standalone, native control flow, zoneless, host bindings, Signal Forms, inject(), and accessibility (WCAG AA / AXE). Use whenever writing, generating, or reviewing Angular/TypeScript code in this repo.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- AtilaMedeiros/skillstheir own version, first seen Nov 16, 2026
- xfstudio/skillstheir own version, first seen Oct 13, 2026
- kumaran-is/claude-code-onboardingtheir own version, first seen May 25, 2026
- tranhieutt/software_development_departmenttheir own version, first seen Apr 30, 2026
- ai4brands-design/claude-skillstheir own version, first seen Mar 22, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- tranhieutt/software_development_department★ 71same name
- kumaran-is/claude-code-onboarding★ 35same name
- xfstudio/skills★ 9same name
- ai4brands-design/claude-skills★ 2same name
- AtilaMedeiros/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
Show its rules and text
We split this skill into the rules it gives an agent
27 rules. 0 are common, 12 are distinctive, and 15 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
12
Distinctive
This author's own choices. Worth a look.
15
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Use strict type checking
- Distinctive: line 17
Prefer type inference when the type is obvious
- Very specific: line 18
Avoid the any type; use unknown when type is uncertain
- Distinctive: line 22
Always use standalone components over NgModules
- Very specific: line 23
Must NOT set standalone: true inside Angular decorators.
- Very specific: line 24
Do NOT set changeDetection: ChangeDetectionStrategy.OnPush explicitly.
- Distinctive: line 25
Use signals for state management
- Very specific: line 27
Do NOT use the @HostBinding and @HostListener decorators.
- Very specific: line 28
Use NgOptimizedImage for all static images.
- Distinctive: line 38
Keep components small and focused on a single responsibility
- Very specific: line 39
Use input() and output() functions instead of decorators
- Very specific: line 40
Use computed() for derived state
- Distinctive: line 41
Prefer inline templates for small components
- Very specific: line 42
Prefer Signal Forms (@angular/forms/signals) for new forms.
- Distinctive: line 43
When not using Signal Forms, prefer Reactive forms instead of Template-driven ones
- Very specific: line 44
Do NOT use ngClass, use class bindings instead
- Distinctive: line 46
When using external templates/styles, use paths relative to the component TS file.
- Distinctive: line 50
Use signals for local component state
- Distinctive: line 52
Keep state transformations pure and predictable
- Very specific: line 53
Do NOT use mutate on signals, use update or set instead
- Distinctive: line 57
Keep templates simple and avoid complex logic
- Very specific: line 58
Use native control flow (@if, @for, @switch) instead of *ngIf, *ngFor, *ngSwitch
- Distinctive: line 59
Use the async pipe to handle observables
- Very specific: line 60
Do not assume globals like (new Date()) are available.
- Very specific: line 65
Use the providedIn: 'root' option for singleton services
- Very specific: line 66
Prefer the @Service decorator over @Injectable({providedIn: 'root'}) for new singleton services (Angular v22+)
- Very specific: line 67
Use the inject() function instead of constructor injection
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Angular Best Practices (official — Angular v22)
Source: the official guide bundled in
@angular/cliand served by its MCPget_best_practicestool. The liveangular-cliMCP server is configured in.mcp.json(tools:search_documentation,get_best_practices,find_examples,list_projects) — query it for the current docs/examples.
You are an expert in TypeScript, Angular, and scalable web application development. You write functional, maintainable, performant, and accessible code following Angular and TypeScript best practices.
TypeScript Best Practices
- Use strict type checking
- Prefer type inference when the type is obvious
- Avoid the
anytype; useunknownwhen type is uncertain
Angular Best Practices
- Always use standalone components over NgModules
- Must NOT set
standalone: trueinside Angular decorators. It's the default in Angular v20+. - Do NOT set
changeDetection: ChangeDetectionStrategy.OnPushexplicitly.OnPushis the default in Angular v22+. - Use signals for state management
- Implement lazy loading for feature routes
- Do NOT use the
@HostBindingand@HostListenerdecorators. Put host bindings inside thehostobject of the@Componentor@Directivedecorator instead - Use
NgOptimizedImagefor all static images.NgOptimizedImagedoes not work for inline base64 images.
Accessibility Requirements
- It MUST pass all AXE checks.
- It MUST follow all WCAG AA minimums, including focus management, color contrast, and ARIA attributes.
Components
- Keep components small and focused on a single responsibility
- Use
input()andoutput()functions instead of decorators - Use
computed()for derived state - Prefer inline templates for small components
- Prefer Signal Forms (
@angular/forms/signals) for new forms. They are stable in Angular v22+ and provide signal-based state, type-safe field access, and schema-based validation - When not using Signal Forms, prefer Reactive forms instead of Template-driven ones
- Do NOT use
ngClass, useclassbindings instead - Do NOT use
ngStyle, usestylebindings instead - When using external templates/styles, use paths relative to the component TS file.
State Management
- Use signals for local component state
- Use
computed()for derived state - Keep state transformations pure and predictable
- Do NOT use
mutateon signals, useupdateorsetinstead
Templates
- Keep templates simple and avoid complex logic
- Use native control flow (
@if,@for,@switch) instead of*ngIf,*ngFor,*ngSwitch - Use the async pipe to handle observables
- Do not assume globals like (
new Date()) are available.
Services
- Design services around a single responsibility
- Use the
providedIn: 'root'option for singleton services - Prefer the
@Servicedecorator over@Injectable({providedIn: 'root'})for new singleton services (Angular v22+) - Use the
inject()function instead of constructor injection
ng-blatui project specifics
- Behavior layer: build accessible component behavior on Angular Aria (
@angular/aria) + Angular CDK (@angular/cdk) — do not hand-roll ARIA/keyboard/focus. - Styling: Tailwind CSS v4 + the BlatUI oklch design tokens (CSS variables) in
projects/ng-blatui/foundations/blatui.css. Every token is a CSS variable; never hard-code colors/radii. - Selectors: library prefix
bui(e.g.<bui-button>); demo app prefixapp. - Constraints: zoneless-safe and SSR-safe by default. Peer support floor is Angular 21.
- Each component ships a Storybook story (states × light/dark) used as the Playwright visual-regression target.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

