agentleFS
anousss007anousss007/ng-blatui/.claude/skills/angular-best-practices/SKILL.md

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

  • Other versions5 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 5

    1. tranhieutt/software_development_department★ 71same name
    2. kumaran-is/claude-code-onboarding★ 35same name
    3. xfstudio/skills★ 9same name
    4. ai4brands-design/claude-skills★ 2same name
    5. 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.

  • In this repository2 other files it gives its agents.

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
  1. Distinctive:

    Use strict type checking

    line 16
  2. Distinctive:

    Prefer type inference when the type is obvious

    line 17
  3. Very specific:

    Avoid the any type; use unknown when type is uncertain

    line 18
  4. Distinctive:

    Always use standalone components over NgModules

    line 22
  5. Very specific:

    Must NOT set standalone: true inside Angular decorators.

    line 23
  6. Very specific:

    Do NOT set changeDetection: ChangeDetectionStrategy.OnPush explicitly.

    line 24
  7. Distinctive:

    Use signals for state management

    line 25
  8. Very specific:

    Do NOT use the @HostBinding and @HostListener decorators.

    line 27
  9. Very specific:

    Use NgOptimizedImage for all static images.

    line 28
  10. Distinctive:

    Keep components small and focused on a single responsibility

    line 38
  11. Very specific:

    Use input() and output() functions instead of decorators

    line 39
  12. Very specific:

    Use computed() for derived state

    line 40
  13. Distinctive:

    Prefer inline templates for small components

    line 41
  14. Very specific:

    Prefer Signal Forms (@angular/forms/signals) for new forms.

    line 42
  15. Distinctive:

    When not using Signal Forms, prefer Reactive forms instead of Template-driven ones

    line 43
  16. Very specific:

    Do NOT use ngClass, use class bindings instead

    line 44
  17. Distinctive:

    When using external templates/styles, use paths relative to the component TS file.

    line 46
  18. Distinctive:

    Use signals for local component state

    line 50
  19. Distinctive:

    Keep state transformations pure and predictable

    line 52
  20. Very specific:

    Do NOT use mutate on signals, use update or set instead

    line 53
  21. Distinctive:

    Keep templates simple and avoid complex logic

    line 57
  22. Very specific:

    Use native control flow (@if, @for, @switch) instead of *ngIf, *ngFor, *ngSwitch

    line 58
  23. Distinctive:

    Use the async pipe to handle observables

    line 59
  24. Very specific:

    Do not assume globals like (new Date()) are available.

    line 60
  25. Very specific:

    Use the providedIn: 'root' option for singleton services

    line 65
  26. Very specific:

    Prefer the @Service decorator over @Injectable({providedIn: 'root'}) for new singleton services (Angular v22+)

    line 66
  27. Very specific:

    Use the inject() function instead of constructor injection

    line 67

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Angular Best Practices (official — Angular v22)

Source: the official guide bundled in @angular/cli and served by its MCP get_best_practices tool. The live angular-cli MCP 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 any type; use unknown when type is uncertain

Angular Best Practices

  • Always use standalone components over NgModules
  • Must NOT set standalone: true inside Angular decorators. It's the default in Angular v20+.
  • Do NOT set changeDetection: ChangeDetectionStrategy.OnPush explicitly. OnPush is the default in Angular v22+.
  • Use signals for state management
  • Implement lazy loading for feature routes
  • Do NOT use the @HostBinding and @HostListener decorators. Put host bindings inside the host object of the @Component or @Directive decorator instead
  • Use NgOptimizedImage for all static images.
    • NgOptimizedImage does 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() and output() 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, use class bindings instead
  • Do NOT use ngStyle, use style bindings 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 mutate on signals, use update or set instead

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 @Service decorator 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 prefix app.
  • 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.