angular-clean-architecture

A development guide for organizing Angular application features into Clean Architecture layers: presentation, application, core, and infrastructure. Angular is a framework for building web applications, and lazy loading loads a feature only when it is needed.

In plain words
What is it for?
Use it when creating or changing modules under `src/app/modules/`, adding use cases, facades, stores, ports, adapters, lazy routes, cached state, or cross-module communication.
Why use it?
It provides a consistent way to keep business logic out of components and manage dependencies between features. It also covers shared navigation state and how modules register their own services.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/fmflurry/settings-opencode/angular-clean-architecture
Any agent
npx skills add fmflurry/settings-opencode --skill angular-clean-architecture
Clone the repo
git clone --depth 1 https://github.com/fmflurry/settings-opencode

Made for: Claude Code, Codex.

Per session 133 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,276 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00133 $0.03276
Opus 5 $0.00067 $0.01638
Sonnet 5 $0.00027 $0.00655
Haiku 4.5 $0.00013 $0.00328

Measured 2d ago against content hash f358894a71d8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

angular-clean-architecture scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/angular-clean-architecture/SKILL.md · 248 lines

How it starts

The opening of the file, as written. The whole thing — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Angular Clean Architecture — Module System

When To Activate

  • Creating a module under src/app/modules/
  • Adding a use case, facade, store, port, or adapter to an existing module
  • Wiring lazy routes + cached state
  • Replacing session proxies with self-contained module adapters
  • Creating standalone components that consume store state via facades
  • Refactoring a legacy/mixed module (NgModule/NgRx) toward Clean Architecture
  • Moving business logic out of components into facades/use-cases
  • Adding or updating cross-module communication via the context registry

Relationship to Other Skills

Concern Owner
Domain modeling (entity, VO, aggregate, invariants) [[angular-ddd]]
State/replay mechanics (Store API, channels, history) [[flurryx]]
Pre-merge enforcement / review checklist [[angular-cop]]
Module layout, DI, ports/adapters, lazy loading, caching wiring, facade, context registry, session-proxy replacement, naming this skill

Architecture Anchors (Verify Before Coding)

Anchor What to look for
Reference module At least one module under src/app/modules/ with full layer structure
flurryx store Store.for<Config>().build() in application/store/
syncToStore usage syncToStore(this.store, KEY) or syncToKeyedStore(...) in adapters/facades
Context registry contextProvidersFor() mapping cross-module providers

If anchors are missing: do NOT invent imports. Continue best-effort, report mismatch.

Architecture Overview

src/app/modules/{moduleName}/
├── presentation/            # list/ details/ create/ edit/ container pages, forms/, components/
├── application/
│   ├── facades/{moduleName}.facade.ts
│   ├── use-cases/{verb-noun}.use-case.ts
│   └── store/{moduleName}.store.ts      # flurryx Store.for<Config>().build()
├── core/                    # domain hexagon — ZERO infra/framework imports
│   ├── models/  ports/  rules/  mappers/  events/
├── infrastructure/
│   ├── adapters/{verb-noun}.adapter.ts
│   └── api/{endpoints/, request/, response/}
├── routes.ts                # lazy loadComponent + route-level providers
├── routes.constants.ts
├── {moduleName}-service.providers.ts    # SELF-REGISTRATION entrypoint
├── public-api.ts            # SYNC contract: models, ports, providers fn
└── integration-api.ts       # REACTIVE contract: exports store for cross-module mirroring

Read the full file on GitHub · 248 lines

Files

What ships with it

7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 248 lines · 0 tokens per session scan A f358894a71d8

Subscribe to this mod's changes

angular-clean-architecture is a skill published in the GitHub repository fmflurry/settings-opencode (172 stars, last pushed 20d ago), licensed MIT. It adds 133 tokens to every session and 3,276 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens