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.
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.
curl -O https://raw.githubusercontent.com/SAP/fundamental-ngx/main/.claude/skills/setup-project/SKILL.mdgit clone --depth 1 https://github.com/SAP/fundamental-ngxWrote 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.
[](https://agentmods.dev/skills/sap/fundamental-ngx/setup-project)<a href="https://agentmods.dev/skills/sap/fundamental-ngx/setup-project"><img src="https://agentmods.dev/badge/skills/sap/fundamental-ngx/setup-project/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.
<a href="https://agentmods.dev/skills/sap/fundamental-ngx/setup-project"><img src="https://agentmods.dev/badge/skills/sap/fundamental-ngx/setup-project.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.02027 |
| Opus 5.5 | $0.00000 | $0.00811 |
| Sonnet 5.5 | $0.00000 | $0.00405 |
| Haiku 4.5 | $0.00000 | $0.00203 |
Grade A, and why
setup-project 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.
How it starts
The opening of the file, as written. The whole thing — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup Project: $ARGUMENTS
If $ARGUMENTS is empty, ask: (1) project name, (2) preferred SAP theme (default: horizon).
Phase 1: Check Prerequisites
node --version # must be ≥ 18.19
ng version # Angular CLI must be installed
If Angular CLI is missing:
npm install -g @angular/cli
Report both versions. If Node < 18.19, stop and tell the user to upgrade Node before continuing.
Phase 2: Create Angular Project
If the user does not already have a project:
ng new [project-name] \
--routing \
--style=scss \
--ssr=false \
--package-manager=npm
cd [project-name]
If the user has an existing project, ask for its root path and cd there, then skip to Phase 3.
Phase 3: Install fundamental-ngx
Attempt ng add first:
ng add @fundamental-ngx/core
ng add installs peer dependencies and patches angular.json. However, it is known to fail with "Can not add index to parent of type array" on the budget update step, and may silently skip the styles patch even when it reports success. After it runs:
- Check that
angular.json"styles"array was updated (see Phase 4). If not, apply the patch manually. - Check that
package.jsonnow listsfundamental-stylesand@sap-theming/theming-base-content. If not, install manually.
If ng add fails entirely (exit code 1) or the environment is offline, install manually:
npm install \
@fundamental-ngx/core \
@fundamental-ngx/platform \
@fundamental-ngx/cdk \
@fundamental-ngx/i18n \
@angular/cdk \
fundamental-styles \
@sap-theming/theming-base-content
Note:
@fundamental-ngx/platformis not installed byng add @fundamental-ngx/core. If you plan to use platform form components (fdp-*), install it too.
Phase 4: Configure Theme
Ask the user which theme they want, or use the argument. Map to file paths:
| Theme name | CSS variable file |
|---|---|
horizon (default) |
sap_horizon/css_variables.css |
horizon-dark |
sap_horizon_dark/css_variables.css |
quartz |
sap_fiori_3/css_variables.css |
quartz-dark |
sap_fiori_3_dark/css_variables.css |
hcb |
sap_hcb/css_variables.css |
hcw |
sap_hcw/css_variables.css |
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.
- 9d ago Changed · -1 lines 01f601479a78
- 2mo ago First seen · 210 lines · 0 tokens per session scan A de89812fcc4f
setup-project is a skill published in the GitHub repository SAP/fundamental-ngx (296 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,027 tokens. 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.
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.
neuralng-angular
Build or update Angular 22+ interfaces with NeuralNg when exact component selection, imports, forms, accessibility, SSR, icons, or theming guidance is needed.
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-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-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-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…