skill-creator

When to Create a Skill

Create an Angular skill when:

• An Angular pattern is used repeatedly and AI needs guidance
• Angular version-specific conventions need documentation
• Complex Angular workflows need step-by-step instructions
• Migration paths between Angular versions require clarity
• Decision trees help AI choose between Angular patterns (e.g., Reactive vs Signal Forms)

Don't create a skill when:

• Official Angular documentation already covers it thoroughly (reference instead)
• Pattern is trivial or self-explanatory
• It's a one-off Angular task
• The pattern applies to only one Angular version without evolution

Skill Structure