Polish a user story into a consistent design spec file through structured brainstorming dialogue BEFORE planning. Use when the user wants to refine, clarify, brainstorm, or "polish" a user story / work item / feature idea for this Angular 22 SimUI repository, or before running /create-implementation-plan on an ambiguous feature, bug, component category, UI variant, documentation, or migration task. Input is an issue/ticket key or URL, Figma/design link, or free-form feature description.
Generates Angular code and provides architectural guidance. Trigger when creating projects, components, or services, or for best practices on reactivity (signals, linkedSignal, resource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, or CLI tooling.
Automate browser interactions, test web pages and work with Playwright tests.
Scaffold a complete SimUI component category with numbered Angular examples, barrels, registry data, a showcase page, routing, a home thumbnail, and preview registration. Use when asked to add a new component category or component list to this repository.
Implement, review, and refactor SimUI styling with Tailwind CSS v4. Use for Angular template classes, responsive layouts, dark mode, semantic color tokens, state and data variants, transitions, class composition with hlm(), or changes to src/styles.css and Tailwind/PostCSS configuration.