Angular Style Guide Agent Skill

Naming conventions, file structure, and coding standards for Angular projects. Use for Angular-specific naming and organization; defer language-only TypeScript naming questions.

2k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

536

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/HoangNguyen0403/agent-skills-standard --skill angular-style-guide

What comes with it

5 290 bytes besides the instruction

evals/evals.json

references/naming-convention.md

The instruction itself

8 sections, as written by the author

Angular Style Guide

Priority: P0 (CRITICAL)

Principles

Single Responsibility: 1 component/service per file. Functions < 75 lines.
Size Limits: Files < 400 lines. Refactor if larger.
Strict Naming: kebab-case with type suffix (e.g., hero-list.component.ts, auth.service.ts, user.pipe.ts, app.routes.ts).
Barrels: index.ts for public APIs only. No deep barrel imports within same feature — import directly. Wrong barrel placement breaks tree-shaking.
LIFT: Locate code quickly, Identify files by name, keep Flattest structure possible, Try to be DRY.

Naming Standards

Files: kebab-case.type.ts
Classes: PascalCase + type suffix (HeroListComponent, AuthService)
Directives: camelCase selector with app prefix (e.g., appHighlight)
Pipes: camelCase name (e.g., truncate)
Services: PascalCase + Service suffix (HeroService)
Interfaces: No — do not use IUser/IHero. Name as nouns: User, Hero. The I-prefix is not recommended by Angular style guide.

Folder Structure

Core: src/app/core/ (singletons and global state).
Shared: src/app/shared/ (reusable UI and pipes).
Features: src/app/features/ (lazy-loaded). Folder depth ≤ 3 levels — no deeper nesting.

Anti-Patterns

No logic in templates: Move to component class or computed() signal.
No deep nesting: Keep folder depth ≤3 levels.
No I-prefix on interfaces: Name interfaces User, not IUser.

References

Naming Conventions

Canonical response anchors

When this skill applies, preserve the following domain terminology or equivalent concrete examples in the answer when relevant:

app prefix,appHighlight,appFocusTrap
Flattest structure
do not use I,avoid the I-prefix,no I-prefix,do not prefix,No. Do not

Other skills for the same job

different authors, same section of the catalogue

MCP Builder

by anthropics

vendor ×13

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

774 tokens

Finishing A Development Branch

by ZhanlinCui

×7

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Vercel React Native Skills

by vercel-labs

vendor ×6

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

39k tokens

Vercel React Best Practices

by ratacat

×5

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

1k tokens

How to use it

Copy the folder

Take hoangnguyen0403/angular-style-guide from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.