angular-coding-practiceslisted

Use when authoring or reviewing Angular apps, kebab-case files, feature folders, inject(), readonly inputs, protected template members, class/style bindings, selector prefixes, and angular-eslint verification.
ryan-brosas/universal-template · ★ 1 · Code & Development · score 60

Install: claude install-skill ryan-brosas/universal-template

# Angular Coding Practices Application skill for angular.dev Style Guide (2025) ingest (`awesome-guidelines`). TypeScript style: `typescript-coding-practices`; domain modeling: `typescript-coding-standards`. SPA compare: `vue-coding-practices`. ## Core Principle Use the installed Angular version and project conventions. The 2025 guide offers feature-first layout, colocated files, injection, and signal patterns; it does not require an unrelated app to migrate its layout or working constructor injection. Treat the review prompts below as contextual checks, not automatic defects. ## When to Use / NOT - Angular 17+ application components, directives, project layout. - Migrating from legacy suffix-heavy style guide to 2025 conventions. - PR review on `.ts`/`.html` in `src/`. **NOT when:** - Generic TypeScript style only, `typescript-coding-practices`. - AngularJS 1.x, archived style guide. - Framework package contributions, Angular repo CONTRIBUTING. ## Workflow 1. **Naming/files**, kebab-case, specs, triplets (`angular-style-naming-files.md`). 2. **Structure**, src, features, one concept (`angular-style-project-structure.md`). 3. **Components**, inject, templates, lifecycle (`angular-style-components-templates.md`). 4. **Selectors/verify**, selectors, I/O, lint (`angular-style-selectors-verify.md`). ## Red Flags - PascalCase or camelCase source filenames - Tests isolated in global `tests/` away from feature - Type-based folders (`components/`, `services/`) - Bootstrap