agentsclimarketplace

Angular enterprise architecture

Skill angular-experts-io/ax-skills/angular-enterprise-architecture

A curated collection of mostly handcrafted skills encoding our more than a decade worth of best practices, proven patterns and lessons learned for Angular / NgRx frontend development which scales from SaaS MVP to enterprise scale environments

Install
npx -y skills add angular-experts-io/ax-skills --skill angular-enterprise-architecture

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 12 stars12 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when designing, reviewing, refactoring, or enforcing Angular application architecture with isolated lazy features, eager core/layout, reusable ui/pattern architecture building blocks, one-way dependency graphs, eslint-plugin-boundaries rules, or folder placement decisions. This skill takes precedence over angular-developer when architecture rules conflict with general Angular advice.

SKILL.md

2.7 KB, 454 tokens by cl100k_base, as published. Nobody here has run it

Angular Enterprise Architecture

Use this skill for Angular architecture decisions before applying general Angular implementation guidance. If this skill conflicts with angular-developer, this skill wins for architecture, dependency direction, folder placement, and lazy/eager boundaries.

Always Apply

  • Keep the eager app minimal: main.ts, app.*, core/, and layout/.
  • Implement every user-facing business flow as a lazy feature/<feature-name>/, even if the app currently has only one feature.
  • Keep sibling lazy features isolated. A feature must not import implementation from another feature.
  • Preserve a one-way dependency graph: more specific blocks may depend on simpler/shared blocks, never the reverse.
  • Share by extracting one level up, not by importing sideways.
  • Do not use feature-shared. A normal parent feature folder covers sharing between its own lazy sub-features.
  • Implement automatic validation with the latest project-compatible eslint-plugin-boundaries flat config. Use the references in this skill as the starting point, then verify against the current JS Boundaries docs/package version before finalizing.

Reference Routing

  • For architecture and folder structure, including what to implement in each folder, read placement.md.
  • For preserving the one-way dependency graph, lazy loading, and lazy feature isolation while sharing code, read extract-one-level-up.md.
  • For standardized architecture building block definitions, folder structure, and dependency rules, read building-blocks.md.
  • For adding a new architecture building block and matching ESLint boundary type, read adding-building-blocks.md.
  • For implementing or adapting ESLint enforcement, read eslint.config.boundaries.js. The provided config targets an Angular CLI polyrepo with multiple apps and libraries under projects/; for a single-app workspace it can be simplified and many basePattern entries can be omitted.

Terminology: use architecture building block for the concept, folder for its implementation location, and ESLint boundary type for the matching eslint-plugin-boundaries enforcement entry.

What ships with it: 5 files

20.5 KB alongside SKILL.md, 1 of them executable

references/

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.