What problem does it solve?
This Skill solves the problem of implementing a consistent, branded Angular Material 3 (M3) theme across both client-side SCSS and legacy server-side/SSR theme configuration.
Core Features & Use Cases
- Define a new M3 theme in SCSS: Create a theme configuration in frontend/src/styles/theme.scss, then wire it into frontend/src/styles.scss so Material tokens and custom CSS variables are applied correctly.
- Update app configuration schema and defaults: Extend config.schema.yml and config/default.yml so the new theme can be selected via application.theme.
- Add a legacy SSR/older UI mapping: Register matching color tokens in views/themes/themes.ts for server-rendered pages and non-M3/legacy UI elements.
Use case: You want the OWASP Juice Shop UI to reflect a new brand identity (primary/surface/nav/text colors) while keeping component styling consistent and ensuring legacy pages use the same palette.
Quick Start
Add your theme name to the SCSS theme definitions in frontend/src/styles/theme.scss and frontend/src/styles.scss, then register the same theme colors in config.schema.yml, config/default.yml, and views/themes/themes.ts.