持續整合/部署

Use when defining and configuring Mise tasks in mise.toml. Covers task definitions, dependencies, file tasks, and parallel execution.

Use when designing solutions, adding features, or refactoring by applying KISS, YAGNI, and Principle of Least Astonishment to write simple, predictable code.

Use when managing development tool versions with Mise. Covers installing tools, version pinning, and replacing language-specific version managers.

Use when integrating Dialyzer into development workflows and CI/CD pipelines for Erlang/Elixir projects.

Use when testing GitHub Actions workflows locally with act. Covers act CLI usage, Docker configuration, debugging workflows, and troubleshooting common issues when running workflows on your local machine.

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 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 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 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 managing Sentry releases, uploading source maps, or tracking deployments. Covers release health and commit association.