Why use this skill with Claude?

It provides Claude with specific architectural constraints and best practices for Elixir, preventing common anti-patterns like bloated controllers or direct Repo calls in the UI layer.

What are Phoenix Contexts?

Phoenix contexts are dedicated modules that group related functionality, acting as an internal API for specific parts of your application and enforcing domain boundaries.

Does this skill support Phoenix 1.8?

Yes, it specifically enforces Phoenix 1.8+ patterns, including the mandatory use of the %Scope{} struct for authorization in context functions.

How does it handle data isolation?

It follows the 'Iron Law' that contexts must own their data, meaning one context never queries another's schema directly via the Repo module.

Can it help with Ecto transactions?

Absolutely. The skill provides patterns for using Ecto.Multi to handle complex transactions that include side effects like PubSub broadcasting.

Phoenix Contexts & Domain Logic

Name: Phoenix Contexts & Domain Logic
Author: oliver-kriska

byoliver-kriska

•

API Development

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.

Key Features

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

Use Cases

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

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add oliver-kriska/claude-elixir-phoenix phoenix-contexts

For use in Claude.ai and ChatGPT

Download Skill