Define and implement Elixir protocols within struct modules using Protoss.
npx skills add https://github.com/ityonemo/pepper --skill protocols-ityonemo
Please help me install this Agent Skill. Skill: protocols Source: https://github.com/ityonemo/pepper/tree/main/.claude/skills/protocols Command: npx skills add https://github.com/ityonemo/pepper --skill protocols-ityonemo
This Skill simplifies Elixir protocol definitions and implementations by allowing them to be colocated within the struct module, reducing boilerplate and improving discoverability.
Use the protocols skill to define a new Elixir protocol named MyProtocol with a required function process/1.
High-intent search queries and answers about installing and using this skill.
You can colocate Elixir protocol definitions and implementations within struct modules using the Protoss library. This Skill provides the syntax to define protocols and implement them directly in the module, reducing boilerplate and improving code discoverability.
The best way to organize Elixir protocol implementations is to colocate them with your struct definitions. This approach keeps the data structure and its associated protocol behavior together for easier management and understanding.
Yes, you need the Protoss library to enable in-module protocol definition and implementation syntax. It provides the necessary functionality to facilitate colocated Elixir protocol definitions directly within your struct modules.
Yes, you can define a new Elixir protocol and implement it directly within the struct module. This allows you to write protocol implementations alongside struct definitions, enhancing code organization and maintainability.
Colocating Elixir protocol implementations with struct definitions solves the problem of boilerplate and poor discoverability. By keeping both the struct and its protocol behavior together, code management and understanding become significantly easier.
The metadata does not specify technical limitations for colocating Elixir protocols with the Protoss library. It is primarily recommended for enhancing code organization and reducing boilerplate when defining new data structures and their associated protocol behaviors.
mkreymanRun Mix-based quality checks for Elixir/Phoenix projects.
leaderiopModel Effect-style dependency injection environments with compile-time validation.
trueraCreate and curate ground-truth evaluation datasets for TruLens.
ccashwellDefine modular Solidity interfaces for standardizing external contract APIs.
