CI/CD

Use when managing test state and infrastructure with reusable Playwright fixtures and lifecycle hooks for efficient test setup and teardown.

Create efficient data pipelines with tf.data

Use when applying Behavior-Driven Development patterns including Given-When-Then structure, feature files, and acceptance criteria. Use when writing BDD-style tests and specifications.

Use when Effect dependency injection patterns including Context, Layer, service definitions, and dependency composition. Use for managing dependencies in Effect applications.

Use when building and deploying Expo apps with EAS Build. Covers build configuration, development builds, production builds, and app store submission.

Use when integrating Ameba into development workflows including CI/CD pipelines, pre-commit hooks, GitHub Actions, and automated code review processes.

Use during implementation when designing modules, functions, and components requiring SOLID principles for maintainable, flexible architecture.

Use when writing effective BDD scenarios including acceptance criteria, edge cases, and scenario organization. Use when defining behavior specifications.

Use when prettier integration with editors, pre-commit hooks, ESLint, and CI/CD pipelines.

Use when implementing Kubernetes security best practices including RBAC, pod security policies, and network policies.

Use when developing custom Checkstyle checks, filters, and plugin integrations for project-specific Java code standards.

Use when implementing Apollo caching strategies including cache policies, optimistic UI, cache updates, and normalization.

Use when oTP behaviors including gen_server for stateful processes, gen_statem for state machines, supervisors for fault tolerance, gen_event for event handling, and building robust, production-ready Erlang applications with proven patterns.

Use when analyzing and fixing Dialyzer warnings and type discrepancies in Erlang/Elixir code.

Use when writing SOPs that require precise requirement levels using RFC 2119 constraint keywords (MUST, SHOULD, MAY). Covers proper usage of requirement keywords for deterministic agent behavior.

Use when managing Sentry releases, uploading source maps, or tracking deployments. Covers release health and commit association.

Use when pylint CI integration including plugins, editor integration, and performance tuning.

Use when kotlin coroutines for structured concurrency including suspend functions, coroutine builders, Flow, channels, and patterns for building efficient asynchronous code with cancellation and exception handling.

Use when building or integrating native modules in React Native. Covers creating native modules, Turbo Modules, bridging native code, and accessing platform-specific APIs.

Use when managing dependencies with Bun's package manager. Covers installing packages, workspaces, lockfiles, and migrating from npm/yarn/pnpm to Bun.