Angular Architecture

This enforces a straightforward architectural rule for Angular projects: components go in their feature folder if only that feature uses them, and they move to a shared folder once a second feature needs them. It's the kind of simple heuristic that prevents bikeshedding about folder structure on teams. The repo has 538 stars and 216 installs, so it's seeing real use. Worth grabbing if you're tired of debating where components should live or if your shared folder has become a dumping ground. The rule is opinionated enough to be useful but flexible enough that you won't fight it.

skills.sh installs: 322
GitHub stars: 665
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add gentleman-programming/gentleman-skills --skill angular-architecture --agent claude-code

Installs into .claude/skills of the current project.

Files

The Scope Rule (REQUIRED)

"Scope determines structure" - Where a component lives depends on its usage.

Usage	Placement
Used by 1 feature	`features/[feature]/components/`
Used by 2+ features	`features/shared/components/`

Example

features/
  shopping-cart/
    shopping-cart.ts          # Main component = feature name
    components/
      cart-item.ts            # Used ONLY by shopping-cart
      cart-summary.ts         # Used ONLY by shopping-cart
  checkout/
    checkout.ts
    components/
      payment-form.ts         # Used ONLY by checkout
  shared/
    components/
      button.ts               # Used by shopping-cart AND checkout
      modal.ts                # Used by multiple features