angular-tooling
Angular CLI usage, code generation, build configuration, and bundle optimization. Use when creating Angular projects, generating components/services/guards, configuring builds, running tests, or analyzing bundles. (triggers: angular.json, ng generate, ng build, ng serve, ng test, ng add, angular cli, bundle analysis)
Best use case
angular-tooling is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Angular CLI usage, code generation, build configuration, and bundle optimization. Use when creating Angular projects, generating components/services/guards, configuring builds, running tests, or analyzing bundles. (triggers: angular.json, ng generate, ng build, ng serve, ng test, ng add, angular cli, bundle analysis)
Teams using angular-tooling should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/angular-tooling/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How angular-tooling Compares
| Feature / Agent | angular-tooling | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Angular CLI usage, code generation, build configuration, and bundle optimization. Use when creating Angular projects, generating components/services/guards, configuring builds, running tests, or analyzing bundles. (triggers: angular.json, ng generate, ng build, ng serve, ng test, ng add, angular cli, bundle analysis)
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Angular Tooling ## **Priority: P2 (OPTIONAL)** ## CLI Essentials - **Command**: `ng generate component` (or `ng g c`) - **Flags**: Use `--dry-run` to preview output first. Add `--change-detection=OnPush` to set CD strategy at generation time. Use `--skip-tests` if spec is not needed. - **Workflow**: Always use `ng generate` — **never create files manually**. ```bash ng new my-app --style=scss --routing # Create project ng g c features/user-profile # Generate component ng g s services/auth # Generate service (providedIn: root) ng g guard guards/auth # Generate functional guard ng g interceptor interceptors/auth # Generate functional interceptor ng g pipe pipes/truncate # Generate standalone pipe ``` ## Code Generation Flags - `--dry-run` — Preview output without writing files. Always use `--dry-run` first for unfamiliar generators. - `--skip-tests` — Skips spec file generation. - `--flat` — Skips subfolder creation. - `--change-detection=OnPush` — Sets CD strategy on generation. - `--style=scss` — Sets stylesheet format. ## Build Configuration - **Dev**: `ng serve --open` - **Prod**: `ng build -c production`. Output goes to `dist/my-app/browser/`. - **SSR**: `ng add @angular/ssr` then `ng build` (adds `server/` output). - **Coverage**: `ng test --code-coverage --watch=false`. Coverage output goes to `coverage/` directory. ## Bundle Analysis ```bash ng build -c production --stats-json npx esbuild-visualizer --metadata dist/my-app/browser/stats.json --open ``` - **Note**: Check `angular.json` budgets — do not hand-edit `angular.json budgets` values; analyze the bundle first to understand what's large. ## Update Angular - **Command**: `ng update` to check available updates. - **Apply**: `ng update @angular/core @angular/cli` — this runs official **codemods** to migrate your code. - **Rule**: **Never use --force**; fix peer dependency conflicts properly instead. ## Anti-Patterns - **No manual file creation**: Always use `ng generate` for consistency and proper registration. - **No `ng update --force`**: Fix peer dependency conflicts instead of skipping checks. - **No hand-editing angular.json budgets**: Lower budgets cause CI failures; analyze bundles first. ## References - [Angular CLI Docs](https://angular.dev/tools/cli)
Related Skills
angular-signals
Implement signal-based reactive state management in Angular v20+. Use for creating reactive state with signal(), derived state with computed(), dependent state with linkedSignal(), and side effects with effect(). Triggers on state management questions, converting from BehaviorSubject/Observable patterns to signals, or implementing reactive data flows.
angular-http
Implement HTTP data fetching in Angular v20+ using resource(), httpResource(), and HttpClient. Use for API calls, data loading with signals, request/response handling, and interceptors. Triggers on data fetching, API integration, loading states, error handling, or converting Observable-based HTTP to signal-based patterns.
angular-directives
Create custom directives in Angular v20+ for DOM manipulation and behavior extension. Use for attribute directives that modify element behavior/appearance, structural directives for portals/overlays, and host directives for composition. Triggers on creating reusable DOM behaviors, extending element functionality, or composing behaviors across components. Note - use native @if/@for/@switch for control flow, not custom structural directives.
angular-di
Implement dependency injection in Angular v20+ using inject(), injection tokens, and provider configuration. Use for service architecture, providing dependencies at different levels, creating injectable tokens, and managing singleton vs scoped services. Triggers on service creation, configuring providers, using injection tokens, or understanding DI hierarchy.
angular
Modern Angular (v20+) expert with deep knowledge of Signals, Standalone Components, Zoneless applications, SSR/Hydration, and reactive patterns. Use PROACTIVELY for Angular development, component architecture, state management, performance optimization, and migration to modern patterns.
angular-ui-patterns
Modern Angular UI patterns for loading states, error handling, and data display. Use when building UI components, handling async data, or managing component states.
angular-migration
Migrate from AngularJS to Angular using hybrid mode, incremental component rewriting, and dependency injection updates. Use when upgrading AngularJS applications, planning framework migrations, or modernizing legacy Angular code.
angular-best-practices
Angular performance optimization and best practices guide. Use when writing, reviewing, or refactoring Angular code for optimal performance, bundle size, and rendering efficiency.
suggesting-tooling
Analyzes a codebase and suggests custom Claude Code skills and subagents to improve development workflow. Use when user wants tooling suggestions, automation ideas, or asks "what skills would help this project".
perigon-angular
Angular 21+ standalone/Material/signal conventions for Perigon WebApp
angular-component
Create modern Angular standalone components following v20+ best practices. Use for building UI components with signal-based inputs/outputs, OnPush change detection, host bindings, content projection, and lifecycle hooks. Triggers on component creation, refactoring class-based inputs to signals, adding host bindings, or implementing accessible interactive components.
rxjs-patterns-for-angular
Implement RxJS patterns for reactive programming in Angular. Use this skill when working with Observables, operators, subscriptions, async data flows, and error handling. Covers common patterns like combineLatest, switchMap, debounceTime, catchError, retry logic, and integration with Angular Signals using toSignal() and toObservable(). Ensures proper subscription cleanup with takeUntilDestroyed().