mcpField
A
angular-best-practices

angular-best-practices

github.com/sickn33Development49.0k507 installsUpdated today
Repository

About angular-best-practices

A performance optimization guide for Angular developers writing or reviewing applications. Its prioritized rules cover bundles, rendering, data fetching, and SSR or hydration configuration.

Key features

  1. 01Prioritized optimization rules
  2. 02Component and page guidance
  3. 03Data-fetching patterns
  4. 04Bundle and rendering advice
  5. 05SSR and hydration guidance

Use cases

  1. 01Building Angular components or pages
  2. 02Reviewing performance issues
  3. 03Reducing bundle size or load times
  4. 04Configuring SSR or hydration

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sickn33/agentic-awesome-skills --skill angular-best-practices

After installing, type/angular-best-practicesin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

metadata.json
README.md
references/
detailed-guide.md

Details

From the project README

Angular Best Practices

Comprehensive performance optimization guide for Angular applications. Contains prioritized rules for eliminating performance bottlenecks, optimizing bundles, and improving rendering.

Detailed Guide

Read the detailed guide before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end-to-end work, read the guide completely.

When to Use

Reference these guidelines when:

  • Writing new Angular components or pages
  • Implementing data fetching patterns
  • Reviewing code for performance issues
  • Refactoring existing Angular code
  • Optimizing bundle size or load times
  • Configuring SSR/hydration

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Comments

Markdown supported