Angular Best Practices Primeng

alfredoperez/angular-best-practices/skills/angular-best-practices-primeng

by alfredopereza499a4786182097a500dd2fb6ddc2489caee3854MIT37 starsListed Oct 9, 2026Updated Oct 9, 2026Repository updated 6 months ago

PrimeNG best practices for Angular. Covers tree-shaking imports, lazy-loaded tables, and the Aura/Lara theme system with design tokens. Activates when working with primeng components. Do not use for Angular Material, Spartan UI, or other component libraries. Install alongside angular-best-practices for full coverage.

ArchivedInstructions onlySoftware Development
AI-generated overview

PrimeNG best practices for Angular: tree-shakeable imports, lazy-loaded tables, and Aura/Lara theming with design tokens.

What it does
Provides guidance rules for using PrimeNG components in Angular projects. It covers standalone component imports for smaller bundles, table configuration with server-side pagination or virtual scrolling, and theme setup through providePrimeNG design tokens instead of CSS overrides. It is an instructions-only add-on meant to be installed alongside a core Angular best-practices skill.
When to use it
Use it when importing PrimeNG standalone components, configuring PrimeNG tables with server-side pagination or virtual scrolling, or setting up Aura/Lara themes with design tokens. It is not intended for Angular Material, Spartan UI, or other component libraries.
Requirements
No scripts or tooling are shipped; it is instructions only. It assumes an Angular project using PrimeNG and is designed to be installed alongside the core angular-best-practices skill.

Angular PrimeNG Best Practices

PrimeNG rules for component imports, table performance, and theming. Use with the core angular-best-practices skill for comprehensive Angular coverage.

Links

When to Apply

  • Importing PrimeNG standalone components
  • Configuring tables with server-side pagination or virtual scrolling
  • Setting up Aura/Lara themes with design tokens

Rules

RuleImpactDescription
Tree-Shake PrimeNG ImportsMEDIUMStandalone component imports for smaller bundles
Use PrimeNG Table with Lazy LoadingHIGHServer-side pagination for large datasets
Use PrimeNG Theme SystemMEDIUMDesign tokens via providePrimeNG instead of CSS overrides

Install

Install from skills.sh/alfredoperez/angular-best-practices:

Source and attribution

Source:alfredoperez/angular-best-practicesinskills/angular-best-practices-primengat commita499a47

License: MIT

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

More from alfredoperez/angular-best-practices

Angular Best Practices Signalstore

alfredoperez

NgRx SignalStore best practices for Angular. Covers shared state, computed state, entity management, and RxJS integration with rxMethod. Activates when working with @ngrx/signals and @ngrx/signals/entities. Do not use for NgRx Store or class-based state services. Install alongside angular-best-practices for full coverage.

Archived
Awaiting classification37updated 6 months ago

Angular Best Practices Ngrx

alfredoperez

NgRx state management best practices for Angular, covering reducers, effects, selectors and entity adapters.

Archived
Software Development37updated 6 months ago

Angular Best Practices Material

alfredoperez

Angular Material and CDK best-practice rules for imports, M3 theming, CDK utilities and component test harnesses.

Archived
Software Development37updated 6 months ago

Angular Best Practices

alfredoperez

Modern Angular best practices for building performant, maintainable Angular 17+ applications. Covers Signals, RxJS, components, templates, styles, performance, SSR, testing, forms, routing, accessibility, and architecture — with code examples and impact ratings for every rule. Use this skill whenever the user is working on Angular code of any kind: components, services, templates, stylesheets, routes, tests, or configuration. This applies to editing .component.ts, .service.ts, .html templates, .scss/.css styles, .spec.ts tests, .routes.ts files, store files, and any general .ts file in an Angular project. Look for angular.json, nx.json, or @angular/core imports as project indicators. Do not use for AngularJS (1.x), React, Vue, or non-Angular TypeScript projects.

Archived
Awaiting classification37updated 6 months ago