fundamental-ngx: Skill for Claude Code

.claude/skills/build-page-layout/SKILL.md

build-page-layout is a skill for Claude Code from SAP/fundamental-ngx. It costs 34 tokens per session (3,678 once invoked), scanned A, original, Apache-2.0.

A procedure for building Angular page layouts with a collapsible header, optional subheader, content area, footer, and tabs. Angular is a framework for building web applications.

In plain words
What is it for?
Use it to create pages in an existing NX monorepo or a standalone Angular app, with headers, filters, tabs, floating action bars, or flexible column layouts.
Why use it?
It provides a consistent way to decide the page structure and the correct reusable layout component before implementation.

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/build-page-layout/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 build-page-layout

README.md
[![agentmods](https://agentmods.dev/badge/skills/sap/fundamental-ngx/build-page-layout/github.svg)](https://agentmods.dev/skills/sap/fundamental-ngx/build-page-layout)
Your own site
<a href="https://agentmods.dev/skills/sap/fundamental-ngx/build-page-layout"><img src="https://agentmods.dev/badge/skills/sap/fundamental-ngx/build-page-layout/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 build-page-layout

Your own site · 80×15
<a href="https://agentmods.dev/skills/sap/fundamental-ngx/build-page-layout"><img src="https://agentmods.dev/badge/skills/sap/fundamental-ngx/build-page-layout.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,678 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 warn 7 Sept 2026
SkillSpector: 1 finding, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Memory Poisoning · line 172
    Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.
    Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
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.00034 $0.03678
Opus 5.5 $0.00014 $0.01471
Sonnet 5.5 $0.00007 $0.00736
Haiku 4.5 $0.00003 $0.00368

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

Security

Grade A, and why

build-page-layout 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/build-page-layout/SKILL.md · 338 lines

How it starts

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

Build Page Layout: $ARGUMENTS

If $ARGUMENTS is empty, ask the user: (1) what this page displays, (2) whether it needs tabs, a collapsible subheader, or a floating footer.

Phase 1: Determine Scope

Parse from $ARGUMENTS or ask:

  • Project type: nx (existing NX monorepo library/app) | standalone (fresh Angular CLI app — needs full setup)
  • Page name (PascalCase, e.g., ProductDetail, OrderList)
  • Base component: fd-dynamic-page (core, sufficient for most cases) | fdp-dynamic-page (platform — needed only if using fdp-icon-tab-bar or the tabChange output event)
  • Sections needed (check all that apply):
    • header — title, subtitle, breadcrumb, global/layout actions (default: yes)
    • subheader — collapsible section below the header with metadata or filters
    • tabs — multiple content sections, each on its own tab
    • footer — floating action bar (Save / Cancel buttons)
    • fcl — page is a column inside fd-flexible-column-layout
  • Header actions: global actions (left-aligned toolbar) and/or layout actions (right-aligned)

Default to fd-dynamic-page with header + one content area unless the user specifies otherwise.

Standalone app setup (skip for NX projects)

If project type is standalone, run these steps before generating the component: Replace APP_NAME, VERSION, PEER_VERSION, and ANGULAR_MAJOR with the desired app name and resolved published versions before running them.

# 1. Create the app (--standalone is accepted but is the default since Angular 19, so it's a no-op)
ng new APP_NAME --routing=true --style=scss --skip-git --package-manager=npm

# 2. Resolve the exact @fundamental-ngx version and fundamental-styles peer version first
npm show @fundamental-ngx/core version          # → e.g. 0.62.2
npm show @fundamental-ngx/core peerDependencies  # → check fundamental-styles exact pin

# 3. Install @fundamental-ngx and peer deps (--legacy-peer-deps is required to resolve Angular CDK peer conflicts)
cd APP_NAME
npm install --legacy-peer-deps \
  @fundamental-ngx/core@VERSION \
  @fundamental-ngx/cdk@VERSION \
  @fundamental-ngx/i18n@VERSION \
  fundamental-styles@PEER_VERSION \
  "@angular/cdk@^ANGULAR_MAJOR.0.0" \
  @sap-theming/theming-base-content

Read the full file on GitHub · 338 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 b912f9907749
  2. 2mo ago First seen · 338 lines · 34 tokens per session scan A 00efbd1c366b

Subscribe to this mod's changes

build-page-layout is a skill published in the GitHub repository SAP/fundamental-ngx (296 stars, last pushed yesterday), licensed Apache-2.0. It adds 34 tokens to every session and 3,678 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