primeng-developer
Generates PrimeNG code and guidance for Angular projects using `primeng` with `@primeuix/themes` and `@primeuix/styles`. Covers installation, design-token theming (Aura / Lara / Nora / Material presets), Styled vs Unstyled modes, the PassThrough (`pt`) customization API, component usage across all categories (form controls, buttons, overlays, layout, data display, display, menus), ReactiveForms / Signal Forms integration, accessibility, and v18→v22 migration renames. Use when the user mentions PrimeNG, `primeng`, `p-*` components, Aura/Lara/Nora theme presets, OR when the Angular project's `package.json` contains `primeng` or `@primeuix/*` dependencies. Pairs with `angular-developer` for Angular fundamentals.
How do I install this agent skill?
npx skills add https://github.com/mofirojean/angular-ui-skills --skill primeng-developerIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill provides guidelines and documentation for using PrimeNG v18+ in Angular projects. It covers installation, theming, component usage, and accessibility best practices without any detected malicious patterns or security risks.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
PrimeNG Developer Guidelines
Pairs with
angular-developer- that skill provides Angular fundamentals (signals, DI, routing, forms, SSR, accessibility). This skill focuses on PrimeNG specifics. Install both for the best experience.
Compatibility
- Tracks: PrimeNG
22.1.3(released 2026-10-20), with@primeuix/themesand@primeuix/stylesboth3.x(currently3.0.2). PrimeNG follows Angular's major, so v22 requires Angular v22 (peer@angular/core@^22.1.0from 22.1 on,^22.0.0on 22.0.x). - Works for: PrimeNG v18 → v22 projects. The skill references include
migration.mdcovering the v18 component renames (Calendar→DatePicker, Dropdown→Select, etc.) and the v21→v22 removals, so v18-v21 projects can use this skill but expect drift on theming and a few component APIs. v22 is the closest match. - v21 → v22: v22 is an Angular-22 alignment plus
@primeuix/themes/@primeuix/stylesv3, and it finalizes (removes) the APIs that were deprecated "for removal in v22" in earlier versions,@primeng/themesimport path,pTemplate,styleClass,showTransitionOptions/hideTransitionOptions, camelCase selectors, and thepButtonicon/label props among them. Treat those as gone, not merely deprecated. See migration.md. - v22.0 → v22.1: no breaking changes. 22.1 adds the experimental
withIsolation()feature (primeng/isolation) for micro frontends and embedded widgets,filterMessage/selectionMessage/emptySelectionMessageinputs onp-select, afilteredNodesmodel onp-tree, and raises the Angular peer to^22.1.0. Also remember v22 sizes components for a 16px root font; apps still on a 14px root should use the-compatpresets (see theming.md). See migration.md. - Docs domain: the official docs moved from
primeng.orgtoprimeng.dev(old links 301-redirect). - Angular: v18 or newer required (v22 for PrimeNG v22). PrimeNG components are standalone since v18. The skill assumes standalone components, control flow (
@if/@for), and signal-based APIs. - Tailwind: v3 or v4 with
tailwindcss-primeuiplugin (optional, for unstyled mode). - Not supported: PrimeNG v17 and below (different theming model based on
prime.css), Angular v17 or below (NgModule patterns).
If the project's PrimeNG version is below v18, point the user to PrimeNG's v17 docs and decline to generate v18+ patterns into a v17 project, they will not compile.
-
Always check the project's PrimeNG version before providing guidance. PrimeNG v18 introduced major component renames (Calendar→DatePicker, Dropdown→Select, InputSwitch→ToggleSwitch, OverlayPanel→Popover, Sidebar→Drawer) and a new design-token theming system.
package.jsonis the source of truth, when in doubt, look there before recommending an API. See migration.md. -
Detect which theming mode the project uses before adding components:
- If
@primeuix/themesis imported andprovidePrimeNG({ theme: ... })is configured → Styled mode (default). - If
unstyled: trueis set inprovidePrimeNG, or the project usestailwindcss-primeui→ Unstyled mode. - The two modes have fundamentally different customization paths. See styled-vs-unstyled.md.
- If
-
Components are standalone since v18. Always import the standalone class (e.g.
Buttonfrom'primeng/button'), not the legacy*Module. Legacy modules still export for backwards compatibility but should not be added to new code. -
After generating PrimeNG code, run
ng buildto catch compile errors. The most common AI mistakes are: (a) importing from@primeng/themesinstead of@primeuix/themes(deprecated path); (b) forgettingprovideAnimationsAsync()on v18 to v20 projects (PrimeNG v21+ uses native CSS animations and no longer requires it); (c) using v17 component names (Calendar,Dropdown,OverlayPanel,Sidebar,InputSwitch) after the v18 renames; (d) writingstyleClass="…"on components, deprecated since v20, use nativeclass="…"(or[class]/[ngClass]) instead; (e) writingpTemplate="item"inside a component imported standalone, thePrimeTemplatedirective is NOT in scope unless you importSharedModule(or a*ModulelikeTableModulethat re-exports it), so the template silently never registers and the component renders empty rows with no build error and no console error. Use a template reference instead (<ng-template #item>,#content,#header, …), every v21 component content-queries those refs directly. See setup.md and migration.md.
PrimeNG architecture: Styled, Unstyled, PassThrough
PrimeNG ships compiled in node_modules, there is no source-copy CLI. Customization happens through three escalating mechanisms:
- Design tokens (Styled mode), override theme variables at the preset level via
definePreset(Aura, {...}). Best for most theming needs. See theming.md. - PassThrough (
pt), per-component prop that injects classes/attributes into any internal DOM section. Works in both Styled and Unstyled modes. Use when tokens aren't enough. See passthrough.md. - Unstyled mode, strip PrimeNG's styles entirely and provide your own (typically Tailwind via
tailwindcss-primeui). Use for teams that already own a design system. See styled-vs-unstyled.md.
Default to Styled mode with Aura preset. Reach for PassThrough when you need to override specific internal sections. Reach for Unstyled only when the project is committed to a Tailwind-driven design system.
Installation and theming
- Setup: Install
primeng @primeuix/themes @primeuix/styles, wireprovidePrimeNG()(andprovideAnimationsAsync()on v18 to v20), common pitfalls. Read setup.md - Theming: Aura / Lara / Nora / Material presets, design tokens, dark mode,
definePresetoverrides, runtime preset switching, CSS layer ordering. Read theming.md - Styled vs Unstyled: When to use each mode, Tailwind v4 +
tailwindcss-primeuiintegration, Volt UI reference patterns. Read styled-vs-unstyled.md - PassThrough: The
ptAPI, globalptinprovidePrimeNG, nested-component prefix (pcBadge),ptOptions.mergeSectionsandmergeProps. Read passthrough.md
Components
PrimeNG provides 80+ components grouped here by category. Each category file covers component APIs, common patterns, and gotchas.
- Form controls: AutoComplete, CascadeSelect, Checkbox, ColorPicker, DatePicker, Editor, FloatLabel, IconField, IftaLabel, InputMask, InputNumber, InputOtp, InputText, Knob, Listbox, MultiSelect, Password, RadioButton, Rating, Select, SelectButton, Slider, Textarea, ToggleButton, ToggleSwitch, TreeSelect. Read form-controls.md
- Buttons: Button, SpeedDial, SplitButton. Read buttons.md
- Overlays: ConfirmDialog, ConfirmPopup, Dialog, Drawer, DynamicDialog, Popover, Toast, Tooltip. Read overlays.md
- Layout: Accordion, BlockUI, Card, Divider, Fieldset, Panel, Scroller (VirtualScroller), ScrollTop, Splitter, Stepper, Tabs, Toolbar. Read layout.md
- Data display: Carousel, DataView, Galleria, OrderList, Paginator, PickList, Table, Timeline, Tree, TreeTable. Read data-display.md
- Display: Avatar, Badge, Chip, Image, Inplace, Message, MeterGroup, OverlayBadge, ProgressBar, ProgressSpinner, Ripple, Skeleton, Tag, Terminal. Read display.md
- Menus: Breadcrumb, ContextMenu, Dock, MegaMenu, Menu, MenuBar, PanelMenu, TieredMenu. Read menus.md
Forms integration
- Forms: Wiring PrimeNG form components to ReactiveForms or Signal Forms, the
[invalid]prop (v20+) replacing.ng-invalid.ng-dirty,ControlValueAccessorpatterns, validation display. Read forms.md
Accessibility
- Accessibility: WCAG 2.1 AA compliance built in,
p-sr-onlyutility, ARIA conventions per component, keyboard navigation, focus management. Read accessibility.md
Migration
- Migration: v18 component renames (Calendar→DatePicker etc.), deprecated APIs, the
[invalid]prop replacing.ng-invalid.ng-dirty, design-token system replacing the legacy SCSS theme. Read migration.md
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/mofirojean/angular-ui-skills/primeng-developer">View primeng-developer on skillZs</a>