Skip to content
TrustedSkillsbeta
Back to all skills

Angular Best Practices Rule Creator

Checked
alfredoperez·vlatest·frontend

Helps with Angular, best practices as part of building frontend UIs and user experiences workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add alfredoperez/angular-best-practices --skill angular-best-practices-rule-creator -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

alfredoperez

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned alfredoperez/angular-best-practices at a499a47861.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
a499a47861
Manifest
.claude/skills/angular-best-practices-rule-creator/SKILL.md
Scanned
1 file, 126 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill generates custom ESLint rules specifically designed to enforce Angular best practices within your codebase. It analyzes project requirements and outputs ready-to-use rule configurations that ensure consistent coding standards.

When to use it

  • Standardizing complex component logic across a large team of developers.
  • Enforcing specific architectural patterns like standalone components or signal usage.
  • Reducing code review time by automating the detection of common Angular anti-patterns.
  • Integrating strict linting policies into CI/CD pipelines for new projects.

Key capabilities

  • Generates custom ESLint rules tailored to your project's specific Angular version and style guide.
  • Provides configuration files that can be directly integrated into existing build workflows.
  • Focuses on maintaining code quality by preventing deviations from established best practices.

Example prompts

  • "Create an ESLint rule that enforces the use of @Input() over setters in all Angular components."
  • "Generate a custom rule to ensure every standalone component includes a standalone: true flag."
  • "Write an ESLint configuration to detect and warn against using ngOnChanges when input signals are available."

Tips & gotchas

Ensure your project is initialized with Angular before generating rules, as the output relies on specific framework metadata. While the skill creates robust rules, manually reviewing generated code for edge cases in complex business logic is recommended.