Angular Core
CheckedGenerates Angular components, services, modules, and pipes based on specifications, adhering to best practices.
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 gentleman-programming/gentleman-skills --skill angular-core -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
gentleman-programming
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 gentleman-programming/gentleman-skills at c8036a3789.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- c8036a3789
- Manifest
- curated/angular/core/SKILL.md
- Scanned
- 1 file, 188 lines
About this skill
What it does
This skill generates Angular components, services, modules, and pipes based on specifications, adhering to best practices for modern Angular development. It focuses on creating standalone components by default and leverages Signals for state management instead of traditional lifecycle hooks or RxJS where possible. The generated code emphasizes function-based input/output bindings over decorator-based approaches.
When to use it
- You need to quickly generate boilerplate Angular component structures.
- You want to ensure your new components follow modern Angular architectural patterns using Signals.
- You're building a new Angular project and want a consistent code style for your components.
- You are refactoring existing Angular components to use Signals instead of lifecycle hooks.
Key capabilities
- Generates standalone Angular components by default.
- Creates input/output functions using the function-based approach (e.g.,
readonly user = input.required<User>();). - Implements state management using Angular Signals for reactivity and derived values.
- Provides examples of how to use
effect()for side effects and computed properties for derived data. - Demonstrates the correct usage of
inject()for dependency injection, avoiding constructor-based injection. - Generates native control flow structures like
@if,@for, and@switch.
Example prompts
- "Generate a UserComponent with an input for userId and display the user's name."
- "Create a component that uses Signals to track a count value and its doubled value."
- "Show me how to use
inject()to get the HttpClient service in an Angular component."
Tips & gotchas
- The skill enforces standalone components; setting
standalone: trueis discouraged. - Traditional lifecycle hooks (e.g.,
ngOnInit,ngOnChanges) are not supported and should be replaced with Signals and effects. - Signals are the preferred method for managing component state, use RxJS only when dealing with complex asynchronous operations.