elixir_rpc_load_balancer

Use when working with rpc_load_balancer for TODO

API wrapper patterns for the CheddarFlow project. TRIGGER when: writing or modifying API wrapper apps (apps with _api suffix), making HTTP requests to external services, working with SharedUtils.HTTP, Tesla middleware, or Finch pools. Also trigger when creating response structs with new!/1 constructors. DO NOT TRIGGER when: working with internal Elixir code that doesn't make external HTTP calls.

Authentication and authorization patterns for the CheddarFlow project. TRIGGER when: writing or modifying authentication, authorization, sessions, Auth0 integration, user access control, entitlements, or any plug/middleware that checks user identity or permissions. Also trigger when working with SessionCache, JWKS, or Ueberauth. DO NOT TRIGGER when: working with code that doesn't involve auth or user identity.

Oban background job patterns for the CheddarFlow project. TRIGGER when: writing or modifying Oban workers, background jobs, cron schedules, job queue configuration, or any code that enqueues or processes Oban jobs. Also trigger when working with Schemas.JobsRepo for job-related queries. DO NOT TRIGGER when: working with code that doesn't involve background job processing.

Caching patterns for the CheddarFlow project. TRIGGER when: writing or modifying caching code involving Redis, ETS, elixir_cache, Cachex, or any of the _cache apps. Also trigger when working with RedisLock, Cache.Redis, Cache.ETS, or cache sandbox testing. DO NOT TRIGGER when: working with code that doesn't involve caching layers.

Umbrella dependency management patterns for the CheddarFlow project. TRIGGER when: adding dependencies, creating new apps, modifying mix.exs files, working with CFX.MixHelpers, or changing the mix_helpers.exs file. Also trigger when adding tags like :root, :web, :http to app configurations. DO NOT TRIGGER when: working with code that doesn't involve dependency or project configuration.

Distributed cluster patterns for the CheddarFlow project. TRIGGER when: writing or modifying code involving cross-node communication, CFXRpc, libcluster, Phoenix.PubSub broadcasting, distributed Erlang, or node routing. Also trigger when working with SharedUtils.Cluster, CFXPubSub, or any code that needs to handle dev/test vs prod cluster differences. DO NOT TRIGGER when: working with single-node code that doesn't involve distribution.

Ecto schema, migration, and database patterns for the CheddarFlow project. TRIGGER when: writing or modifying Ecto schemas, changesets, migrations, database queries, context modules, or any code in the schemas app. Also trigger when creating new database tables, adding indexes, working with EctoShorts, QueryBuilder, TimescaleDB, or FactoryEx factories. DO NOT TRIGGER when: working with code that doesn't touch the database layer.

Elixir code patterns and conventions for the CheddarFlow project. TRIGGER when: writing or modifying ANY Elixir code in this project, including modules, functions, GenServers, supervisors, or any .ex/.exs file. This skill should ALWAYS be read first before any other skill when working with Elixir code. DO NOT TRIGGER when: only modifying non-Elixir files like Terraform, Ansible, Docker, or documentation.

GenStage pipeline patterns for the CheddarFlow project. TRIGGER when: writing or modifying GenStage pipelines, event processors, trade ingestion code, or any code in options_events_processor or dark_pool_events_processor apps. Also trigger when working with PipelineSupervisor, Producer/Consumer stages, or SSE ingestion. DO NOT TRIGGER when: working with code unrelated to event processing pipelines.

Feature flag patterns for the CheddarFlow project. TRIGGER when: writing or modifying feature flag code, FunWithFlags usage, CFXFeatureFlags calls, or conditional feature enablement. Also trigger when adding new flags to config or checking flag state. DO NOT TRIGGER when: working with code that doesn't involve feature flags.

Feed system patterns for the CheddarFlow project. TRIGGER when: writing or modifying feed server code, feed adapters, SharedFeedUtils, FeedServer, FeedSupervisor, or any real-time data streaming components. Also trigger when working with ETS-backed feed state, feed routing via CFXRpc, or Absinthe subscription resolvers that read feed data. DO NOT TRIGGER when: working with code unrelated to real-time data feeds.

GraphQL and Absinthe patterns for the CheddarFlow project. TRIGGER when: writing or modifying GraphQL schemas, types, queries, mutations, subscriptions, resolvers, or Absinthe middleware in the cfx_web app. Also trigger when working with Dataloader, Absinthe.Subscription, or any file under schema/, resolvers/, or types/ directories. DO NOT TRIGGER when: working with non-GraphQL code.

Deployment and infrastructure patterns for the CheddarFlow project. TRIGGER when: working with deployment, infrastructure, OpenTofu/Terraform, Ansible, CI/CD workflows, release configuration, AWS resources, or deploy_ex. Also trigger when modifying GitHub Actions workflows, Dockerfiles, or cloud-init templates. DO NOT TRIGGER when: working with application-level Elixir code that doesn't touch infrastructure.

Telemetry and metrics patterns for the CheddarFlow project. TRIGGER when: writing or modifying telemetry events, metrics definitions, CFXMetrics modules, or monitoring-related code. Also trigger when adding :telemetry.execute or :telemetry.span calls, or working with Prometheus/Grafana metric exports. DO NOT TRIGGER when: working with code that doesn't involve observability or metrics.

Phoenix framework patterns for the CheddarFlow project. TRIGGER when: writing or modifying Phoenix controllers, LiveView modules, templates, routes, plugs, components, layouts, or any code in the cfx_web app that touches the web layer. Also trigger when working with core_components.ex, router.ex, or endpoint.ex. DO NOT TRIGGER when: working with non-web Elixir code that doesn't involve Phoenix.

Testing patterns for the CheddarFlow project. TRIGGER when: writing or modifying tests, test support modules, test configuration, FactoryEx factories, or test helper functions. Also trigger when setting up HTTP sandboxing, database sandbox, or Oban test helpers. DO NOT TRIGGER when: writing production code that doesn't involve test infrastructure.