Claude Skills by janpereira-dev

Use when an AI coding agent needs NgAutoPilot routing, version-aware Angular guidance, frontend quality gates, skill catalog maintenance, plugin bundle validation, or safe agent adapter installation.

Validate the Angular 22 hop after migration and before follow-up modernization. For Angular 22 projects and 21-to-22 upgrade planning.

Gate Angular 22 compiler, core, forms, HTTP, router, platform-server, and upgrade breaking changes. For Angular 22 projects and 21-to-22 upgrade planning.

Inventory Angular 21 project risks before changing dependencies. For Angular 22 projects and 21-to-22 upgrade planning.

Coordinate the bounded Angular 21 to 22 hop without mixing modernization into the dependency upgrade. For Angular 22 projects and 21-to-22 upgrade planning.

Detect and gate the Angular CLI builder path, including browser, browser-esbuild, application, and custom builders.

Gate Angular changes with the required Node.js, TypeScript, and RxJS compatibility matrix for the current target version.

Audit Angular peer dependencies and transitive blockers before applying an upgrade or refactor.

Index production-ready and experimental Angular 22 features and route them to concern-first skills. For Angular 22 projects and 21-to-22 upgrade planning.

Classify Angular 22 risks by domain, severity, validation need, and PR slicing recommendation. For Angular 22 projects and 21-to-22 upgrade planning.

Align Angular 22 recommendations with official roadmap status and avoid premature adoption of unfinished work. For Angular 22 projects and 21-to-22 upgrade planning.

Determines Angular compatibility across Node.js, TypeScript, RxJS, Angular CLI and browser support before planning or executing upgrade hops.

Detects Angular version constraints before recommending APIs such as Signals, signal inputs, standalone APIs, control flow, @defer, takeUntilDestroyed, resource, or httpResource.

Central index for Angular versioning, compatibility gates, hop planning, and routing to the correct upgrade or modernization skill.

Defines the main NgAutoPilot workflow for understanding a task, detecting project context, selecting the smallest skill, assessing risk, applying a minimal change, and validating the result.

Prevents incompatible recommendations by routing Angular, TypeScript, JavaScript, RxJS, Node, and tooling advice through detected project versions and supported feature gates.

Collects the minimum repository context needed before an agent changes Angular, TypeScript, JavaScript, testing, architecture, or quality code.

Classifies change risk before code edits and forces small, reversible implementation plans for refactors, architecture changes, migrations, dependencies, routing, build, state, and public APIs.

Selects the smallest useful NgAutoPilot skill based on user goal, affected area, detected stack, compatibility constraints, risk, and expected output.

Detects Angular, TypeScript, JavaScript, Node, RxJS, package manager, test runner, linting, and framework features from repository evidence before applying version-sensitive guidance.

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.

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.

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.

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.

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.

Use this skill when Angular 22 changes affect component creation, selector rules, host directives, or default component behavior.

Splits Angular components into container and presentational responsibilities when it improves data flow, reuse, testability, and UI boundaries.