No. Do not prefix Angular interfaces with `I`. Name interfaces as nouns, such as `User` or `Hero`, rather than `IUser` or `IHero`: ```ts export interface User { id: string; displayName: string; } ``` The noun already communicates that the type is a model or contract, and the `I` prefix adds no useful information. Use the appropriate suffix for classes that implement behavior, for example `UserService`, while keeping the data contract named `User`.
Scanned 9/5/2026
Install to Claude Code
Skills Directorynpx -y skills add HoangNguyen0403/agent-skills-standard --skill angular-style-guide --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Angular Style Guide?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/hoangnguyen0403-angular-style-guide-893ca245)More formats (shields.io, HTML) on the badges page.
No. Do not prefix Angular interfaces with `I`. Name interfaces as nouns, such as `User` or `Hero`, rather than `IUser` or `IHero`:
```ts
export interface User {
id: string;
displayName: string;
}
```
The noun already communicates that the type is a model or contract, and the `I` prefix adds no useful information. Use the appropriate suffix for classes that implement behavior, for example `UserService`, while keeping the data contract named `User`.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
