[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79DHA6HXFDZ68J3E1KXPPVE":3,"skill-same:01M79DHA6HXFDZ68J3E1KXPPVE":220},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M79DHA6HXFDZ68J3E1KXPPVE","angular-developer",null,"Generates Angular code and provides architectural guidance. Trigger when creating projects, components, or services, or for best practices on reactivity (signals, linkedSignal, resource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, or CLI tooling.","araketski\u002Fpi-packages","araketski","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F211123241?v=4","01M79DGNR6TAW7QF1C5MKPYZER","Aliaksei Raketski","01M79DGNSAHG54WD4Q20WQ014N",0,"MIT","https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: angular-developer\ndescription: Generates Angular code and provides architectural guidance. Trigger when creating projects, components, or services, or for best practices on reactivity (signals, linkedSignal, resource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, or CLI tooling.\nlicense: MIT\nmetadata:\n  author: Copyright 2026 Google LLC\n  version: '1.0'\n---\n\n# Angular Developer Guidelines\n\n1. 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.\n\n2. 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.\n\n3. Once you finish generating code, run `ng build` to 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.\n\n4. When you need version-aware Angular best practices or official angular.dev documentation search, use the local helper scripts documented in [docs-helpers.md](references\u002Fdocs-helpers.md).\n\n## Creating New Projects\n\nIf no guidelines are provided by the user, here are same default rules to follow when creating a new Angular project:\n\n1. Use the latest stable version of Angular unless the user specifies otherwise.\n2. Use Signals Forms for form management in new projects (available in Angular v21 and newer) [Find out more](references\u002Fsignal-forms.md).\n\n**Execution Rules for `ng new`:**\nWhen asked to create a new Angular project, you must determine the correct execution command by following these strict steps:\n\n**Step 1: Check for an explicit user version.**\n\n- **IF** the user requests a specific version (e.g., Angular 15), bypass local installations and strictly use `npx`.\n- **Command:** `npx @angular\u002Fcli@\u003Crequested_version> new \u003Cproject-name>`\n\n**Step 2: Check for an existing Angular installation.**\n\n- **IF** no specific version is requested, run `ng version` in the terminal to check if the Angular CLI is already installed on the system.\n- **IF** the command succeeds and returns an installed version, use the local\u002Fglobal installation directly.\n- **Command:** `ng new \u003Cproject-name>`\n\n**Step 3: Fallback to Latest.**\n\n- **IF** no specific version is requested AND the `ng version` command fails (indicating no Angular installation exists), you must use `npx` to fetch the latest version.\n- **Command:** `npx @angular\u002Fcli@latest new \u003Cproject-name>`\n\n## Components\n\nWhen working with Angular components, consult the following references based on the task:\n\n- **Fundamentals**: Anatomy, metadata, core concepts, and template control flow (@if, @for, @switch). Read [components.md](references\u002Fcomponents.md)\n- **Inputs**: Signal-based inputs, transforms, and model inputs. Read [inputs.md](references\u002Finputs.md)\n- **Outputs**: Signal-based outputs and custom event best practices. Read [outputs.md](references\u002Foutputs.md)\n- **Host Elements**: Host bindings and attribute injection. Read [host-elements.md](references\u002Fhost-elements.md)\n\nIf you require deeper documentation not found in the references above, read the documentation at `https:\u002F\u002Fangular.dev\u002Fguide\u002Fcomponents`.\n\n## Reactivity and Data Management\n\nWhen managing state and data reactivity, use Angular Signals and consult the following references:\n\n- **Signals Overview**: Core signal concepts (`signal`, `computed`), reactive contexts, and `untracked`. Read [signals-overview.md](references\u002Fsignals-overview.md)\n- **Dependent State (`linkedSignal`)**: Creating writable state linked to source signals. Read [linked-signal.md](references\u002Flinked-signal.md)\n- **Async Reactivity (`resource`)**: Fetching asynchronous data directly into signal state. Read [resource.md](references\u002Fresource.md)\n- **Side Effects (`effect`)**: Logging, third-party DOM manipulation (`afterRenderEffect`), and when NOT to use effects. Read [effects.md](references\u002Feffects.md)\n\n## Forms\n\nIn most cases for new apps, **prefer signal forms**. When making a forms decision, analyze the project and consider the following guidelines:\n\n- if the application is using v21 or newer and this is a new form, **prefer signal forms**.\n  -For older applications or when working with existing forms, use the appropriate form type that matches the applications current form strategy.\n\n- **Signal Forms**: Use signals for form state management. Read [signal-forms.md](references\u002Fsignal-forms.md)\n- **Template-driven forms**: Use for simple forms. Read [template-driven-forms.md](references\u002Ftemplate-driven-forms.md)\n- **Reactive forms**: Use for complex forms. Read [reactive-forms.md](references\u002Freactive-forms.md)\n\n## Dependency Injection\n\nWhen implementing dependency injection in Angular, follow these guidelines:\n\n- **Fundamentals**: Overview of Dependency Injection, services, and the `inject()` function. Read [di-fundamentals.md](references\u002Fdi-fundamentals.md)\n- **Creating and Using Services**: Creating services, the `providedIn: 'root'` option, and injecting into components or other services. Read [creating-services.md](references\u002Fcreating-services.md)\n- **Defining Dependency Providers**: Automatic vs manual provision, `InjectionToken`, `useClass`, `useValue`, `useFactory`, and scopes. Read [defining-providers.md](references\u002Fdefining-providers.md)\n- **Injection Context**: Where `inject()` is allowed, `runInInjectionContext`, and `assertInInjectionContext`. Read [injection-context.md](references\u002Finjection-context.md)\n- **Hierarchical Injectors**: The `EnvironmentInjector` vs `ElementInjector`, resolution rules, modifiers (`optional`, `skipSelf`), and `providers` vs `viewProviders`. Read [hierarchical-injectors.md](references\u002Fhierarchical-injectors.md)\n\n## Angular Aria\n\nWhen building accessible custom components for any of the following patterns: Accordion, Listbox, Combobox, Menu, Tabs, Toolbar, Tree, Grid, consult the following reference:\n\n- **Angular Aria Components**: Building headless, accessible components (Accordion, Listbox, Combobox, Menu, Tabs, Toolbar, Tree, Grid) and styling ARIA attributes. Read [angular-aria.md](references\u002Fangular-aria.md)\n\n## Routing\n\nWhen implementing navigation in Angular, consult the following references:\n\n- **Define Routes**: URL paths, static vs dynamic segments, wildcards, and redirects. Read [define-routes.md](references\u002Fdefine-routes.md)\n- **Route Loading Strategies**: Eager vs lazy loading, and context-aware loading. Read [loading-strategies.md](references\u002Floading-strategies.md)\n- **Show Routes with Outlets**: Using `\u003Crouter-outlet>`, nested outlets, and named outlets. Read [show-routes-with-outlets.md](references\u002Fshow-routes-with-outlets.md)\n- **Navigate to Routes**: Declarative navigation with `RouterLink` and programmatic navigation with `Router`. Read [navigate-to-routes.md](references\u002Fnavigate-to-routes.md)\n- **Control Route Access with Guards**: Implementing `CanActivate`, `CanMatch`, and other guards for security. Read [route-guards.md](references\u002Froute-guards.md)\n- **Data Resolvers**: Pre-fetching data before route activation with `ResolveFn`. Read [data-resolvers.md](references\u002Fdata-resolvers.md)\n- **Router Lifecycle and Events**: Chronological order of navigation events and debugging. Read [router-lifecycle.md](references\u002Frouter-lifecycle.md)\n- **Rendering Strategies**: CSR, SSG (Prerendering), and SSR with hydration. Read [rendering-strategies.md](references\u002Frendering-strategies.md)\n- **Route Transition Animations**: Enabling and customizing the View Transitions API. Read [route-animations.md](references\u002Froute-animations.md)\n\nIf you require deeper documentation or more context, visit the [official Angular Routing guide](https:\u002F\u002Fangular.dev\u002Fguide\u002Frouting).\n\n## Styling and Animations\n\nWhen implementing styling and animations in Angular, consult the following references:\n\n- **Using Tailwind CSS with Angular**: Integrating Tailwind CSS into Angular projects. Read [tailwind-css.md](references\u002Ftailwind-css.md)\n- **Angular Animations**: Using native CSS (recommended) or the legacy DSL for dynamic effects. Read [angular-animations.md](references\u002Fangular-animations.md)\n- **Styling components**: Best practices for component styles and encapsulation. Read [component-styling.md](references\u002Fcomponent-styling.md)\n\n## Testing\n\nWhen writing or updating tests, consult the following references based on the task:\n\n- **Fundamentals**: Best practices for unit testing (Vitest), async patterns, and `TestBed`. Read [testing-fundamentals.md](references\u002Ftesting-fundamentals.md)\n- **Component Harnesses**: Standard patterns for robust component interaction. Read [component-harnesses.md](references\u002Fcomponent-harnesses.md)\n- **Router Testing**: Using `RouterTestingHarness` for reliable navigation tests. Read [router-testing.md](references\u002Frouter-testing.md)\n- **End-to-End (E2E) Testing**: Best practices for E2E tests with Cypress. Read [e2e-testing.md](references\u002Fe2e-testing.md)\n\n## Tooling\n\nWhen working with Angular tooling, consult the following references:\n\n- **Angular CLI**: Creating applications, generating code (components, routes, services), serving, and building. Read [cli.md](references\u002Fcli.md)\n- **Code Modernization**: Automatically refactoring to modern standards using migrations. Read [migrations.md](references\u002Fmigrations.md)\n- **Angular documentation helpers**: Use local helper scripts for version-aware best practices and official angular.dev documentation search. Read [docs-helpers.md](references\u002Fdocs-helpers.md)\n- **Environment Configuration**: Strategies for build-time and runtime configuration. Read [environment-configuration.md](references\u002Fenvironment-configuration.md)\n","# Angular Developer Guidelines\n\n1. 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.\n\n2. 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.\n\n3. Once you finish generating code, run `ng build` to 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.\n\n4. When you need version-aware Angular best practices or official angular.dev documentation search, use the local helper scripts documented in [docs-helpers.md](references\u002Fdocs-helpers.md).\n\n## Creating New Projects\n\nIf no guidelines are provided by the user, here are same default rules to follow when creating a new Angular project:\n\n1. Use the latest stable version of Angular unless the user specifies otherwise.\n2. Use Signals Forms for form management in new projects (available in Angular v21 and newer) [Find out more](references\u002Fsignal-forms.md).\n\n**Execution Rules for `ng new`:**\nWhen asked to create a new Angular project, you must determine the correct execution command by following these strict steps:\n\n**Step 1: Check for an explicit user version.**\n\n- **IF** the user requests a specific version (e.g., Angular 15), bypass local installations and strictly use `npx`.\n- **Command:** `npx @angular\u002Fcli@\u003Crequested_version> new \u003Cproject-name>`\n\n**Step 2: Check for an existing Angular installation.**\n\n- **IF** no specific version is requested, run `ng version` in the terminal to check if the Angular CLI is already installed on the system.\n- **IF** the command succeeds and returns an installed version, use the local\u002Fglobal installation directly.\n- **Command:** `ng new \u003Cproject-name>`\n\n**Step 3: Fallback to Latest.**\n\n- **IF** no specific version is requested AND the `ng version` command fails (indicating no Angular installation exists), you must use `npx` to fetch the latest version.\n- **Command:** `npx @angular\u002Fcli@latest new \u003Cproject-name>`\n\n## Components\n\nWhen working with Angular components, consult the following references based on the task:\n\n- **Fundamentals**: Anatomy, metadata, core concepts, and template control flow (@if, @for, @switch). Read [components.md](references\u002Fcomponents.md)\n- **Inputs**: Signal-based inputs, transforms, and model inputs. Read [inputs.md](references\u002Finputs.md)\n- **Outputs**: Signal-based outputs and custom event best practices. Read [outputs.md](references\u002Foutputs.md)\n- **Host Elements**: Host bindings and attribute injection. Read [host-elements.md](references\u002Fhost-elements.md)\n\nIf you require deeper documentation not found in the references above, read the documentation at `https:\u002F\u002Fangular.dev\u002Fguide\u002Fcomponents`.\n\n## Reactivity and Data Management\n\nWhen managing state and data reactivity, use Angular Signals and consult the following references:\n\n- **Signals Overview**: Core signal concepts (`signal`, `computed`), reactive contexts, and `untracked`. Read [signals-overview.md](references\u002Fsignals-overview.md)\n- **Dependent State (`linkedSignal`)**: Creating writable state linked to source signals. Read [linked-signal.md](references\u002Flinked-signal.md)\n- **Async Reactivity (`resource`)**: Fetching asynchronous data directly into signal state. Read [resource.md](references\u002Fresource.md)\n- **Side Effects (`effect`)**: Logging, third-party DOM manipulation (`afterRenderEffect`), and when NOT to use effects. Read [effects.md](references\u002Feffects.md)\n\n## Forms\n\nIn most cases for new apps, **prefer signal forms**. When making a forms decision, analyze the project and consider the following guidelines:\n\n- if the application is using v21 or newer and this is a new form, **prefer signal forms**.\n  -For older applications or when working with existing forms, use the appropriate form type that matches the applications current form strategy.\n\n- **Signal Forms**: Use signals for form state management. Read [signal-forms.md](references\u002Fsignal-forms.md)\n- **Template-driven forms**: Use for simple forms. Read [template-driven-forms.md](references\u002Ftemplate-driven-forms.md)\n- **Reactive forms**: Use for complex forms. Read [reactive-forms.md](references\u002Freactive-forms.md)\n\n## Dependency Injection\n\nWhen implementing dependency injection in Angular, follow these guidelines:\n\n- **Fundamentals**: Overview of Dependency Injection, services, and the `inject()` function. Read [di-fundamentals.md](references\u002Fdi-fundamentals.md)\n- **Creating and Using Services**: Creating services, the `providedIn: 'root'` option, and injecting into components or other services. Read [creating-services.md](references\u002Fcreating-services.md)\n- **Defining Dependency Providers**: Automatic vs manual provision, `InjectionToken`, `useClass`, `useValue`, `useFactory`, and scopes. Read [defining-providers.md](references\u002Fdefining-providers.md)\n- **Injection Context**: Where `inject()` is allowed, `runInInjectionContext`, and `assertInInjectionContext`. Read [injection-context.md](references\u002Finjection-context.md)\n- **Hierarchical Injectors**: The `EnvironmentInjector` vs `ElementInjector`, resolution rules, modifiers (`optional`, `skipSelf`), and `providers` vs `viewProviders`. Read [hierarchical-injectors.md](references\u002Fhierarchical-injectors.md)\n\n## Angular Aria\n\nWhen building accessible custom components for any of the following patterns: Accordion, Listbox, Combobox, Menu, Tabs, Toolbar, Tree, Grid, consult the following reference:\n\n- **Angular Aria Components**: Building headless, accessible components (Accordion, Listbox, Combobox, Menu, Tabs, Toolbar, Tree, Grid) and styling ARIA attributes. Read [angular-aria.md](references\u002Fangular-aria.md)\n\n## Routing\n\nWhen implementing navigation in Angular, consult the following references:\n\n- **Define Routes**: URL paths, static vs dynamic segments, wildcards, and redirects. Read [define-routes.md](references\u002Fdefine-routes.md)\n- **Route Loading Strategies**: Eager vs lazy loading, and context-aware loading. Read [loading-strategies.md](references\u002Floading-strategies.md)\n- **Show Routes with Outlets**: Using `\u003Crouter-outlet>`, nested outlets, and named outlets. Read [show-routes-with-outlets.md](references\u002Fshow-routes-with-outlets.md)\n- **Navigate to Routes**: Declarative navigation with `RouterLink` and programmatic navigation with `Router`. Read [navigate-to-routes.md](references\u002Fnavigate-to-routes.md)\n- **Control Route Access with Guards**: Implementing `CanActivate`, `CanMatch`, and other guards for security. Read [route-guards.md](references\u002Froute-guards.md)\n- **Data Resolvers**: Pre-fetching data before route activation with `ResolveFn`. Read [data-resolvers.md](references\u002Fdata-resolvers.md)\n- **Router Lifecycle and Events**: Chronological order of navigation events and debugging. Read [router-lifecycle.md](references\u002Frouter-lifecycle.md)\n- **Rendering Strategies**: CSR, SSG (Prerendering), and SSR with hydration. Read [rendering-strategies.md](references\u002Frendering-strategies.md)\n- **Route Transition Animations**: Enabling and customizing the View Transitions API. Read [route-animations.md](references\u002Froute-animations.md)\n\nIf you require deeper documentation or more context, visit the [official Angular Routing guide](https:\u002F\u002Fangular.dev\u002Fguide\u002Frouting).\n\n## Styling and Animations\n\nWhen implementing styling and animations in Angular, consult the following references:\n\n- **Using Tailwind CSS with Angular**: Integrating Tailwind CSS into Angular projects. Read [tailwind-css.md](references\u002Ftailwind-css.md)\n- **Angular Animations**: Using native CSS (recommended) or the legacy DSL for dynamic effects. Read [angular-animations.md](references\u002Fangular-animations.md)\n- **Styling components**: Best practices for component styles and encapsulation. Read [component-styling.md](references\u002Fcomponent-styling.md)\n\n## Testing\n\nWhen writing or updating tests, consult the following references based on the task:\n\n- **Fundamentals**: Best practices for unit testing (Vitest), async patterns, and `TestBed`. Read [testing-fundamentals.md](references\u002Ftesting-fundamentals.md)\n- **Component Harnesses**: Standard patterns for robust component interaction. Read [component-harnesses.md](references\u002Fcomponent-harnesses.md)\n- **Router Testing**: Using `RouterTestingHarness` for reliable navigation tests. Read [router-testing.md](references\u002Frouter-testing.md)\n- **End-to-End (E2E) Testing**: Best practices for E2E tests with Cypress. Read [e2e-testing.md](references\u002Fe2e-testing.md)\n\n## Tooling\n\nWhen working with Angular tooling, consult the following references:\n\n- **Angular CLI**: Creating applications, generating code (components, routes, services), serving, and building. Read [cli.md](references\u002Fcli.md)\n- **Code Modernization**: Automatically refactoring to modern standards using migrations. Read [migrations.md](references\u002Fmigrations.md)\n- **Angular documentation helpers**: Use local helper scripts for version-aware best practices and official angular.dev documentation search. Read [docs-helpers.md](references\u002Fdocs-helpers.md)\n- **Environment Configuration**: Strategies for build-time and runtime configuration. Read [environment-configuration.md](references\u002Fenvironment-configuration.md)\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"version":26},"Copyright 2026 Google LLC","1.0","main","d9b1b8c72bf261be74d3229e766adb685b940aa4","packages\u002Fangular-developer\u002Fskills\u002Fangular-developer",2,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages","https:\u002F\u002Fgithub.com\u002Faraketski","2026-10-26 23:06:21",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add araketski\u002Fpi-packages --skill angular-developer",{"tool":40,"command":41},"bunx","bunx skills add araketski\u002Fpi-packages --skill angular-developer",{"tool":43,"command":44},"pnpm","pnpm dlx skills add araketski\u002Fpi-packages --skill angular-developer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002FSKILL.md",true,[48,54,58,62,66,70,74,78,82,86,90,94,98,102,106,110,114,118,122,126,130,134,138,142,146,150,154,158,162,166,170,174,178,182,186,190,194,198,202,208,212,216],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"data\u002Fbest-practices.md","REFERENCE","参考文档",2636,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Fdata\u002Fbest-practices.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fangular-animations.md",3982,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Freferences\u002Fangular-animations.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fangular-aria.md",18453,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Freferences\u002Fangular-aria.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fcli.md",3716,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Freferences\u002Fcli.md",{"path":67,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fcomponent-harnesses.md",2816,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Freferences\u002Fcomponent-harnesses.md",{"path":71,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fcomponent-styling.md",2531,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Freferences\u002Fcomponent-styling.md",{"path":75,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fcomponents.md",3422,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Freferences\u002Fcomponents.md",{"path":79,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fcreating-services.md",2877,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Freferences\u002Fcreating-services.md",{"path":83,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fdata-resolvers.md",1634,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Freferences\u002Fdata-resolvers.md",{"path":87,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fdefine-routes.md",1731,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Freferences\u002Fdefine-routes.md",{"path":91,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fdefining-providers.md",2270,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Freferences\u002Fdefining-providers.md",{"path":95,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fdi-fundamentals.md",3479,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Freferences\u002Fdi-fundamentals.md",{"path":99,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fdocs-helpers.md",1358,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Freferences\u002Fdocs-helpers.md",{"path":103,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fe2e-testing.md",2498,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Freferences\u002Fe2e-testing.md",{"path":107,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Feffects.md",2777,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Freferences\u002Feffects.md",{"path":111,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":112,"sourceHtmlUrl":113},"references\u002Fenvironment-configuration.md",3328,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Freferences\u002Fenvironment-configuration.md",{"path":115,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":116,"sourceHtmlUrl":117},"references\u002Fhierarchical-injectors.md",2105,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Freferences\u002Fhierarchical-injectors.md",{"path":119,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":120,"sourceHtmlUrl":121},"references\u002Fhost-elements.md",2190,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Freferences\u002Fhost-elements.md",{"path":123,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":124,"sourceHtmlUrl":125},"references\u002Finjection-context.md",1933,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Freferences\u002Finjection-context.md",{"path":127,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":128,"sourceHtmlUrl":129},"references\u002Finputs.md",2506,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Freferences\u002Finputs.md",{"path":131,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":132,"sourceHtmlUrl":133},"references\u002Flinked-signal.md",2660,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Freferences\u002Flinked-signal.md",{"path":135,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":136,"sourceHtmlUrl":137},"references\u002Floading-strategies.md",1457,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Freferences\u002Floading-strategies.md",{"path":139,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":140,"sourceHtmlUrl":141},"references\u002Fmigrations.md",2075,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Freferences\u002Fmigrations.md",{"path":143,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":144,"sourceHtmlUrl":145},"references\u002Fnavigate-to-routes.md",1643,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Freferences\u002Fnavigate-to-routes.md",{"path":147,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":148,"sourceHtmlUrl":149},"references\u002Foutputs.md",2651,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Freferences\u002Foutputs.md",{"path":151,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":152,"sourceHtmlUrl":153},"references\u002Freactive-forms.md",3565,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Freferences\u002Freactive-forms.md",{"path":155,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":156,"sourceHtmlUrl":157},"references\u002Frendering-strategies.md",1828,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Freferences\u002Frendering-strategies.md",{"path":159,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":160,"sourceHtmlUrl":161},"references\u002Fresource.md",2698,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Freferences\u002Fresource.md",{"path":163,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":164,"sourceHtmlUrl":165},"references\u002Froute-animations.md",1690,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Freferences\u002Froute-animations.md",{"path":167,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":168,"sourceHtmlUrl":169},"references\u002Froute-guards.md",1397,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Freferences\u002Froute-guards.md",{"path":171,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":172,"sourceHtmlUrl":173},"references\u002Frouter-lifecycle.md",1536,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Freferences\u002Frouter-lifecycle.md",{"path":175,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":176,"sourceHtmlUrl":177},"references\u002Frouter-testing.md",3832,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Freferences\u002Frouter-testing.md",{"path":179,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":180,"sourceHtmlUrl":181},"references\u002Fshow-routes-with-outlets.md",1672,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Freferences\u002Fshow-routes-with-outlets.md",{"path":183,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":184,"sourceHtmlUrl":185},"references\u002Fsignal-forms.md",28273,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Freferences\u002Fsignal-forms.md",{"path":187,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":188,"sourceHtmlUrl":189},"references\u002Fsignals-overview.md",2855,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Freferences\u002Fsignals-overview.md",{"path":191,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":192,"sourceHtmlUrl":193},"references\u002Ftailwind-css.md",1868,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Freferences\u002Ftailwind-css.md",{"path":195,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":196,"sourceHtmlUrl":197},"references\u002Ftemplate-driven-forms.md",3758,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Freferences\u002Ftemplate-driven-forms.md",{"path":199,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":200,"sourceHtmlUrl":201},"references\u002Ftesting-fundamentals.md",2589,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Freferences\u002Ftesting-fundamentals.md",{"path":203,"resourceType":204,"resourceTypeDesc":205,"sizeBytes":206,"sourceHtmlUrl":207},"scripts\u002Fbounded-fetch.mjs","SCRIPT","脚本",3984,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Fscripts\u002Fbounded-fetch.mjs",{"path":209,"resourceType":204,"resourceTypeDesc":205,"sizeBytes":210,"sourceHtmlUrl":211},"scripts\u002Fget-best-practices.mjs",7821,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Fscripts\u002Fget-best-practices.mjs",{"path":213,"resourceType":204,"resourceTypeDesc":205,"sizeBytes":214,"sourceHtmlUrl":215},"scripts\u002Fsearch-documentation.mjs",10635,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002Fscripts\u002Fsearch-documentation.mjs",{"path":217,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":218,"sourceHtmlUrl":219},"UPSTREAM.md",375,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fangular-developer\u002Fskills\u002Fangular-developer\u002FUPSTREAM.md",[221,228,235,242,249,256],{"skillNo":222,"name":223,"nameZh":6,"description":224,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":225,"categories":226,"keywords":227,"publishedAt":19},"01M79DJSQ1DE940XNF88TSA624","taiga-ui-docs","Use when implementing, debugging, reviewing, migrating, or looking up Angular Taiga UI components. Provides a bundled helper script equivalent to Taiga UI MCP docs tools for overview\u002Fimport guidance, section lists, exact component documentation\u002Fexamples, and migration guide content from llms-full.txt.","https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Ftaiga-ui-docs\u002Fskills\u002Ftaiga-ui-docs\u002FSKILL.md",[],[],{"skillNo":229,"name":230,"nameZh":6,"description":231,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":232,"categories":233,"keywords":234,"publishedAt":19},"01M79DJN6T3K2HKXBNPCSN5T4Z","nx-workspace","Explore and understand Nx workspaces. USE WHEN answering questions about the workspace, projects, or tasks. ALSO USE WHEN an nx command fails or you need to check available targets\u002Fconfiguration before running a task. EXAMPLES: 'What projects are in this workspace?', 'How is project X configured?', 'What depends on library Y?', 'What targets can I run?', 'Cannot find configuration for task', 'debug nx task failure'.","https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fnx-developer\u002Fskills\u002Fnx-workspace\u002FSKILL.md",[],[],{"skillNo":236,"name":237,"nameZh":6,"description":238,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":239,"categories":240,"keywords":241,"publishedAt":19},"01M79DJJXEA2AKZBK49WFTVH43","nx-run-tasks","Helps with running tasks in an Nx workspace. USE WHEN the user wants to execute build, test, lint, serve, or run any other tasks defined in the workspace.","https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fnx-developer\u002Fskills\u002Fnx-run-tasks\u002FSKILL.md",[],[],{"skillNo":243,"name":244,"nameZh":6,"description":245,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":246,"categories":247,"keywords":248,"publishedAt":19},"01M79DJGSN8JRD741EB4HKNHXJ","nx-plugins","Find and add Nx plugins. USE WHEN user wants to discover available plugins, install a new plugin, or add support for a specific framework or technology to the workspace.","https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fnx-developer\u002Fskills\u002Fnx-plugins\u002FSKILL.md",[],[],{"skillNo":250,"name":251,"nameZh":6,"description":252,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":253,"categories":254,"keywords":255,"publishedAt":19},"01M79DJBPC0M2Q91P2C59JN88Q","nx-import","Import, merge, or combine repositories into an Nx workspace using nx import. USE WHEN the user asks to adopt Nx across repos, move projects into a monorepo, or bring code\u002Fhistory from another repository.","https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fnx-developer\u002Fskills\u002Fnx-import\u002FSKILL.md",[],[],{"skillNo":257,"name":258,"nameZh":6,"description":259,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":260,"categories":261,"keywords":262,"publishedAt":19},"01M79DJ78DFAHNRDKAK3ZHR7W6","nx-generate","Generate code using nx generators. INVOKE IMMEDIATELY when user mentions scaffolding, setup, structure, creating apps\u002Flibs, or setting up project structure. Trigger words - scaffold, setup, create a new app, create a new lib, project structure, generate, add a new project. ALWAYS use this BEFORE using the nx-docs skill or local Nx documentation helper or exploring - this skill handles discovery internally.","https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fnx-developer\u002Fskills\u002Fnx-generate\u002FSKILL.md",[],[]]