IA-Skills

Create distinctive, production-grade frontend interfaces with high design quality. Trigger: When the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

Node.js development principles and decision-making. Framework selection, async patterns, security, and architecture. Teaches thinking, not copying. Triggers: When the user asks to build a Node.js application, API, backend, or any server-side JavaScript project.

Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices. Trigger: When creating Node.js servers, REST APIs, GraphQL backends, or microservices architectures.

Optimize for search engine visibility and ranking. Use when asked to "improve SEO", "optimize for search", "fix meta tags", "add structured data", "sitemap optimization", or "search engine optimization". Trigger: when asked to "improve SEO", "optimize for search", "fix meta tags", "add structured data", "sitemap optimization", or "search engine optimization".

Provides comprehensive Tailwind CSS utility-first styling patterns including responsive design, layout utilities, flexbox, grid, spacing, typography, colors, and modern CSS best practices. Trigger: When styling components, building responsive layouts, implementing design systems, or optimizing CSS workflow.

Guide for styling with Tailwind CSS 4, including utility-first composition, `cn()` usage, theme variable handling, and project-safe class patterns. Trigger: Use when the task involves styling UI with Tailwind classes, composing conditional class names with `cn()`, working with Tailwind 4 theme variables, translating design/UI requirements into utility classes, or reviewing className usage to avoid invalid patterns such as wrapping theme variables with `var()` inside className-driven styling.

Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Trigger: When you need to implement complex type logic, create reusable type utilities, or ensure compile-time type safety in TypeScript projects.

Guide for building, validating, submitting, and debugging action-backed forms with AshPhoenix.Form in Phoenix and LiveView, including nested forms, parameter preparation, error transformation, and form lifecycle handling. Trigger: Use when the task mentions or contains `AshPhoenix.Form`, `for_create`, `for_update`, `for_read`, `for_destroy`, `validate`, `submit`, nested form operations like `add_form` or `remove_form`, or when working on Ash-backed form flows in LiveView/Phoenix and deciding how validation, submission, params, or errors should be handled.

Guide for exposing Ash resources through AshJsonApi, including domain and resource configuration, JSON:API route design, relationship endpoints, includes, pagination, filtering, sorting, router setup, and safe public API exposure. Trigger: Use when the task mentions or contains `AshJsonApi.Domain`, `AshJsonApi.Resource`, `json_api do`, JSON:API route definitions such as `get`, `index`, `post`, `patch`, `delete`, `related`, `relationship`, `post_to_relationship`, `patch_relationship`, `delete_from_relationship`, or when deciding how to expose Ash resources and relationships through a JSON:API-compliant public API.

Practical guide for working with Ash in Elixir applications. Trigger: Use when creating or modifying resources, domains, actions, relationships, queries, changesets, code interfaces, policies, calculations, aggregates, or when deciding if domain logic should live in Ash.

Guide for using Flutter AutoSizeText in a consistent, responsive, and maintainable way, including sizing constraints, scaling rules, AutoSizeGroup usage, Theme integration, and testing considerations. Trigger: Use when the task involves `AutoSizeText`, `AutoSizeGroup`, responsive text sizing, preventing text overflow in constrained layouts, adapting typography for long or translated strings, or reviewing whether auto-resizing text is being used correctly without abusing it for layout logic or global styling decisions.

Core catalog of 8 critical Elixir/Phoenix anti-patterns covering error handling, separation of concerns, Ecto queries, and testing. Trigger: During Elixir code review, refactoring sessions, or when writing Phoenix/Ecto code.

Guide for writing, reviewing, and improving tests in Elixir applications, including ExUnit, OTP processes, Ecto/database flows, Phoenix behavior, and dependency isolation strategies. Trigger: Use when the task involves creating or debugging tests, reviewing test quality, deciding between unit/integration/OTP tests, working with ExUnit, testing GenServers or supervised processes, mocking or isolating external dependencies, validating Ecto-backed behavior, or diagnosing flaky Elixir test cases.

Guide for using Flutter Riverpod 2.x in a consistent, maintainable, and testable way, including provider selection, UI consumption patterns, dependency composition, side-effect handling, lifecycle management, and testing strategy. Trigger: Use when the task involves `Provider`, `StateProvider`, `NotifierProvider`, `AsyncNotifierProvider`, `FutureProvider`, `StreamProvider`, `ProviderScope`, `WidgetRef`, `ref.watch`, `ref.read`, `ref.listen`, `AsyncValue`, provider overrides, or when deciding how state, dependencies, side effects, or controller logic should be modeled with Riverpod in Flutter.

