Claude Skills by janpereira-dev

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.

Use this skill when an Angular 22 app still depends on Zone.js behavior or needs to make change-detection boundaries explicit.

Use this skill when an Angular 22 app wants to move toward zoneless operation or start from zoneless-friendly defaults.

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.

Use CSS :has() and :not(:has()) to adapt layout to child content without JavaScript, Angular bindings, or class toggles.

Build and review accessible frontend flows with semantic structure, keyboard operation, readable error feedback, and resilient content.

Design resilient CSS layouts with content-first sizing, progressive enhancement, readable reflow, and reduced-motion support.

Block release when semantics, keyboard, focus, contrast, target size, announcements, zoom, motion, or error recovery fail.

Detect trend-stacked and brandless interfaces, then require product-specific visual reasoning before design approval.

Build meaningful color roles and validate contrast, state distinction, focus visibility, and non-color cues.

Design reusable component contracts with semantic typed APIs, slots, defaults, events, extension points, and controlled complexity.

Define visual, behavioral, content, accessibility, and responsive contracts for every meaningful component state.

Route broad frontend design work through product, visual, usability, accessibility, responsive, state, and release gates.

Score product intent, visual identity, usability, components, accessibility, responsiveness, states, motion, and validation with blocker overrides.

Evolve reusable UI foundations through explicit tokens, component contracts, accessibility states, and evidence-based adoption decisions.

Define semantic, scalable design tokens and component token boundaries instead of hardcoded visual values.

Build disclosure and accordion patterns with details and summary first, progressive enhancement, and explicit accessibility fallbacks.

Define clear labels, validation, loading feedback, empty states, errors, confirmations, and recovery actions for product interfaces.

Use CSS-first motion for causality and feedback with reduced-motion support, bounded timing, browser fallbacks, and stable end states.

Choose native HTML semantics before custom widgets and define safe escalation to verified accessibility primitives.

Establish user task, content, constraints, brand direction, risk, and measurable outcomes before frontend design work.

Translate a frontend request into a focused user outcome, task flow, content hierarchy, edge states, and measurable acceptance criteria.

Design layout behavior around content, task priority, container size, zoom, and input modality rather than fixed screenshots.

Define story coverage, deterministic fixtures, screenshot baselines, interaction states, and approval rules for component changes.

Review user flows for clarity, decision cost, error prevention, recovery, feedback, consistency, and completion confidence.

Use semantic content order, typography, spacing, and grouping to make task priority and information relationships clear.

Define coherent visual rules for interface typography, imagery, shape, density, contrast, and motion from product intent.

Improve frontend loading and interaction performance through measured user-path evidence, resource prioritization, rendering analysis, and explicit budgets.

Gather evidence for critical frontend journeys across behavior, accessibility, visual regressions, network resilience, and performance without requiring a fixed test tool.

Reviews asynchronous JavaScript error handling in browser-facing code, focusing on user-facing failure states, safe fallbacks, retry behavior, and preserved error context.

Reviews asynchronous JavaScript error handling in browser-facing code for modern runtime baselines, focusing on user-facing failure states, safe fallbacks, retry behavior, and preserved error context.

Reviews asynchronous JavaScript error handling in Node.js 18+ projects, focusing on process-level failure behavior, file and network operations, and safe propagation from scripts and services.

Reviews asynchronous JavaScript error handling in Node.js 20+ projects, focusing on process-level failure behavior, modern runtime expectations, and safe propagation from scripts, services, and workers.

Reviews and refactors asynchronous JavaScript error handling so Promise-based code avoids swallowed failures, unhandled rejections, unclear fallback behavior, and weak failure contracts.

Assess opt-in JavaScript language, host, toolchain, library, and polyfill risks before adopting a feature or changing observable semantics.

Coordinates the learning and review path for JavaScript async error handling, modules, and pure functions so agents can choose the right primitive for the runtime and project maturity.

Reviews JavaScript module boundaries, exports, barrels, side effects, circular dependencies, and CommonJS versus ES Module interoperability.