angular-best-practices
Angular performance optimization and best practices guide. Use when writing, reviewing, or refactoring Angular code for optimal performance, bundle size, and rendering efficiency.
86
Quality
81%
Does it follow best practices?
Impact
100%
1.13xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
75%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description has good structure with explicit 'Use when' guidance and clear Angular-specific focus, making it complete and distinctive. However, it lacks specific concrete actions (what optimization techniques it covers) and could include more natural trigger terms users might actually say when experiencing Angular performance issues.
Suggestions
Add specific concrete actions like 'implement lazy loading, configure OnPush change detection, optimize template expressions, reduce bundle size with tree shaking'
Include more natural trigger terms users might say: 'slow Angular app', 'large bundle', 'change detection issues', 'lazy loading', 'AOT', 'zone.js'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Angular) and mentions general areas (performance, bundle size, rendering efficiency) but doesn't list specific concrete actions like 'implement lazy loading', 'configure change detection', or 'optimize template bindings'. | 2 / 3 |
Completeness | Clearly answers both what ('Angular performance optimization and best practices guide') and when ('Use when writing, reviewing, or refactoring Angular code for optimal performance, bundle size, and rendering efficiency') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'Angular', 'performance', 'bundle size', 'rendering' but misses common variations users might say like 'slow Angular app', 'reduce build size', 'change detection', 'lazy loading', or 'AOT compilation'. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Angular-specific performance optimization, which is distinct from general JavaScript/TypeScript skills or other framework skills. The combination of 'Angular' + 'performance' creates a clear niche. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality Angular performance skill with excellent actionability through concrete CORRECT/WRONG code patterns and strong organization via priority tables and checklists. The content is appropriately concise for Claude's knowledge level. The main weakness is the lack of explicit validation workflows - there's no guidance on how to verify optimizations are working (e.g., measuring bundle size, profiling change detection cycles).
Suggestions
Add a validation section with commands to verify optimizations (e.g., `ng build --stats-json` for bundle analysis, Chrome DevTools profiling steps)
Include expected outcomes or metrics for each optimization category (e.g., 'OnPush should reduce change detection cycles by X%')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables for quick reference, code examples without unnecessary explanation, and assuming Claude understands Angular concepts. No verbose explanations of what Angular or change detection is. | 3 / 3 |
Actionability | Every section provides executable, copy-paste ready code examples with clear CORRECT/WRONG patterns. The code is complete TypeScript/HTML that can be directly used in Angular projects. | 3 / 3 |
Workflow Clarity | While the content has clear checklists and prioritized categories, it lacks explicit validation steps or feedback loops. The checklists are verification-oriented but don't include how to validate that optimizations worked (e.g., bundle size checks, performance profiling steps). | 2 / 3 |
Progressive Disclosure | Content is well-organized with a priority table upfront, clear section headers, and external resource links at the end. The quick reference checklists provide excellent navigation for different use cases without requiring additional files. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (564 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- boisenoise/skills-collections
- Commit
5c5ae21
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.