Guide for using Flutter Secure Storage in a secure, testable, and maintainable way, including wrapper services, provider-based access, key management, session persistence, token lifecycle handling, and Riverpod integration. Trigger: Use when the task mentions or contains `FlutterSecureStorage`, secure local persistence of tokens or session data, wrapper storage services, provider-based storage access, key naming for sensitive values, logout/session cleanup, bootstrap or rehydration of auth state from secure storage, or when reviewing whether sensitive local storage is being used safely and outside the UI layer.

Guide for building Flutter forms with flutter_form_builder and form_builder_validators in a consistent, maintainable, and testable way, including FormBuilder structure, field selection, declarative validation, form state handling, and Riverpod-friendly architecture. Trigger: Use when the task mentions or contains `FormBuilder`, `FormBuilderState`, `FormBuilderTextField`, `FormBuilderDropdown`, `FormBuilderValidators`, `saveAndValidate`, `didChange`, a centralized `GlobalKey<FormBuilderState>`, or when designing, validating, submitting, resetting, or refactoring Flutter forms built with flutter_form_builder.

Guide for building, reviewing, and refactoring Phoenix LiveView code, including routes, live sessions, mounts, events, assigns, components, forms, streams, PubSub, and LiveView tests. Trigger: Use when the task mentions or contains `use ... :live_view`, `live_session`, `on_mount`, `mount/3`, `handle_event/3`, `handle_info/2`, `assign`, `stream`, function components, live components, LiveView forms, PubSub/Presence updates, or when deciding whether behavior belongs in a LiveView, component, context, or message-driven flow.

Guide for using Realm in Flutter as a consistent, testable, and maintainable persistence layer, including initialization, schema design, transactions, queries, migrations, sync considerations, error handling, and repository-based architecture. Trigger: Use when the task mentions or contains `Realm`, `Configuration.local`, Realm schemas/models, write transactions, migrations, query encapsulation, Realm providers or DI setup, live Realm objects, sync/session handling, or when deciding how local persistence, reactivity, and data-layer responsibilities should be modeled with Realm in a Flutter app.

Guide for spotting and avoiding common testing and TDD anti-patterns, especially around mock misuse, over-isolation, implementation-coupled assertions, and weak integration coverage. Trigger: Use when reviewing or writing tests for new development, bug fixes, or behavior changes, especially if the task involves mocks, test doubles, isolation strategy, integration coverage decisions, cleanup logic added for tests, or diagnosing brittle tests that pass without proving real behavior.

Practical guide for applying test-driven development to new development, bug fixes, and behavior changes. Trigger: Use when the task involves implementing a new behavior, fixing a bug, changing observable behavior, designing code from requirements, or deciding what test should be written first before production code. Also use when reviewing whether a change should follow a red-green-refactor workflow instead of coding first.

Guide for writing, generating, reviewing, and refactoring maintainable code using practical software design heuristics such as DRY, KISS, YAGNI, SOLID, separation of concerns, high cohesion, low coupling, fail fast, and clear naming without applying them dogmatically. Trigger: Use when the task involves creating new code, refactoring existing code, reviewing implementation quality, improving readability or maintainability, reducing duplication or coupling, choosing clearer abstractions, or deciding how to structure logic so the code stays simple, cohesive, and easy to evolve.

Angular core patterns: standalone components, signals, inject, control flow, zoneless. Trigger: When creating Angular components, using signals, or setting up zoneless.

Angular forms: Signal Forms (experimental) and Reactive Forms. Trigger: When working with forms, validation, or form state in Angular.

Angular performance: NgOptimizedImage, @defer, lazy loading, SSR. Trigger: When optimizing Angular app performance, images, or lazy loading.

Jest testing patterns and best practices for modern TypeScript/JavaScript projects. Trigger: Writing, refactoring, or reviewing Jest unit/integration tests (matchers, async, mocks, timers, snapshots, setup/teardown).

Playwright E2E testing patterns. Trigger: When writing Playwright E2E tests (Page Object Model, selectors, MCP exploration workflow).

TypeScript strict patterns and best practices. Trigger: When implementing or refactoring TypeScript in .ts/.tsx (types, interfaces, generics, const maps, type guards, removing any, tightening unknown).