jeffweiss/elixir-production

jeffweiss/elixir-production

Agent

Use when a problem needs novel algorithmic approaches, academic paper citations, or evaluation of cutting-edge data structures not covered in the algorithms skill.

jeffweiss/elixir-production

Agent

Use when actively analyzing a specific module or codebase for cognitive load, onboarding difficulty, or refactoring opportunities.

jeffweiss/elixir-production

Agent

Use when designing a distributed architecture, investigating a distributed bug (split-brain, state disagreement, partition recovery, data loss), evaluating consensus algorithm tradeoffs, or working with message brokers (Kafka, RabbitMQ), PubSub systems, event streaming, or message delivery guarantees (at-least-once…

jeffweiss/elixir-production

Agent

Use when a feature needs architectural design before implementation, including complexity analysis, test specification, and phased implementation strategy.

jeffweiss/elixir-production

Agent

Use when implementing Elixir code after a plan exists, or when writing new functions, modules, or features that need tests written first.

jeffweiss/elixir-production

Agent

Use when code changes need review against production standards, before committing, or when checking if implementation is production-ready.

jeffweiss/elixir-production

Agent

Use when actively profiling slow code, running benchmarks to compare implementations, or investigating a specific performance bottleneck with measurement tools.

jeffweiss/elixir-production

Agent

Use when building or debugging Phoenix LiveView features that need guided implementation, not just pattern lookup.

jeffweiss/elixir-production

Agent

Use when reviewing a GitHub pull request by number, or when validating a PR is ready to merge.

jeffweiss/elixir-production

Agent

Use when designing a test strategy for a feature, analyzing behavioral coverage gaps, or specifying which test cases to write with criticality ratings.