Skip to content
TrustedSkillsbeta
Back to all skills

Angular Best Practices Spartan

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-spartan -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
skills/angular-best-practices-spartan/SKILL.md
Scanned
2 files, 117 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 enforces Angular development standards specifically tailored for the Spartan framework, ensuring code consistency and maintainability. It automatically applies best practices to your project configuration and component structure during the build process.

When to use it

  • You are building a new Angular application using the Spartan architecture and need immediate standardization.
  • Your team requires automated enforcement of specific coding conventions to reduce technical debt.
  • You want to ensure compatibility between Angular core features and Spartan-specific patterns.
  • You need to streamline CI/CD pipelines by validating code against established best practices before deployment.

Key capabilities

  • Applies Angular-specific best practices relevant to the Spartan ecosystem.
  • Validates project structure and component implementation against defined standards.
  • Provides automated feedback on code quality during the development workflow.

Example prompts

  • "Apply angular-best-practices-spartan to my current project folder."
  • "Check my existing components for violations of Spartan Angular standards."
  • "Generate a configuration file that enforces these best practices in my build pipeline."

Tips & gotchas

Ensure your project is already initialized with the base Spartan framework before running this skill, as it relies on specific architectural patterns. This skill focuses on convention enforcement rather than fixing complex logic errors within your business rules.