Skip to main content
skill CX Codex

angular-development — Claude Code skill: Angular and TypeScript rules

Tells the agent how to write Angular, SASS and TypeScript: strict typing, standalone components, signals. Useful once your project is already on Angular.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add Mindrally/skills --skill angular-development -a claude-code
Open on GitHub

What angular-development does

The skill turns the assistant into an Angular developer with a fixed set of principles. Data models get interfaces, any is off the table, and files follow kebab-case with suffixes like user-profile.component.ts. Component composition comes before inheritance, and variable names should read like isUserLoggedIn.

State and templates have their own rules. Angular signals handle reactivity, services are injected with inject, and templates use the async pipe, NgOptimizedImage and deferred loading. For lists the skill suggests trackBy; for heavy computation, pure pipes. Direct DOM access and innerHTML are discouraged because Angular's built-in sanitization already covers XSS.

Testing gets a section too: Arrange-Act-Assert, with coverage for services, components and utilities. Code style is pinned down as well — single quotes, 2-space indentation, const for constants. On a React or Vue codebase this skill works against you: it pulls the agent toward Angular conventions, so every edit is worth checking.

What it helps with

  • keep strict typing and drop any from a new service
  • migrate a component to standalone without NgModule
  • replace manual subscriptions with signals
  • speed up rendering of a long list with trackBy
  • structure unit tests around Arrange-Act-Assert

Example prompts for the agent

  • Create a standalone user profile component with a signal for the loading state
  • Refactor this service: remove any, define interfaces for the models and inject dependencies with inject
  • Optimize the ngFor in the orders list and add trackBy

How to install angular-development

1Skills CLI (Vercel)

npx skills add Mindrally/skills --skill angular-development -a claude-code

2Manually: put the files in place

~/.claude/skills/angular-development/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/angular-development/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about angular-development

How do I install angular-development in Claude?

Run npx skills add Mindrally/skills --skill angular-development -a claude-code. The skill file then lives at ~/.claude/skills/angular-development/SKILL.md.

What does angular-development do?

It gives the agent Angular and TypeScript conventions: interfaces instead of any, standalone components, signals for state, inject for services. It also covers file naming and code style.

Which platforms support the skill?

Claude, Codex, Cursor, GitHub Copilot, Gemini CLI and OpenCode. Each platform has its own install command and its own SKILL.md path.

Source text

SKILL.md · Apache-2.0
---
name: angular-development
description: Expert guidance for Angular and TypeScript development focused on scalable, high-performance web applications
metadata:
  maintainer: Mindrally
  source: https://github.com/Mindrally/skills
---

# Angular Development

You are an Angular, SASS, and TypeScript expert focused on creating scalable and high-performance web applications.

## Key Development Principles

### Type Safety with Interfaces
- Define data models using interfaces for explicit types
- Maintain strict typing to avoid `any`
- Use TypeScript's type system to define specific types

### Component Composition
- Favor component composition over inheritance
- Enhance modularity, enabling reusability and easy maintenance

### Meaningful Naming
- Use descriptive variable names like `isUserLoggedIn`, `userPermissions`
- Communicate intent clearly through naming

### File Naming
- Enforce kebab-case naming for files (e.g., `user-profile.component.ts`)
- Match Angular's conventions for file suffixes

## Angular Best Practices

### Standalone Components
- Use standalone components as appropriate
- Promote code reusability without relying on Angular modules

### Signals for State Management
- Utilize Angular's signals system for efficient reactive programming
- Enhance both state handling and rendering performance

### Service Injection
- Use the `inject` function to inject services directly
- Reduce boilerplate code

### Template Best Practices
- Use `async` pipe for observables in templates
- Enable lazy loading for feature modules
- Use `NgOptimizedImage` for efficient image loading
- Implement deferrable views for non-essential components

## File Structure

- **Component Files**: `*.component.ts`
- **Service Files**: `*.service.ts`
- **Module Files**: `*.module.ts`
- **Directive Files**: `*.directive.ts`
- **Pipe Files**: `*.pipe.ts`
- **Test Files**: `*.spec.ts`

## Coding Standards

- Use single quotes for string literals
- Use 2-space indentation
- Prefer `const` for constants and immutable variables
- Use template literals for string interpolation

## Performance Optimization

- Use trackBy functions with `ngFor` to optimize list rendering
- Apply pure pipes for computationally heavy operations
- Avoid direct DOM manipulation
- Leverage Angular's signals system to reduce unnecessary re-renders

## Security Best Practices

- Prevent XSS by relying on Angular's built-in sanitization
- Avoid `innerHTML`
- Sanitize dynamic content using Angular's trusted sanitization methods

## Testing

- Adhere to the Arrange-Act-Assert pattern for unit tests
- Ensure high test coverage for services, components, and utilities

© Mindrally · Apache-2.0 · Mindrally/skills

Similar skills

Everything for Frontend and UI →

From the same set168

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor