Guide Angular NgModule patterns for non-standalone components and lazy-loaded routes.
npx skills add https://github.com/sebasmzg/sebas.dot --skill angular-sebasmzg
Please help me install this Agent Skill. Skill: angular Source: https://github.com/sebasmzg/sebas.dot/tree/main/.config/opencode/skill/angular Command: npx skills add https://github.com/sebasmzg/sebas.dot --skill angular-sebasmzg
Provides clear patterns and templates to avoid common architectural mistakes when building Angular applications with non-standalone components and NgModule-based organization, reducing runtime errors and module misuse.
Use the angular skill to get NgModule patterns, templates, and a short checklist for converting components and services into a feature module.
High-intent search queries and answers about installing and using this skill.
Organize Angular NgModules by declaring components in feature modules, placing shared components in a SharedModule, and providing singletons in a CoreModule. This separation prevents duplicate declarations and ensures proper module-level provider scoping for non-standalone components.
Use BrowserModule only in the root AppModule to enable critical application providers, and use CommonModule in feature modules to access common directives like ngIf and ngFor. This distinction prevents runtime errors and ensures correct module initialization.
Implement lazy-loaded routes by using the loadChildren property in your routing configuration to dynamically import the feature module. This pattern defers module initialization until navigation, improving application performance.
Configure service providers using the providedIn property within the @Injectable decorator to define scoping. Choosing providedIn: 'root' creates a singleton service, while module-level providers restrict availability to that specific NgModule.
Duplicate declaration errors occur when an Angular component, directive, or pipe is declared in multiple NgModules. Resolve this by declaring each component in a single feature or shared module and importing that module where needed.
Yes, NgModule patterns are specifically designed for non-standalone Angular components. This approach provides structured templates for component declarations, service provisioning, and routing within a modular architecture.
cdrguruInitialize Gemini CLI configuration and auditor persona for the PACK workflow.
oguzhan18Guide writing, running, and maintaining Angular tests across Jasmine, Karma, Vitest, Jest, and Cypress.
oguzhan18Manage reactive state and side effects using Angular Signals.
arbazkhan971Architect Angular applications for maintainability, performance, and scalable state management.
