elixir-scribe

Organize Elixir projects into domain-resource-action folders for single-responsibility modules.

1|1|Updated Jan 3, 2026

Search Tags:#architecture #elixir #domain-driven #single-responsibility #folder-structure #manual-enforcement #nerves

Ready to run

npx skills add https://github.com/layeddie/ai-rules --skill elixir-scribe

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: elixir-scribe
Source: https://github.com/layeddie/ai-rules/tree/main/skills/elixir-scribe
Command: npx skills add https://github.com/layeddie/ai-rules --skill elixir-scribe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Elixir-Scribe approach provides a clear, explicit folder-based organization to enforce the Single Responsibility Principle, avoiding magic and DSLs in favor of manual discipline.

Core Features & Use Cases

Domain-first organization with explicit Domains/Resources/Actions
One action per module to improve maintainability and onboarding
Self-documenting folder structures that ease migration and onboarding, including Nerves embedded projects and non-Ash Elixir code

Quick Start

Create a domains/ folder under lib/YourApp and place each action in its own module file following the catalog/product structure.

Frequently Asked Questions about elixir-scribe

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce single responsibility principle in Elixir project folder structure?▼

To enforce single responsibility principle in Elixir, organize your lib directory into domain-resource-action folders with one action per module. This explicit structure relies on manual discipline rather than DSLs or magic.

What is the best way to organize non-Ash Elixir codebases by domain?▼

The best way to organize non-Ash Elixir codebases is using a domain-first folder structure. Grouping modules by domain, resource, and action creates a self-documenting architecture that improves onboarding without framework dependencies.

How do I structure an Elixir Nerves embedded project for better maintainability?▼

To structure an Elixir Nerves embedded project for maintainability, apply a domain-resource-action folder hierarchy under lib. Placing one action per module file creates a self-documenting layout that eases embedded project onboarding.

Does domain-driven folder structure work without Ash framework in Elixir?▼

Domain-driven folder structure works without Ash framework in Elixir by using explicit manual enforcement. You create domains and resources as physical folders, avoiding DSLs while maintaining a clear, self-documenting codebase architecture.

Why use manual folder enforcement instead of framework DSLs for Elixir architecture?▼

Manual folder enforcement avoids framework DSLs and magic in Elixir architecture by making code organization explicit. This self-documenting folder structure requires discipline but improves clarity, migration, and onboarding without locking you into a framework.

When should I not use a single action per module organization in Elixir?▼

You should not use single action per module organization if your team lacks the discipline for manual enforcement. This Elixir folder structure avoids framework automation, meaning clarity depends entirely on maintaining strict domain-resource-action boundaries.