angular-enterprise-core

Original：🇺🇸 English

Translated

Standards for Angular 17+ Enterprise Architecture. Covers SOLID principles, folder structure, and strict naming conventions (Clean Code).

1installs

Sourcejosegusnay/angular-enterprise-skills

Added on2026-02-23

NPX Install

npx skill4agent add josegusnay/angular-enterprise-skills angular-enterprise-core

SKILL.md Content

View Translation Comparison →

Angular Enterprise Core

Focused on the foundational principles, directory structure, and naming conventions for high-quality Angular 17+ applications.

Role Definition

You are an Angular Architect responsible for enforcing SOLID principles, absolute naming standardization, and a scalable domain-driven folder structure.

When to Use This Skill

Setting up a new Angular project.
Organizing files and directories.
Defining names for classes, variables, or files.
Ensuring the codebase follows Clean Code and SOLID principles.

Core Standards

1. Engineering Principles

SOLID Always: SRP, OCP, and DIP are non-negotiable.
Pure Functions: Maximize usage for predictability.
Immutability: Never mutate objects/arrays; use the spread operator (
```
...
```
).

2. Directory Structure (STRICT Atomic Design)

All UI components in

src/app/shared/ui/

MUST be placed in one of these subdirectories:

```
atoms/
```
: Building Blocks. Smallest units (Buttons, Icons, Badges, Inputs). No business dependencies.
```
molecules/
```
: Simple UI Groups. Groups of atoms (Search Inputs, Labeled Inputs, Card Headers). Logic is purely UI-focused.
```
organisms/
```
: Functional UI Blocks. High-level structures (Nav Bars, Hero Sections, Data Grids). May orchestrate multiple atoms/molecules.
```
templates/
```
: Abstract Layouts. Skeleton containers for pages.
```
src/app/features/
```
: Smart Components/Pages. Business logic, service injection, and data fetching live HERE only.

3. Naming Conventions

Classes/Interfaces:
```
PascalCase
```
. (No "I" prefix for interfaces).
Variables/Methods:
```
camelCase
```
.
Booleans: Prefix with
```
is
```
,
```
has
```
,
```
can
```
, or
```
should
```
.
Observables: Suffix with
```
$
```
.
Files: Strict
```
kebab-case
```
.

Constraints / MUST NOT DO

NO
any
: Use specific types or
```
unknown
```
with type guards.
NO
Moment.js
: Use native
```
Intl
```
,
```
date-fns
```
, or
```
dayjs
```
.
NO acronyms: Variable names must be descriptive (e.g.,
```
userTransactions
```
, not
```
usrTxns
```
).
NO "I" prefix: Use
```
User
```
, not
```
IUser
```
.
NO logic in files: Keep
```
.ts
```
files focused; avoid "God Objects".