What problem does it solve? When writing or extending code in the angular-webapp-template project, generic Angular best practices often conflict with what the codebase actually does — leading to inconsistent components, wrong DI patterns, and mismatched styling. This Skill captures the repo's real conventions (including its known inconsistencies) so generated code matches sibling files instead of textbook Angular. ## Core Features & Use Cases - Architecture guidance: Vertical Slice project structure, standalone components, inject()-only DI, signal-based stores, and the three-piece data-access token pattern for Supabase-backed features. - Cross-cutting rules: Reactive Forms without FormBuilder, Transloco i18n usage, RxJS conventions with takeUntilDestroyed and toSignal, and @if/@for template control flow. - Styling conventions: BEM-via-Sass naming, is-* state classes, --mat-sys-* design tokens, and the global styles.scss duplication pattern for Material overlay content. - Use Case: When asked to add a new CRUD feature to the project, follow the documented token pattern (InjectionToken + interface, Supabase implementation, binding in app.config.ts) plus a signal-based store service, matching how existing features like sights are built. ## Quick Start Use the angular-webapp-conventions skill to create a new feature page with a signal-based store and Supabase data-access layer in this project.