angular-conventions

Detect Angular project conventions and apply matching bootstrap and pattern guidelines.

9|1|Updated Jun 16, 2026
One-click install
npx skills add https://github.com/AratKruglik/antigravity-sdlc --skill angular-conventions-aratkruglik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: angular-conventions
Source: https://github.com/AratKruglik/antigravity-sdlc/tree/main/plugins/angular-plugin/skills/angular-conventions
Command: npx skills add https://github.com/AratKruglik/antigravity-sdlc --skill angular-conventions-aratkruglik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Angular projects often struggle with choosing between standalone components and NgModule-based architectures, leading to inconsistent patterns and maintenance challenges. This skill provides clear conventions to detect project style, decide on bootstrap strategy, and apply modern decorators, DI patterns, and template syntax consistently across codebases.

Core Features & Use Cases

  • Detect project style (standalone-first vs NgModule legacy) and recommend the appropriate bootstrap and module strategy.
  • Standardize dependency injection patterns (inject() vs constructor) and modern template syntax (@if/@for/@switch vs *ngIf/*ngFor) across codebases.
  • Provide migration guidance and examples for Angular 17+ standalone components and NgModule legacy projects.

Quick Start

Audit your Angular project and align bootstrap, decorators, and template syntax to the standalone-first conventions.

Frequently Asked Questions about angular-conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize Angular standalone components versus NgModule architecture across my project?

This convention detects whether your Angular project uses standalone components or NgModule legacy setups, then applies the appropriate bootstrap strategy, decorators, and template syntax guidelines to keep patterns consistent.

What is the best way to migrate an Angular legacy NgModule project to standalone components?

The best way to migrate legacy NgModule projects to standalone components is to audit the current bootstrap setup and apply progressive migration guidance for standalone decorators, inject() patterns, and modern template syntax.

Should I use inject() or constructor injection for dependency injection in Angular 17+?

For Angular 17+ standalone projects, using inject() instead of constructor injection standardizes dependency injection patterns and aligns with modern standalone-first conventions across the codebase.

Does this Angular convention guidance work with both modern template syntax and legacy structural directives?

Yes, this convention guidance supports both modern template syntax (@if/@for/@switch) and legacy structural directives (*ngIf/*ngFor), applying the appropriate template patterns based on your detected project style.

Can I apply these Angular conventions to a mixed codebase with both standalone and NgModule components?

Yes, these conventions apply to mixed codebases by detecting standalone-first versus NgModule legacy styles and providing practical operational guidance for consistent implementation and migration across both architecture types.

When should I avoid migrating NgModule legacy code to standalone components in Angular?

You should avoid migrating NgModule legacy code to standalone components when existing module boundaries are stable and heavily interdependent, as forced migration can introduce inconsistency without delivering immediate architectural benefits.