angular-style-guide
/angular-style-guide
Naming conventions, file structure, and coding standards for Angular projects. Use for Angular-specific naming and organization; defer language-only TypeScript naming questions.
- Author
- HoangNguyen0403 ↗
- Repository
- agent-skills-standard ↗
- Licence
- MIT
- Last repository change
- 22.10.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 22.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Naming conventions, file structure, and coding standards for Angular projects. Use for Angular-specific naming and organization; defer language-only TypeScript naming questions.
Original author description
Naming conventions, file structure, and coding standards for Angular projects. Use for Angular-specific naming and organization; defer language-only TypeScript naming questions.
How it works
- Priority: P0 (CRITICAL)
- Principles
- Naming Standards
- Folder Structure
- Anti-Patterns
- References
- Canonical response anchors
SKILL.md preview
---
name: angular-style-guide
description: Naming conventions, file structure, and coding standards for Angular projects. Use for Angular-specific naming and organization; defer language-only TypeScript naming questions.
metadata:
triggers:
keywords:
- angular style
- naming convention
- file structure
- angular-style-guide
---
# 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](references/naming-convention.md)
## 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
Files in this package (3)
- SKILL.md 2 KB
- evals/evals.json 4 KB
- references/naming-convention.md 1 KB
Versions
The database has no other skills named angular-style-guide.
Database snapshot: 13.11.2026 · package version fac7607d2f62 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100angular
Angular-specific coding standards and best practices Triggers on: **/*.ts, **/*.html, **/*.scss, **/*.css - 100cpp-naming-check
Check C++ naming conventions against Google Style Guide. Use when checking if names follow conventions or when renaming identifiers. - 100angular-architecture
Standards for Angular project structure, feature modules, and lazy loading. Use when structuring Angular apps, defining feature modules, or configuring lazy loading. - 96angular-conventions
Modern Angular (v18+) coding standards — signals, standalone, OnPush, inject(), built-in control flow. Use when writing, refactoring or reviewing Angular code. - 90typescript-conventions
Framework-agnostic TypeScript conventions for frontend code (Angular, React, Next.js): strict tsconfig, ESLint flat config with Prettier, naming and module layout, no barrel-file cycles, runtime validation at I/O boundaries with zod or valibot, typed environment access, date and… - 96angular
Angular开发专家助手。当用户需要进行Angular前端开发、TypeScript企业级应用、RxJS响应式编程或SPA开发时调用。