angular-developer
Skill1 starsChanged 6 days agoMITView on GitHub
Generates Angular code and provides architectural guidance. Trigger when creating projects, components, services, or HTTP communication, or for best practices on reactivity (signals, linkedSignal, resource, httpResource), queries and content projection, forms, dependency injection, routing, server and hybrid rendering (SSR, prerendering, hydration), accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, naming conventions, or CLI tooling.
27 other projects use a version of this, 26 of them edited.
Adopted by
Most recently taken up by
- AndresArreguy/ecc-pi-portedited, first seen Nov 16, 2026
- Hive-Academy/ptah-extensionedited, first seen Nov 15, 2026
- Hive-Academy/PtahCodeedited, first seen Nov 15, 2026
- swap-cameroon/kuro-antigravity-configedited, first seen Nov 15, 2026
- angular/skillsedited, first seen Nov 11, 2026
- JuankCadavid/akili-specsedited, first seen Nov 2, 2026
Used with
Projects with it also use brainstorming.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
OpenAISkillbrainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Also in 3 projects that use this
Other versions27 projects use a version of this.
Word for word · 0
None found.
Edited · 26
- angular/angular★ 101k98% same
- ghostfolio/ghostfolio★ 9.7k98% same
- jsverse/transloco★ 2.3k93% same
- dotCMS/core★ 97196% same
- angular/skills★ 72698% same
- biaogebusy/web-builder★ 58393% same
- azerothcore/Keira3★ 46393% same
- Fmarzochi/EGC★ 6177% same
- Hive-Academy/ptah-extension★ 3498% same
- Hive-Academy/PtahCode★ 3498% same
16 more not listed
Wrote their own version · 1
- Sleestk/Skills-Pipeline★ 86same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- cavemanSkill
- find-animation-opportunitiesSkill
- frontend-designSkill
- grillingSkill
- grill-meSkill
- impeccableSkill
- improve-animationsSkill
- ui-tasteSkill
- web-design-guidelinesSkill
- angular-doctorSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
24 rules. 19 are common, 1 is distinctive, and 4 are very specific to this project.
19
Common
Most of the 27 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 12
Always analyze the project's Angular version before providing guidance, as best practices and available features can vary significantly …
- Common: line 14
When generating code, follow Angular's style guide and best practices for maintainability and performance.
- Common: line 20
If no guidelines are provided by the user, here are some default rules to follow when creating a new Angular project:
- Common: line 22
Use the latest stable version of Angular unless the user specifies otherwise.
- Common: line 23
Use Signal Forms for form management in new projects (stable in Angular v22 and newer) Find out more.
- Common: line 26
When asked to create a new Angular project, you must determine the correct execution command by following these strict steps:
- Very specific: line 35
IF no specific version is requested, run ng version in the terminal to check if the Angular CLI is already installed on the system.
- Very specific: line 41
IF no specific version is requested AND the ng version command fails (indicating no Angular installation exists), you must use npx to fetch …
- Common: line 46
When working with Angular components, consult the following references based on the task:
- Very specific: line 56
If you require deeper documentation not found in the references above, read the documentation at https://angular.dev/guide/components.
- Common: line 60
When managing state and data reactivity, use Angular Signals and consult the following references:
- Distinctive: line 69
When communicating with backend services, use Angular HTTP APIs and consult the following reference:
- Common: line 77
If the application is using v22 or newer and this is a new form, prefer Signal Forms.
- Common: line 80
Signal Forms: Use signals for form state management.
- Common: line 81
Template-driven forms: Use for simple forms. Read template-driven-forms.md
- Common: line 82
Reactive forms: Use for complex forms. Read reactive-forms.md
- Common: line 86
When implementing dependency injection in Angular, follow these guidelines:
- Very specific: line 96
When formatting values in templates, creating custom pipes, or reusing pipe-like logic in TypeScript, consult the following reference.
- Common: line 102
When building accessible custom components for any of the following patterns: Accordion, Listbox, Combobox, Menu, Tabs, Toolbar, Tree, …
- Common: line 108
When implementing navigation in Angular, consult the following references:
- Common: line 121
If you require deeper documentation or more context, visit the official Angular Routing guide.
- Common: line 125
When implementing styling and animations in Angular, consult the following references:
- Common: line 133
When writing or updating tests, consult the following references based on the task:
- Common: line 142
When working with Angular tooling, consult the following references:
“Common” is measured: kept by at least 6 in 10 of the 27 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.
Files
Angular Developer Guidelines
- Always analyze the project's Angular version before providing guidance, as best practices and available features can vary significantly between versions. If creating a new project with Angular CLI, do not specify a version unless prompted by the user.
- When generating code, follow Angular's style guide and best practices for maintainability and performance. Use the Angular CLI for scaffolding components, services, directives, pipes, and routes to ensure consistency.
- Once you finish generating code, run
ng buildto ensure there are no build errors. If there are errors, analyze the error messages and fix them before proceeding. Do not skip this step, as it is critical for ensuring the generated code is correct and functional.
Creating New Projects
If no guidelines are provided by the user, here are some default rules to follow when creating a new Angular project:
- Use the latest stable version of Angular unless the user specifies otherwise.
- Use Signal Forms for form management in new projects (stable in Angular v22 and newer) Find out more.
Execution Rules for ng new:
When asked to create a new Angular project, you must determine the correct execution command by following these strict steps:
Step 1: Check for an explicit user version.
- IF the user requests a specific version (e.g., Angular 15), bypass local installations and strictly use
npx. - Command:
npx @angular/cli@<requested_version> new <project-name>
Step 2: Check for an existing Angular installation.
- IF no specific version is requested, run
ng versionin the terminal to check if the Angular CLI is already installed on the system. - IF the command succeeds and returns an installed version, use the local/global installation directly.
- Command:
ng new <project-name>
Step 3: Fallback to Latest.
- IF no specific version is requested AND the
ng versioncommand fails (indicating no Angular installation exists), you must usenpxto fetch the latest version. - Command:
npx @angular/cli@latest new <project-name>
Components
When working with Angular components, consult the following references based on the task:
- Fundamentals: Anatomy, metadata, core concepts, self-closing tags, and template control flow (@if, @for, @switch). Read components.md
- Inputs: Signal-based inputs, transforms, and model inputs. Read inputs.md
- Outputs: Signal-based outputs and custom event best practices. Read outputs.md
- Host Elements: Host bindings and attribute injection. Read host-elements.md
- Naming Conventions: Modern Angular v20+ naming style ("Intent over Role") for files, components, services, directives, pipes, and models. Read naming-conventions.md
- Queries and Content Projection: Signal-based view and content queries (viewChild, viewChildren, contentChild, contentChildren) and content projection with
<ng-content>slots and fallback content. Read queries-and-projection.md - Deferrable Views: Lazy loading, code splitting, triggers, prefetching, loading states, SSR, and layout stability with
@defer. Read deferrable-views.md
If you require deeper documentation not found in the references above, read the documentation at https://angular.dev/guide/components.
Reactivity and Data Management
When managing state and data reactivity, use Angular Signals and consult the following references:
- Signals Overview: Core signal concepts (
signal,computed), reactive contexts, anduntracked. Read signals-overview.md - Dependent State (
linkedSignal): Creating writable state linked to source signals. Read linked-signal.md - Async Reactivity (
resource): Fetching asynchronous data directly into signal state. Read resource.md - Side Effects (
effect): Logging, third-party DOM manipulation (afterRenderEffect), and when NOT to use effects. Read effects.md
HTTP Communication
When communicating with backend services, use Angular HTTP APIs and consult the following reference:
- HTTP Client and Resources:
provideHttpClient,HttpClient, interceptors, andhttpResource. Read http-client.md
Forms
In most cases for new apps, prefer signal forms. When making a forms decision, analyze the project and consider the following guidelines:
- If the application is using v22 or newer and this is a new form, prefer Signal Forms.
- For older applications or when working with existing forms, use the appropriate form type that matches the applications current form strategy.
- Signal Forms: Use signals for form state management. Read signal-forms.md
- Template-driven forms: Use for simple forms. Read template-driven-forms.md
- Reactive forms: Use for complex forms. Read reactive-forms.md
Dependency Injection
When implementing dependency injection in Angular, follow these guidelines:
- Fundamentals: Overview of Dependency Injection, services, and the
inject()function. Read di-fundamentals.md - Creating and Using Services: Creating services, the
providedIn: 'root'option, and injecting into components or other services. Read creating-services.md - Defining Dependency Providers: Automatic vs manual provision,
InjectionToken,useClass,useValue,useFactory, and scopes. Read defining-providers.md - Injection Context: Where
inject()is allowed,runInInjectionContext, andassertInInjectionContext. Read injection-context.md - Hierarchical Injectors: The
EnvironmentInjectorvsElementInjector, resolution rules, modifiers (optional,skipSelf), andprovidersvsviewProviders. Read hierarchical-injectors.md
Pipes
When formatting values in templates, creating custom pipes, or reusing pipe-like logic in TypeScript, consult the following reference. Prefer pipes in templates; outside templates, avoid injecting pipe classes just to call transform().
- Pipes: Built-in pipe imports, custom pipe naming and implementation, pure vs impure pipes, and TypeScript reuse patterns using standalone formatting functions or extracted plain functions. Read pipes.md
Angular Aria
When building accessible custom components for any of the following patterns: Accordion, Listbox, Combobox, Menu, Tabs, Toolbar, Tree, Grid, consult the following reference:
- Angular Aria Components: Building headless, accessible components (Accordion, Listbox, Combobox, Menu, Tabs, Toolbar, Tree, Grid) and styling ARIA attributes. Read angular-aria.md
Routing
When implementing navigation in Angular, consult the following references:
- Define Routes: URL paths, static vs dynamic segments, wildcards, and redirects. Read define-routes.md
- Route Loading Strategies: Eager vs lazy loading, and context-aware loading. Read loading-strategies.md
- Show Routes with Outlets: Using
<router-outlet>, nested outlets, and named outlets. Read show-routes-with-outlets.md - Navigate to Routes: Declarative navigation with
RouterLinkand programmatic navigation withRouter. Read navigate-to-routes.md - Control Route Access with Guards: Implementing
CanActivate,CanMatch, and other guards for security. Read route-guards.md - Data Resolvers: Pre-fetching data before route activation with
ResolveFn. Read data-resolvers.md - Router Lifecycle and Events: Chronological order of navigation events and debugging. Read router-lifecycle.md
- Rendering Strategies: Choosing between CSR, SSG (prerendering), and SSR. Read rendering-strategies.md
- Server and Hybrid Rendering: Implementing server routes, prerendering, hydration, server-compatible code, and request data in an SSR-configured app. Read server-side-rendering.md
- Route Transition Animations: Enabling and customizing the View Transitions API. Read route-animations.md
If you require deeper documentation or more context, visit the official Angular Routing guide.
Styling and Animations
When implementing styling and animations in Angular, consult the following references:
- Using Tailwind CSS with Angular: Integrating Tailwind CSS into Angular projects. Read tailwind-css.md
- Angular Animations: Using native CSS (recommended) or the legacy DSL for dynamic effects. Read angular-animations.md
- Styling components: Best practices for component styles and encapsulation. Read component-styling.md
Testing
When writing or updating tests, consult the following references based on the task:
- Fundamentals: Best practices for unit testing (Vitest), async patterns, and
TestBed. Read testing-fundamentals.md - Component Harnesses: Standard patterns for robust component interaction. Read component-harnesses.md
- Router Testing: Using
RouterTestingHarnessfor reliable navigation tests. Read router-testing.md - End-to-End (E2E) Testing: Setting up and running E2E tests. Read e2e-testing.md
Tooling
When working with Angular tooling, consult the following references:
- Angular CLI: Creating applications, generating code (components, routes, services), serving, and building. Read cli.md
- Code Modernization: Automatically refactoring to modern standards using migrations. Read migrations.md
- Angular MCP Server: Available tools, configuration, and experimental features. Read mcp.md
- Environment Configuration: Strategies for build-time and runtime configuration. Read environment-configuration.md
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
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.

