home / skills / partme-ai / full-stack-skills / angular
/skills/angular
This skill provides comprehensive Angular guidance for building components, modules, services, routing, and forms to accelerate your front-end development.
npx playbooks add skill partme-ai/full-stack-skills --skill angularReview the files below or copy the command above to add this skill to your agents.
---
name: angular
description: Provides comprehensive guidance for Angular framework including components, modules, services, dependency injection, routing, forms, and TypeScript integration. Use when the user asks about Angular, needs to create Angular applications, implement Angular components, or work with Angular features.
license: Complete terms in LICENSE.txt
---
## When to use this skill
Use this skill whenever the user wants to:
- [待完善:根据具体工具添加使用场景]
## How to use this skill
[待完善:根据具体工具添加使用指南]
## Best Practices
[待完善:根据具体工具添加最佳实践]
## Keywords
[待完善:根据具体工具添加关键词]
This skill provides comprehensive, practical guidance for building applications with the Angular framework, covering components, modules, services, dependency injection, routing, forms, and TypeScript integration. It focuses on actionable patterns, code structure, and common pitfalls to help you design maintainable, testable Angular apps. Use it to get step-by-step instructions, code snippets, and architecture advice tailored to real development scenarios.
The skill inspects your Angular goals and current project context to recommend concrete steps: creating components, structuring modules, registering providers, configuring routes, and implementing reactive or template-driven forms. It explains TypeScript typings and Angular CLI commands, suggests folder layouts, and provides examples for lifecycle hooks, change detection strategies, and unit testing. When you supply code or error messages, it offers targeted fixes and best-practice refactors.
Should I use Reactive Forms or Template-driven Forms?
Use Reactive Forms for complex validation, dynamic form controls, or when you need explicit form state management. Template-driven Forms are fine for simple forms with minimal logic.
How do I decide between services providedIn: 'root' and module providers?
Provide services in 'root' for singletons accessible app-wide. Provide services in a feature module to limit scope and create separate instances when the module is lazy-loaded.