> 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)
curl "https://skillshub.wtf/HoangNguyen0403/agent-skills-standard/angular-tooling?format=md"Angular Tooling
Priority: P2 (OPTIONAL)
CLI Essentials
- Command:
ng generate component(orng g c) - Flags: Use
--dry-runto preview output first. Add--change-detection=OnPushto set CD strategy at generation time. Use--skip-testsif spec is not needed. - Workflow: Always use
ng generate— never create files manually.
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-runfirst 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 todist/my-app/browser/. - SSR:
ng add @angular/ssrthenng build(addsserver/output). - Coverage:
ng test --code-coverage --watch=false. Coverage output goes tocoverage/directory.
Bundle Analysis
ng build -c production --stats-json
npx esbuild-visualizer --metadata dist/my-app/browser/stats.json --open
- Note: Check
angular.jsonbudgets — do not hand-editangular.json budgetsvalues; analyze the bundle first to understand what's large.
Update Angular
- Command:
ng updateto 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 generatefor 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
> related_skills --same-repo
> golang-tooling
Go developer toolchain — gopls LSP diagnostics, linting, formatting, and vet. Use when setting up Go tooling, running linters, or integrating gopls with Claude Code. (triggers: gopls, golangci-lint, golangci.yml, go vet, goimports, staticcheck, go tooling, go lint)
> common-ui-design
Create distinctive, production-grade frontend UI with bold aesthetic choices. Use when building web components, pages, interfaces, dashboards, or applications in any framework (React, Next.js, Angular, Vue, HTML/CSS). Triggers: 'build a page', 'create a component', 'design a dashboard', 'landing page', 'UI for', 'build a layout', 'make it look good', 'improve the design', build UI, create interface, design screen
> common-owasp
OWASP Top 10 audit checklist for Web Applications (2021) and APIs (2023). Load during any security review, PR review, or codebase audit touching web, mobile backend, or API code. (triggers: security review, OWASP, broken access control, IDOR, BOLA, injection, broken auth, API review, authorization, access control)
> common-llm-security
OWASP LLM Top 10 (2025) audit checklist for AI applications, agent tools, RAG pipelines, and prompt construction. Load during any security review touching LLM client code, prompt templates, agent tools, or vector stores. (triggers: LLM security, prompt injection, agent security, RAG security, AI security, openai, anthropic, langchain, LLM review)