skills/angular-awesome-migration/SKILL.md
Migrate Angular Awesome component wrappers when the upstream Web Awesome API changes. Use when replacing custom implementations with official web components, updating property names or types, removing deprecated fields, aligning placement/position values, updating tests for new APIs, and updating docs/changelog for breaking changes.
npx skillsauth add gedmarc/angular-awesome angular-awesome-migrationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Workflow for migrating wrapper implementations when the upstream Web Awesome component API changes.
position → placement)llms.txt API with current directive implementation.src/types/tokens.ts or component-local types.$angular-awesome-new-component.applyInputs().npx ng build && scoped test run.node docs/generate-docs.js.Before: Custom wa-toast-container rendering <wa-callout> elements with manual CSS positioning.
After: Official <wa-toast> + <wa-toast-item> web components.
Changes made:
WaToastDirective (new, wraps <wa-toast>)WaToastItemDirective (new, wraps <wa-toast-item>)WaToastContainerComponent template from <wa-callout> to <wa-toast> + <wa-toast-item>ToastConfig.position → ToastConfig.placement with new values (top-start/top-end instead of top-left/top-right)appearance, closable, gap, zIndex from types (handled natively)ToastPosition type — use ToastPlacement instead| Old Property | New Property | Notes |
|-------------|-------------|-------|
| position | placement | Values also changed: top-right → top-end |
| closable | (removed) | Handled by native <wa-toast-item> close button |
| appearance | (removed) | Not supported by official <wa-toast-item> |
| gap | --gap CSS var | Set via CSS custom property on <wa-toast> |
| zIndex | (removed) | Managed by native component stacking |
development
Use Angular Awesome wrapper directives for Web Awesome web components in Angular 20+ projects. Trigger when tasks mention wa-* components (wa-button, wa-input, wa-dialog, wa-toast, wa-select, wa-checkbox, etc.), Angular Awesome directives, Web Awesome Angular integration, component variants/appearance/size tokens, slot projection, form control binding, or angular-awesome imports. Covers component usage, layout utilities, services (toast), theming, and accessibility.
development
Theme and style Angular Awesome components using Web Awesome design tokens, CSS custom properties, CSS parts, variant/appearance/size tokens, and layout utilities. Use when customizing component appearance, applying brand colors, overriding default styles, using CSS shadow parts, or configuring layout directives (cluster, stack, grid, gap, align, flank, frame, split).
development
Write and maintain tests for Angular Awesome wrapper directives, components, and services. Use when creating spec files for wa-* components, testing form control integration, testing event emission, testing toast/service behavior, running headless or BrowserStack tests, or debugging test failures in Angular Awesome.
development
Create a new Angular Awesome wrapper directive or component for a Web Awesome web component. Use when adding a new wa-* component wrapper, scaffolding a directive with its spec/rules/example files, wiring it into public-api.ts, updating the changelog, and regenerating docs. Covers the full end-to-end flow from llms.txt API extraction through to build verification.