Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From primeng
Migrate PrimeNG code using only current routed PrimeNG migration guidance and current component/setup metadata. Use for supported version boundaries and source-backed deprecated-API cleanup.
How this skill is triggered — by the user, by Claude, or both
Slash command
/primeng:primeng-migrationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Read installed PrimeNG and Angular versions and the target from package metadata and the lockfile. Record the standalone application configuration, `providePrimeNG`, theme configuration, forms approach, and affected components. Do not call `version` merely to replace this project evidence.
Read installed PrimeNG and Angular versions and the target from package metadata and the lockfile. Record the standalone application configuration, providePrimeNG, theme configuration, forms approach, and affected components. Do not call version merely to replace this project evidence.
Call get_guide only for a current routed PrimeNG migration guide that covers the requested boundary. If no such guide is returned, state that the migration path is unsupported and do not synthesize renames or replacements. Call get_component for each materially affected component's current selector, import, inputs, outputs, templates, directives, forms, and API contract; use get_setup only when returned migration guidance requires a supported standalone setup change.
Separate confirmed required changes from optional cleanup. Preserve unrelated code and local conventions. Never infer deprecations, removals, imports, theme tokens, pass-through keys, Angular compatibility, NgModule setup, or another PrimeUI library's behavior. Call validate_usage once on final migrated component code, repeating only after a reported issue, then run focused Angular checks.
migration: get_guide -> get_component -> validate_usage; maximum 3.Report source and target evidence, migration/component resource and public citations, validation results, and unsupported gaps.
npx claudepluginhub primefaces/primeui-plugins --plugin primengCreates, edits, and verifies skills using a test-driven development approach with pressure scenarios and subagents.