Claude Skills by janpereira-dev

Audits and designs Angular shared UI/component libraries in Nx monorepos to keep reusable UI contracts free of feature, domain, data-access, store, router, and backend concerns.

Reviews and refactors Angular services so each service has one bounded responsibility such as API access, state ownership, mapping, validation, permissions, or feature orchestration.

Reviews Angular component testing patterns for Angular 17+ projects, focusing on modern template syntax awareness, stable component contracts, and contract-focused tests.

Designs and reviews Angular component testing patterns for enterprise apps, focusing on template interaction, inputs and outputs, host testing, harnesses, and boundary-focused assertions.

Route Angular testing work to Vitest, Jest, or Karma based on the current project and migration goals.

Replace TestBed.get with TestBed.inject in Angular tests. Use when older tests still rely on TestBed.get and need a small, controlled modernization step.

Use this skill when Angular 22 changes affect test reliability, async expectations, or compile-time behavior in the suite.

Validate Angular user journeys with evidence across behavior, keyboard access, automated accessibility signals, and stable visual checks when repository capabilities allow.

Write or review Angular tests in existing Jest projects, with narrow typed mocks, deterministic async behavior, and assertions that catch regressions.

Designs and reviews end-to-end validation for Angular micro-frontends in Nx monorepos, covering shell startup, remote loading, cross-remote flows, fallback behavior, and release confidence.

Uses read-only NgAutoPilot MCP tools to inspect catalog skills, content signals, packs, adapters, subagents, stack metadata, Angular compatibility, upgrade hops, and repository consistency. Use when a task needs deterministic NgAutoPilot repository evidence.

Evaluates and designs design systems shared across Angular micro-frontends in Nx monorepos, focusing on reusable tokens, component contracts, accessibility, and visual consistency across remotes.

Evaluates and designs Angular micro-frontends architectures in Nx monorepos, focusing on organizational fit, shell and remote boundaries, shared library contracts, runtime integration risks, and delivery governance.

Evaluates communication patterns between Angular micro-frontends in Nx monorepos, focusing on explicit contracts, low coupling, shared state limits, and safe cross-remote event flow.

Reviews shared dependency policy for Angular micro-frontends in Nx monorepos, focusing on singleton control, version alignment, bundle duplication risk, and shared library boundaries.

Designs fallback and rollback behavior for Angular micro-frontends in Nx monorepos, focusing on remote load failure, safe degradation, retry flow, and release rollback readiness.

Reviews observability contracts for Angular micro-frontends in Nx monorepos, focusing on logging, metrics, tracing, error boundaries, and runtime failure visibility.

Reviews ownership, permissions, and role-based access control for Angular micro-frontends in Nx monorepos, focusing on team responsibility, route access, remote boundaries, and least-privilege policy.

Reviews release governance for Angular micro-frontends in Nx monorepos, focusing on ownership, versioning, deployment independence, compatibility checks, and coordinated rollout policy.

Audits Angular shell or container apps in micro-frontends architectures, focusing on routing, composition, error handling, cross-cutting concerns, and strict separation from domain logic.

Reviews version compatibility gates for Angular micro-frontends in Nx monorepos, focusing on shell and remote compatibility ranges, dependency version drift, and upgrade safety.

Evaluates Angular Module Federation and Native Federation runtime contracts in Nx monorepos, focusing on remote exposure, shared dependency policy, fallback behavior, and version compatibility.

Classify whether Angular micro-frontends are warranted and choose the simplest viable integration pattern before introducing shell and remote boundaries.

Control which libraries may be shared across Angular micro-frontends and prevent domain leakage through shared packages.

Design fallback UI, safe redirects, and rollback paths for failed Angular remote loading or incompatible deploys.

Define a thin Angular shell contract that handles routing, composition, fallback UX, and cross-cutting concerns without owning domain logic.

Gate Angular shell and remote version drift so incompatible combinations are blocked before runtime exposure.

Designs and reviews end-to-end validation for Angular micro-frontends in Nx monorepos, covering shell startup, remote loading, cross-remote flows, fallback behavior, and release confidence.

Use official Angular Agent Skills as reference material without copying them blindly or replacing NgAutoPilot routing. For Angular 22 projects and 21-to-22 upgrade planning.

Use AI tutor workflows to teach Angular concepts without allowing unsafe code or secret exposure. For Angular 22 projects and 21-to-22 upgrade planning.

Integrate Angular MCP agent workflows without vendor lock-in or hidden local assumptions. For Angular 22 projects and 21-to-22 upgrade planning.

Use devserver build logs as an agent feedback loop while keeping validation deterministic. For Angular 22 projects and 21-to-22 upgrade planning.

Design WebMCP tool exposure with narrow capabilities, validation, permissions, and auditability. For Angular 22 projects and 21-to-22 upgrade planning.

Designs Angular enterprise onboarding paths that ramp developers through project conventions, architecture boundaries, testing discipline, and version-aware delivery expectations.

Coordinates the enterprise learning and review path for Angular forms, signals, and testing so teams can adopt the right primitive at the right version and maturity level.

Assesses Angular enterprise training readiness by mapping current team capability, version awareness, architecture gaps, testing maturity, and safe follow-up skill routing.

Designs version-aware Angular training paths for enterprise teams using a continuous business case study, architecture checkpoints, testing discipline, and practical validation outputs.

Orchestrates senior Angular architecture review by selecting focused patterns for container/presentational components, facades, state boundaries, service responsibility, and reactive contracts.

Builds Angular training matrices that map framework version features, compatibility risks, and learning priorities to enterprise team capabilities and delivery constraints.

Adopt Angular control flow syntax in bounded post-upgrade modernization slices to replace structural directive boilerplate with `@if`, `@for`, and `@switch` without mixing the change into an Angular version hop.

Adopt Angular defer blocks and modern lazy loading in bounded post-upgrade modernization slices to improve render timing, route splitting, and loading behavior without mixing the change into an Angular version hop.

Adopt Angular directive composition in bounded slices after the app is stable, using it to reduce inheritance-heavy patterns and share behavior without mixing the change into upgrade work.

Introduces or reviews Angular facades that provide a focused feature API over data access, state, permissions, navigation, and orchestration.

Adopt Angular host directives in bounded post-upgrade modernization slices to share host behavior, reduce wrapper components, and replace inheritance-heavy patterns without mixing the change into an Angular version hop.

Enforces practical Angular architecture boundaries between UI, feature or application logic, state, services, data access, and core or platform concerns to prevent responsibility leaks and unsafe module or standalone organization.

Audits Nx monorepo tagging and dependency constraints for Angular bounded contexts so shared UI, shared domain, and shared data-access libraries remain explicitly separated and enforceable.

Audits and designs Angular shared data-access libraries in Nx monorepos to keep reusable persistence and transport layers free of feature UI, router, and app-specific orchestration concerns.

Audits and designs Angular shared domain libraries in Nx monorepos to keep reusable business concepts, entities, and policies isolated from UI, transport, and feature orchestration concerns.

Adopt Angular signals in bounded post-upgrade modernization slices to replace or complement local component state, derived state, and reactive glue without mixing the change into an Angular version hop.

Adopt Angular standalone components after an Angular upgrade when the app is stable on Ivy and the goal is architectural modernization rather than a version hop. Use when the project is ready to reduce NgModule usage incrementally or convert bounded feature areas without mixing the change into the upgrade itself.