fundamental-ngx: Skill for Claude Code

.claude/skills/best-practices/SKILL.md

best-practices is a skill for Claude Code from SAP/fundamental-ngx. It costs 18 tokens per session (1,244 once invoked), scanned A, original, Apache-2.0.

A review checklist for checking existing Angular code against project conventions and Angular 22 or newer practices.

In plain words
What is it for?
Use it to audit an Angular component or folder, including templates, state handling, subscriptions, styling bindings, and project-specific rules.
Why use it?
It finds patterns that are outdated, inconsistent, or unnecessarily complex without requiring a code diff.

Skill for Claude Code ✓ vendor

Written for Claude Code: allowed-tools in frontmatter. Also seen: agent in frontmatter.

This is SAP/fundamental-ngx's own configuration. It tells Claude Code how to work on fundamental-ngx itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything fundamental-ngx configures →

About the project

Fundamental Library for Angular is an SAP-maintained Angular component library implementing SAP's design system and wrapping UI5 Web Components. Angular developers use its typed UI components and higher-level composites to build SAP-style web interfaces. Catalogue entries provide skills, agents, instructions, and a rule for working with the library.

SAP/fundamental-ngx · 296 stars · on GitHub · sap.github.io

Reuse

Borrowing it

Nothing to install: this file belongs to SAP/fundamental-ngx. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/SAP/fundamental-ngx/main/.claude/skills/best-practices/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/SAP/fundamental-ngx

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for best-practices

README.md
[![agentmods](https://agentmods.dev/badge/skills/sap/fundamental-ngx/best-practices/github.svg)](https://agentmods.dev/skills/sap/fundamental-ngx/best-practices)
Your own site
<a href="https://agentmods.dev/skills/sap/fundamental-ngx/best-practices"><img src="https://agentmods.dev/badge/skills/sap/fundamental-ngx/best-practices/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for best-practices

Your own site · 80×15
<a href="https://agentmods.dev/skills/sap/fundamental-ngx/best-practices"><img src="https://agentmods.dev/badge/skills/sap/fundamental-ngx/best-practices.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,244 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00018 $0.01244
Opus 5.5 $0.00007 $0.00498
Sonnet 5.5 $0.00004 $0.00249
Haiku 4.5 $0.00002 $0.00124

Measured 9d ago against content hash 3af697153470, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

best-practices scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/best-practices/SKILL.md · 119 lines

How it starts

The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Best Practices Audit: $ARGUMENTS

If $ARGUMENTS is empty, ask the user for a component path or folder before proceeding.

Audit the code at $ARGUMENTS against the project's conventions. Unlike /review-pr which checks diffs, this audits existing code as-is.

Checklist

1. Angular 22+ Patterns

  • New code uses input() / output() / model() / linkedSignal(). Existing @Input() / @Output() decorators are acceptable.
  • host: {} in decorator — no @HostBinding() / @HostListener()
  • @if / @for / @switch — no *ngIf / *ngFor / *ngSwitch
  • No standalone: true (default since Angular 19)
  • No allowSignalWrites option in effect() (the option no longer exists)
  • DestroyRef + takeUntilDestroyed() — no custom DestroyedService
  • computed() + host: { '[class]': } — no CssClassBuilder / @applyCssClass
  • No ngClass / ngStyle (use direct bindings)

2. State Management

  • signal() only when reactive consumer exists
  • Plain properties for internal bookkeeping
  • No redundant markForCheck() after signal updates
  • BehaviorSubject only for async streams, not local state
  • effect() for signal side effects — no Subject<void> for trigger-only patterns
  • No effect() used for state derivation — use computed() or linkedSignal instead
  • linkedSignal used for mutable derived state (e.g., editable fields that reset on input change)
  • No object/array mutation in place then signal.set() with same reference — always create new references
  • No conditional signal reads creating invisible dependency gaps in effect() / computed() — tracked signals read before conditional logic

3. Dependency Injection

  • InjectionToken for contextual defaults — not @ContentChild assigning to signal inputs
  • Tokens defined near child component with { optional: true }
  • FD_ prefix for component identity tokens
  • Queries by token, not concrete class

Read the full file on GitHub · 119 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago Changed 3af697153470
  2. 2mo ago First seen · 119 lines · 18 tokens per session scan A e5ca0239a992

Subscribe to this mod's changes

best-practices is a skill published in the GitHub repository SAP/fundamental-ngx (296 stars, last pushed yesterday), licensed Apache-2.0. It adds 18 tokens to every session and 1,244 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

angular-best-practices

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.

anousss007/ng-blatui · 60 tokens

neuralng-angular

Build or update Angular 22+ interfaces with NeuralNg when exact component selection, imports, forms, accessibility, SSR, icons, or theming guidance is needed.

hasanaydin7/NeuralTech · 38 tokens

igniteui-angular-figma-to-app

Builds Angular views from Figma designs with Ignite UI for Angular, supporting Indigo.Design kits, third-party kits, and plain frames. Uses Figma, Ignite UI CLI, theming, and Playwright MCP servers. WHEN TO USE: implementing a Figma design or artboard in an Ignite UI Angular project. WHEN NOT TO USE: screenshots or…

IgniteUI/igniteui-angular · 126 tokens

igniteui-angular-generate-from-image-design

Implements Angular application views from design images using Ignite UI Angular components. Uses MCP servers (igniteui-cli, igniteui-theming, angular-cli) to discover components, generate themes, and follow best practices. WHEN TO USE: the user provides a design image (screenshot, mockup, wireframe) and wants it built…

IgniteUI/igniteui-angular · 215 tokens

igniteui-angular-theming

Generates and customizes Ignite UI for Angular themes including color palettes, typography, elevations, and component-level styles using the Sass theming system and the igniteui-theming MCP server. WHEN TO USE: users ask to theme, restyle, or style Ignite UI components, change colors or the color palette, switch…

IgniteUI/igniteui-angular · 163 tokens

igniteui-angular-grids

Provides guidance on all Ignite UI for Angular data grid types (Flat Grid, Tree Grid, Hierarchical Grid, Grid Lite, Pivot Grid) including setup, column configuration, sorting, filtering, selection, editing, grouping, summaries, toolbar, export, paging, remote data, and state persistence. WHEN TO USE: users ask about…

IgniteUI/igniteui-angular · 162 tokens