Skillshub angular-architecture
Standards for Angular project structure, feature modules, and lazy loading. Use when structuring Angular apps, defining feature modules, or configuring lazy loading. (triggers: angular.json, angular components, standalone, feature module, lazy loading, loadComponent, loadChildren)
install
source · Clone the upstream repo
git clone https://github.com/ComeOnOliver/skillshub
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/ComeOnOliver/skillshub "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/HoangNguyen0403/agent-skills-standard/angular-architecture" ~/.claude/skills/comeonoliver-skillshub-angular-architecture-1ca6c9 && rm -rf "$T"
manifest:
skills/HoangNguyen0403/agent-skills-standard/angular-architecture/SKILL.mdsource content
Angular Architecture
Priority: P0 (CRITICAL)
Principles
- Feature-Based: Organize by feature folder (e.g.,
) containing components, services, and models. Apply LIFT: Locate, Identify, Flat structure, Try DRY.features/dashboard/ - Standalone First: Use standalone components, Pipes, and Directives. Eliminate NgModule for new code; use standalone: true (or default in Angular 20+).
- Core vs Shared:
: Global singletons (AuthService, Interceptors). Never put singletons in shared/.core/
: Reusable UI components, pipes, utils (Buttons, Formatters).shared/
- Smart vs Dumb:
- Smart (Container): Talks to services, manages state.
- Dumb (Presentational): Inputs/Outputs only. No logic. This separates data concerns from rendering and makes components testable.
Guidelines
- Lazy Loading: All feature routes MUST be lazy loaded using loadComponent or loadChildren.
- Example:
{ path: 'dashboard', loadComponent: () => import('./features/dashboard/dashboard.component').then(m => m.DashboardComponent) }
- Example:
- Flat Modules: Avoid deep nesting of modules.
- Barrel Files: Use carefully. Prefer direct imports for better tree-shaking in some build tools (though modern bundlers handle barrels well).
Verification Checklist (Mandatory)
- Lazy Loading: Are all feature routes using
orloadComponent
?loadChildren - Standalone: Are components, pipes, and directives standalone?
- Core/Shared: Are global services in
and reusable UI incore/
?shared/ - Smart/Dumb: Are presentational components logic-free with only @Input/@Output?
- Signals: Are you using Signals for local state where applicable (Angular 16+)?
Anti-Patterns
- No NgModule: Eliminate NgModule for new code; use standalone components.
- No eager feature imports: Lazy load all features with
orloadComponent
.loadChildren - No type-based folders: Organize by feature, not by
,/components
top-level dirs./services