TheBushidoCollective/han - Page 6

bun-bundler

Use when bundling JavaScript/TypeScript code with Bun's fast bundler. Covers building for different targets, tree-shaking, code splitting, and optimization strategies.

bun-package-manager

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

bun-runtime

Use when working with Bun's runtime APIs including file I/O, HTTP servers, and native APIs. Covers modern JavaScript/TypeScript execution in Bun's fast runtime environment.

bun-sqlite

Use when working with SQLite databases in Bun. Covers Bun's built-in SQLite driver, database operations, prepared statements, and transactions with high performance.

bun-testing

Use when writing tests with Bun's built-in test runner. Covers test organization, assertions, mocking, and snapshot testing using Bun's fast test infrastructure.

cocoapods-podspec-fundamentals

Use when creating or modifying CocoaPods podspec files. Covers required attributes, file patterns, dependencies, and platform specifications for iOS, macOS, tvOS, watchOS, and visionOS projects.

cocoapods-privacy-manifests

Use when implementing iOS 17+ privacy manifests for CocoaPods libraries. Covers PrivacyInfo.xcprivacy file creation, required reasons API declarations, and proper resource bundle integration for App Store compliance.

cocoapods-publishing-workflow

Use when publishing CocoaPods libraries to CocoaPods Trunk. Covers pod trunk registration, podspec validation, version management, and publishing best practices for successful library distribution.

cocoapods-subspecs-organization

Use when organizing complex CocoaPods libraries into subspecs. Covers modular architecture, dependency management between subspecs, and default subspecs patterns for better code organization and optional features.

cocoapods-test-specs

Use when adding automated tests to CocoaPods libraries using test specs. Covers test spec configuration, app host requirements, and testing patterns that integrate with pod lib lint validation.

cucumber-best-practices

Cucumber best practices, patterns, and anti-patterns

cucumber-fundamentals

Core Cucumber concepts, Gherkin syntax, and feature file structure

cucumber-step-definitions

Writing effective step definitions and organizing test code

cypress-advanced

Use when advanced Cypress features including custom commands, plugins, and network stubbing.

cypress-ci-cd

Use when cypress CI/CD integration including parallelization, test recording, and media capture.

cypress-fundamentals

Use when cypress fundamentals including commands, assertions, fixtures, and E2E testing patterns.

docker-compose-basics

Use when defining and running multi-container Docker applications with Docker Compose YAML configuration.

docker-compose-networking

Use when configuring networks and service communication in Docker Compose including bridge networks, overlay networks, service discovery, and inter-service communication.

docker-compose-production

Use when deploying Docker Compose applications to production including security hardening, resource management, health checks, logging, monitoring, and high-availability patterns.

gitlab-ci-artifacts-caching

Use when configuring artifacts for inter-job data passing or caching for faster builds. Covers cache strategies and artifact management.

gitlab-ci-best-practices

Use when optimizing GitLab CI/CD pipelines for performance, reliability, or maintainability. Covers pipeline optimization and organizational patterns.

gitlab-ci-job-configuration

Use when defining GitLab CI jobs, configuring scripts, setting up environments, or managing job dependencies. Covers job structure and execution options.

gitlab-ci-pipeline-configuration

Use when configuring GitLab CI/CD pipelines, defining stages, or setting up workflow rules. Covers pipeline structure, stage ordering, and execution flow.

gitlab-ci-variables-secrets

Use when configuring GitLab CI/CD variables, managing secrets, or integrating with external secret providers. Covers secure credential handling.

graphql-inspector-audit

Use when auditing GraphQL operations for complexity metrics, depth analysis, directive usage, or query performance concerns.

graphql-inspector-ci

Use when setting up GraphQL Inspector in CI/CD pipelines, GitHub Actions, or GitLab CI for automated schema validation.

graphql-inspector-diff

Use when detecting breaking changes between GraphQL schema versions, comparing schemas across branches, or validating schema migrations.

graphql-inspector-validate

Use when validating GraphQL operations/documents against a schema, checking query depth, complexity, or fragment usage.

graphql-performance

Use when optimizing GraphQL API performance with query complexity analysis, batching, caching strategies, depth limiting, monitoring, and database optimization.

graphql-resolvers

Use when implementing GraphQL resolvers with resolver functions, context management, DataLoader batching, error handling, authentication, and testing strategies.

graphql-schema-design

Use when designing GraphQL schemas with type system, SDL patterns, field design, pagination, directives, and versioning strategies for maintainable and scalable APIs.

helm-charts

Use when understanding and creating Helm charts for packaging and deploying Kubernetes applications.

helm-templates

Use when working with Helm templates and template functions for generating Kubernetes manifests dynamically.

helm-values

Use when managing Helm values files and configuration overrides for customizing Kubernetes deployments.

jest-advanced

Use when advanced Jest features including custom matchers, parameterized tests with test.each, coverage configuration, and performance optimization.

jest-configuration

Use when jest configuration, setup files, module resolution, and project organization for optimal testing environments.

jest-testing-patterns

Use when jest testing patterns including unit tests, mocks, spies, snapshots, and assertion techniques for comprehensive test coverage.

junit-extensions

Use when jUnit extensions including custom extensions, rules, and conditional test execution.

junit-fundamentals

Use when jUnit fundamentals including annotations, assertions, and test lifecycle for Java testing.

junit-parameterized

Use when jUnit parameterized tests with various value sources and test factories.