Claude Skills by NoaiRox

Use when adding API integration to a module - creates types, contracts, adapter, and service layer.

Use when a module needs test coverage - creates tests for adapters, hooks/composables/stores, and components.

Use when integrating with an API endpoint and need TypeScript types, contracts, and adapters generated automatically.

Use when onboarding onto a module and need a quick summary of its structure, patterns, and key files.

Use when a component needs migration to the target architecture or framework version.

Use when a complete module needs migration to the target architecture - runs 6 phases with approval gates.

Use when checking if code follows ARCHITECTURE.md patterns - runs automated conformance checks.

Use when architecture violations were found and need automated fixing by priority.

Use when code changes need review before merge - validates architecture, types, security, and test coverage.

Use when adding a new UI component to an existing module - handles templates, props, and test scaffolding.

Use when creating a new feature module with all layers - service, adapter, types, state, components, and tests.

Use when adding API integration to a module - creates types, contracts, adapter, and service layer.

Use when a module needs test coverage - creates tests for adapters, composables, and components.

Use when integrating with an API endpoint and need TypeScript types, contracts, and adapters generated automatically.

Use when onboarding onto a module and need a quick summary of its structure, patterns, and key files.

Use when a component needs migration to the target architecture or framework version.

Use when a complete module needs migration to the target architecture - runs 6 phases with approval gates.

Use when checking if code follows ARCHITECTURE.md patterns - runs automated conformance checks.

Use when architecture violations were found and need automated fixing by priority.

Use when code changes need review before merge - validates architecture, types, security, and test coverage.

Use when adding a new UI component to an existing module - handles templates, props, and test scaffolding.

Use when adding server state management to a module - creates React Query hook with caching and error handling.

Use when creating a new feature module with all layers - service, adapter, types, state, components, and tests.

Use when adding API integration to a module - creates types, contracts, adapter, and service layer.

Use when a module needs test coverage - creates tests for adapters, hooks/composables/stores, and components.

Use when integrating with an API endpoint and need TypeScript types, contracts, and adapters generated automatically.

Use when onboarding onto a module and need a quick summary of its structure, patterns, and key files.

Use when a component needs migration to the target architecture or framework version.

Use when a complete module needs migration to the target architecture - runs 6 phases with approval gates.

Use when checking if code follows ARCHITECTURE.md patterns - runs automated conformance checks.

Use when architecture violations were found and need automated fixing by priority.

Use when code changes need review before merge - validates architecture, types, security, and test coverage.

Use when adding a new UI component to an existing module - handles templates, props, and test scaffolding.

Use when creating a new feature module with all layers - service, adapter, types, state, components, and tests.

Use when adding API integration to a module - creates types, contracts, adapter, and service layer.

Use when a module needs test coverage - creates tests for adapters, hooks/composables/stores, and components.

Use when integrating with an API endpoint and need TypeScript types, contracts, and adapters generated automatically.

Use when onboarding onto a module and need a quick summary of its structure, patterns, and key files.

Use when a component needs migration to the target architecture or framework version.

Use when a complete module needs migration to the target architecture - runs 6 phases with approval gates.

Use when checking if code follows ARCHITECTURE.md patterns - runs automated conformance checks.

Use when architecture violations were found and need automated fixing by priority.

Use when code changes need review before merge - validates architecture, types, security, and test coverage.

Use when adding a new UI component to an existing module - handles templates, props, and test scaffolding.

Use when adding server state management to a module - creates Vue Query composable with caching and error handling.

Use when creating a new feature module with all layers - service, adapter, types, state, components, and tests.

Use when adding API integration to a module - creates types, contracts, adapter, and service layer.

Use when a module needs test coverage - creates tests for adapters, hooks/composables/stores, and components.

Use when integrating with an API endpoint and need TypeScript types, contracts, and adapters generated automatically.

Use when onboarding onto a module and need a quick summary of its structure, patterns, and key files.