Phoenix Contexts & Domain Logic

•
62
•

Implements robust Phoenix context designs and domain-driven patterns while enforcing data ownership and Phoenix 1.8+ standards.

This skill equips Claude with specialized knowledge for architecting Elixir applications using Phoenix's bounded context pattern. It strictly enforces architectural 'Iron Laws' such as cross-context data ownership, mandatory %Scope{} structs for Phoenix 1.8+ authorization, and the use of Ecto.Multi for complex transactions. By providing expert guidance on when to split or merge contexts and how to handle cross-boundary communication, it ensures your application remains maintainable, scalable, and secure while keeping controllers thin and side effects out of schemas.

主な機能

01Ecto.Multi patterns for complex, atomic database transactions with side effects
02Automatic implementation of Phoenix 1.8+ Scope structs for authorization context
0362 GitHub stars
04Architectural 'Iron Law' enforcement for context data ownership and isolation
05Best-practice routing implementation using verified routes and secure pipelines
06Decision frameworks for splitting or merging domain contexts based on vocabulary

ユースケース

01Designing complex backend workflows that require atomic operations and PubSub broadcasting
02Refactoring large, monolithic Phoenix modules into maintainable bounded contexts
03Implementing secure multi-tenant data access using mandatory Scope parameters