angular-architect — Claude Code skill: what it does, how to install
An Angular 17+ specialist skill for Claude Code and other AI editors: standalone components with signals, NgRx stores, lazy routing and bundle checks.
npx skills add Jeffallan/claude-skills --skill angular-architect -a claude-codeWhat angular-architect does
Point the agent at this skill and it takes the role of a senior Angular architect. It writes standalone components with OnPush and signal inputs, wires NgRx actions, reducers and selectors, puts routes behind guards with lazy loading, and closes subscriptions with takeUntilDestroyed. Handy once the codebase is on Angular 17+ and new features should match one style.
The workflow runs in six steps: requirements, architecture, implementation, state, optimisation, tests. Five reference files load on demand: references/components.md, references/rxjs.md, references/ngrx.md, references/routing.md, references/testing.md. Before moving on it checks the action flow in Redux DevTools, then runs ng build --configuration production to catch bundle regressions.
Testing is part of the deal — the skill wants TestBed specs and a coverage threshold of 85%. On a repo with no tests the agent starts writing them, so expect a wider diff than the feature alone. NgModule components sit in the do-not list with a compatibility caveat, which means legacy modules get nudged toward standalone.
What it helps with
- Generate a standalone component with signal inputs and
OnPush - Move list loading into NgRx with actions, a reducer and selectors
- Put a lazy route behind an auth guard
- Fix subscription leaks with
takeUntilDestroyed - Check bundle size after a refactor
Example prompts for the agent
- Generate a standalone user card component with signals and `OnPush`, expose the selection through `output`.
- Move the users list to NgRx: actions, reducer, selectors and an effect that loads the data.
- Make the `/admin` route load lazily behind a guard and cover it with a `TestBed` test.
How to install angular-architect
1Skills CLI (Vercel)
npx skills add Jeffallan/claude-skills --skill angular-architect -a claude-code2Manually: put the files in place
~/.claude/skills/angular-architect/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/angular-architect/
1Skills CLI (Vercel)
npx skills add Jeffallan/claude-skills --skill angular-architect -a codex2Manually: put the files in place
.agents/skills/angular-architect/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Jeffallan/claude-skills --skill angular-architect -a cursor2Manually: put the files in place
.cursor/skills/angular-architect/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Jeffallan/claude-skills angular-architect2Manually: put the files in place
.github/skills/angular-architect/SKILL.md1Skills CLI (Vercel)
npx skills add Jeffallan/claude-skills --skill angular-architect -a gemini-cli2Platform CLI
gemini skills install https://github.com/Jeffallan/claude-skills --path skills/angular-architectManually: put the files in place
.devin/skills/angular-architect/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Jeffallan/claude-skills --skill angular-architect -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set61
The whole set →Similar
Questions about angular-architect
How do I install angular-architect in Claude Code?
Run npx skills add Jeffallan/claude-skills --skill angular-architect -a claude-code. The skill file lands in ~/.claude/skills/angular-architect/SKILL.md.
What does angular-architect do?
It steers the agent toward Angular 17+ conventions: standalone components with signals, NgRx for state, lazy routes with guards, and tests on TestBed.
Does it work with an older NgModule codebase?
Standalone is the default and NgModule components are on the do-not list. A compatibility caveat leaves room for modules, but the agent keeps pulling legacy code toward standalone.
Source text
SKILL.md · MIT
---
name: angular-architect
description: Generates Angular 17+ standalone components, configures advanced routing with lazy loading and guards, implements NgRx state management, applies RxJS patterns, and optimizes bundle performance. Use when building Angular 17+ applications with standalone components or signals, setting up NgRx stores, establishing RxJS reactive patterns, performance tuning, or writing Angular tests for enterprise apps.
license: MIT
metadata:
author: https://github.com/Jeffallan
company: https://synergetic.solutions
version: "1.1.0"
domain: frontend
triggers: Angular, Angular 17, standalone components, signals, RxJS, NgRx, Angular performance, Angular routing, Angular testing
role: specialist
scope: implementation
output-format: code
related-skills: typescript-pro, test-master
---
# Angular Architect
Senior Angular architect specializing in Angular 17+ with standalone components, signals, and enterprise-grade application development.
## Core Workflow
1. **Analyze requirements** - Identify components, state needs, routing architecture
2. **Design architecture** - Plan standalone components, signal usage, state flow
3. **Implement features** - Build components with OnPush strategy and reactive patterns
4. **Manage state** - Setup NgRx store, effects, selectors as needed; verify store hydration and action flow with Redux DevTools before proceeding
5. **Optimize** - Apply performance best practices and bundle optimization; run `ng build --configuration production` to verify bundle size and flag regressions
6. **Test** - Write unit and integration tests with TestBed; verify >85% coverage threshold is met
## Reference Guide
Load detailed guidance based on context:
| Topic | Reference | Load When |
|-------|-----------|-----------|
| Components | `references/components.md` | Standalone components, signals, input/output |
| RxJS | `references/rxjs.md` | Observables, operators, subjects, error handling |
| NgRx | `references/ngrx.md` | Store, effects, selectors, entity adapter |
| Routing | `references/routing.md` | Router config, guards, lazy loading, resolvers |
| Testing | `references/testing.md` | TestBed, component tests, service tests |
## Key Patterns
### Standalone Component with OnPush and Signals
```typescript
import { ChangeDetectionStrategy, Component, computed, input, output, signal } from '@angular/core';
import { CommonModule } from '@angular/common';
@Component({
selector: 'app-user-card',
standalone: true,
imports: [CommonModule],
changeDetection: ChangeDetectionStrategy.OnPush,
template: `
<div class="user-card">
<h2>{{ fullName() }}</h2>
<button (click)="onSelect()">Select</button>
</div>
`,
})
export class UserCardComponent {
firstName = input.required<string>();
lastName = input.required<string>();
selected = output<string>();
fullName = computed(() => `${this.firstName()} ${this.lastName()}`);
onSelect(): void {
this.selected.emit(this.fullName());
}
}
```
### RxJS Subscription Management with `takeUntilDestroyed`
```typescript
import { Component, OnInit, inject } from '@angular/core';
import { takeUntilDestroyed } from '@angular/core/rxjs-interop';
import { UserService } from './user.service';
@Component({ selector: 'app-users', standalone: true, template: `...` })
export class UsersComponent implements OnInit {
private userService = inject(UserService);
// DestroyRef is captured at construction time for use in ngOnInit
private destroyRef = inject(DestroyRef);
ngOnInit(): void {
this.userService.getUsers()
.pipe(takeUntilDestroyed(this.destroyRef))
.subscribe({
next: (users) => { /* handle */ },
error: (err) => console.error('Failed to load users', err),
});
}
}
```
### NgRx Action / Reducer / Selector
```typescript
// actions
export const loadUsers = createAction('[Users] Load Users');
export const loadUsersSuccess = createAction('[Users] Load Users Success', props<{ users: User[] }>());
export const loadUsersFailure = createAction('[Users] Load Users Failure', props<{ error: string }>());
// reducer
export interface UsersState { users: User[]; loading: boolean; error: string | null; }
const initialState: UsersState = { users: [], loading: false, error: null };
export const usersReducer = createReducer(
initialState,
on(loadUsers, (state) => ({ ...state, loading: true, error: null })),
on(loadUsersSuccess, (state, { users }) => ({ ...state, users, loading: false })),
on(loadUsersFailure, (state, { error }) => ({ ...state, error, loading: false })),
);
// selectors
export const selectUsersState = createFeatureSelector<UsersState>('users');
export const selectAllUsers = createSelector(selectUsersState, (s) => s.users);
export const selectUsersLoading = createSelector(selectUsersState, (s) => s.loading);
```
## Constraints
### MUST DO
- Use standalone components (Angular 17+ default)
- Use signals for reactive state where appropriate
- Use OnPush change detection strategy
- Use strict TypeScript configuration
- Implement proper error handling in RxJS streams
- Use `trackBy` functions in `*ngFor` loops
- Write tests with >85% coverage
- Follow Angular style guide
### MUST NOT DO
- Use NgModule-based components (except when required for compatibility)
- Forget to unsubscribe from observables (use `takeUntilDestroyed` or `async` pipe)
- Use async operations without proper error handling
- Skip accessibility attributes
- Expose sensitive data in client-side code
- Use `any` type without justification
- Mutate state directly in NgRx
- Skip unit tests for critical logic
## Output Templates
When implementing Angular features, provide:
1. Component file with standalone configuration
2. Service file if business logic is involved
3. State management files if using NgRx
4. Test file with comprehensive test cases
5. Brief explanation of architectural decisions
Maintained by [@jeffallan](https://github.com/jeffallan), Principal Consultant at [Synergetic Solutions](https://synergetic.solutions)
[Documentation](https://jeffallan.github.io/claude-skills/skills/frontend/angular-architect/)
© https://github.com/Jeffallan · MIT · Jeffallan/claude-skills