Angular Best Practices
CheckedHelps with Angular, best practices as part of building frontend UIs and user experiences workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add boise-state-development/agentcore-public-stack --skill angular-best-practices -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
boise-state-development
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.
Automated safety checks
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 boise-state-development/agentcore-public-stack at d22f8533f6.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- d22f8533f6
- Scanned
- 2 files, 311 lines
About this skill
What it does
This skill provides guidance on implementing best practices for Angular development, including structure, performance optimization, and maintainability. It helps developers write clean, scalable code that adheres to industry standards.
When to use it
- When building a new Angular application from scratch
- When refactoring an existing Angular project for better organization
- When optimizing the performance of an Angular app with large component trees
- When preparing an Angular app for long-term maintenance and team collaboration
Key capabilities
- Code structure recommendations (e.g., feature modules, lazy loading)
- Performance optimization techniques (e.g., change detection strategies, AOT compilation)
- Best practices for state management and data flow
- Guidance on testing and CI/CD integration
Example prompts
- "How should I organize my Angular project for scalability?"
- "What are the best practices for improving Angular app performance?"
- "Can you explain how to implement lazy loading in Angular modules?"
Tips & gotchas
- Ensure your team is familiar with Angular CLI and module-based architecture before applying these practices.
- Some optimizations may require additional tooling or configuration, such as Webpack or Bazel.