cucumber-best-practices
Cucumber best practices, patterns, and anti-patterns
Cucumber best practices, patterns, and anti-patterns
Use when designing system architecture, making high-level technical decisions, or planning major system changes. Focuses on structure, patterns, and long-term strategy.
Use when erlang's concurrency model including lightweight processes, message passing, process links and monitors, error handling patterns, selective receive, and building massively concurrent systems on the BEAM VM.
Use when working with SIP messages, methods, call flows, and protocol fundamentals for VoIP applications.
Use when active Record patterns including models, associations, queries, validations, and callbacks.
Use when building reliable and scalable distributed systems.
Use when Java generics including type parameters, wildcards, and type bounds. Use when writing type-safe reusable code.
Use when oTP actor patterns in Gleam including processes, message passing, GenServer implementations, supervisors, fault tolerance, state management, and building concurrent, fault-tolerant applications on the Erlang VM.
Use when designing monorepo structure, organizing packages, or migrating to monorepo architecture with architectural patterns for managing dependencies and scalable workspace configurations.
Deploy meta-cognition and recursive systems thinking mode. Use when need to question the question, find root causes of root causes, or escape current system constraints.
Use when deciding between inheritance and composition in object-oriented design. Use when creating class hierarchies or composing objects from smaller components.
Identify how consciousness maintains, transforms, and operates itself. Use when diagnosing notion-reality engines, mind projection patterns, ego-sense dynamics, equanimity operations, or inquiry dissolution. Recognize operational patterns in consciousness evolution.
PRIORITY OVERRIDE protocol. Activates when trauma/crisis/vulnerability detected. Stops all frameworks, deploys presence-only mode. Always running in background.
Use when functional programming patterns in Scala including higher-order functions, immutability, pattern matching, algebraic data types, monads, for-comprehensions, and functional composition for building robust, type-safe applications.
Use when Go concurrency with goroutines, channels, and sync patterns. Use when writing concurrent Go code.
Use when C# async/await patterns including Task, ValueTask, async streams, and cancellation. Use when writing asynchronous C# code.
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 C# nullable reference types and value types for null safety, nullable annotations, and patterns for handling null values.
Use when protocol-oriented programming in Swift including protocol extensions, default implementations, protocol composition, associated types, and designing flexible, reusable abstractions that favor composition over inheritance.
Use when Effect core patterns including Effect<A, E, R> type, succeed, fail, sync, promise, and Effect.gen for composing effects. Use for basic Effect operations.
Use when designing GraphQL schemas with Absinthe. Covers type definitions, interfaces, unions, enums, and schema organization patterns.
Use when nestJS guards and interceptors for auth, logging, and transformation. Use when implementing cross-cutting concerns.
Use when implementing GraphQL resolvers with Absinthe. Covers resolver patterns, dataloader integration, batching, and error handling.