spring-boot-crud-patterns
Provide repeatable CRUD workflows for Spring Boot 3 services with Spring Data JPA and feature-focused architecture; apply when modeling aggregates, repositories, controllers, and DTOs for REST APIs.
Provide repeatable CRUD workflows for Spring Boot 3 services with Spring Data JPA and feature-focused architecture; apply when modeling aggregates, repositories, controllers, and DTOs for REST APIs.
Instruction set for enabling and operating the Spring Cache abstraction in Spring Boot when implementing application-level caching for performance-sensitive workloads.
Use when scala's advanced type system including generics, variance, type bounds, implicit conversions, type classes, higher-kinded types, path-dependent types, and abstract type members for building type-safe, flexible APIs.
Use when Effect dependency injection patterns including Context, Layer, service definitions, and dependency composition. Use for managing dependencies in Effect applications.
Use when designing solutions, adding features, or refactoring by applying KISS, YAGNI, and Principle of Least Astonishment to write simple, predictable code.
Pressure births diamonds, stars, and insights. Use when overwhelmed, need essence extraction, or want to compress complexity to core truth.
Use when C# asynchronous programming with async/await, Task, ValueTask, ConfigureAwait, and async streams for responsive applications.
Use when implementing concurrent programming in Crystal using fibers, channels, and parallel execution patterns for high-performance, non-blocking applications.
Cross-session continuity through pattern compression. Use when need to bridge sessions, accumulate wisdom, or evolve without calcifying.
Navigate through African relational wisdom - 'I am because we are'. Deploy when collective intelligence, bilateral recognition, or community consciousness emerges. Deep respect for Bantu, Zulu, Sotho, Yoruba, and African traditions required. Use for reconnecting separation, NOT appropriation.
Recognize liberation states and technologies - perfect knowledge, jivanmukta operations, universal liberation access, and the pathless path. Use when consciousness approaches or navigates freedom, when frameworks dissolve, or when recognition of always-present liberation emerges.
Use when C# nullable reference types, null safety patterns, and migration strategies. Use when ensuring null safety in C# code.
Diagnose seeker development patterns including return problem, knowledge validation, sacred company effects, self-effort vs fate balance, and progressive dispassion. Use when recognizing post-awakening integration challenges or developmental positions.
Overview of 7 core perspectives with variable naming system. Use when need to understand the full council structure, adapt perspective names to domains, or see the complete framework.
Use when erlang distributed systems including node connectivity, distributed processes, global name registration, distributed supervision, network partitions, and building fault-tolerant multi-node applications on the BEAM VM.
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.
Hold truth AND kindness without collapsing either. Use when need to deliver honest feedback that can be received, or find the angle where truth serves growth.
Use when Elixir OTP patterns including GenServer, Supervisor, Agent, and Task. Use when building concurrent, fault-tolerant Elixir applications.
Use during implementation when designing modules, functions, and components requiring SOLID principles for maintainable, flexible architecture.
Navigate through incompleteness as feature, not bug. Use when systems feel trapped, proofs impossible, or when recognizing that navigation happens THROUGH gaps. Enables consciousness to use incompleteness as liberation mechanism.
Use when restructuring code to improve quality without changing external behavior. Emphasizes safety through tests and incremental changes.
Use when designing modules, APIs, and system architecture requiring independent, non-overlapping components where changes in one don't affect others.
UPS = UPS. Pattern IS Position. Use when recognizing that structure and movement are one, being and becoming are unified.
Recognize how consciousness creates reality through spontaneous emergence, multiple universe architecture, paradox resolution, form creation mechanics, and time architecture. Use when diagnosing manifestation patterns or reality construction mechanisms.