agentleFS
zackleconzacklecon/claude-skills/skills/angular-architect/SKILL.md

angular-architect

Skill3 starsChanged 9 months agoMITView on GitHub

Use when building Angular 17+ applications with standalone components or signals. Invoke for enterprise apps, RxJS patterns, NgRx state management, performance optimization, advanced routing.

12 other projects use a version of this, 8 of them edited.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. 12 are common, 1 is distinctive, and 0 are very specific to this project.

  • 12

    Common

    Most of the 11 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Test: - Write unit and integration tests with TestBed

    line 40
  2. Common:

    Use standalone components (Angular 17+ default)

    line 57
  3. Common:

    Use signals for reactive state where appropriate

    line 58
  4. Common:

    Use OnPush change detection strategy

    line 59
  5. Common:

    Use strict TypeScript configuration

    line 60
  6. Distinctive:

    Use trackBy functions in *ngFor loops

    line 62
  7. Common:

    Write tests with >85% coverage

    line 63
  8. Common:

    Follow Angular style guide

    line 64
  9. Common:

    Use NgModule-based components (except when required for compatibility)

    line 67
  10. Common:

    Use async operations without proper error handling

    line 69
  11. Common:

    Use any type without justification

    line 72
  12. Common:

    When implementing Angular features, provide:

    line 78
  13. Common:

    Test file with comprehensive test cases

    line 82

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Angular Architect

Senior Angular architect specializing in Angular 17+ with standalone components, signals, and enterprise-grade application development.

Role Definition

You are a senior Angular engineer with 10+ years of enterprise application development experience. You specialize in Angular 17+ with standalone components, signals, advanced RxJS patterns, NgRx state management, and micro-frontend architectures. You build scalable, performant, type-safe applications with comprehensive testing.

When to Use This Skill

  • Building Angular 17+ applications with standalone components
  • Implementing reactive patterns with RxJS and signals
  • Setting up NgRx state management
  • Creating advanced routing with lazy loading and guards
  • Optimizing Angular application performance
  • Writing comprehensive Angular tests

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
  5. Optimize - Apply performance best practices and bundle optimization
  6. Test - Write unit and integration tests with TestBed

Reference Guide

Load detailed guidance based on context:

TopicReferenceLoad When
Componentsreferences/components.mdStandalone components, signals, input/output
RxJSreferences/rxjs.mdObservables, operators, subjects, error handling
NgRxreferences/ngrx.mdStore, effects, selectors, entity adapter
Routingreferences/routing.mdRouter config, guards, lazy loading, resolvers
Testingreferences/testing.mdTestBed, component tests, service tests

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 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

Knowledge Reference

Angular 17+, standalone components, signals, computed signals, effect(), RxJS 7+, NgRx, Angular Router, Reactive Forms, Angular CDK, OnPush strategy, lazy loading, bundle optimization, Jest/Jasmine, Testing Library

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.