elixir-architect

Codify Elixir architecture requirements into ADRs, guardrails, and handoff documents.

1|1|Updated Jan 3, 2026

Search Tags:#architecture #adr #handoff #elixir #otp #oban #ash-framework

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide helps senior Elixir/OTP practitioners design production-ready Phoenix applications by providing comprehensive architecture documentation, clear domain modeling with Ash Framework, and ready handoff materials for Director and Implementor AI collaboration.

Core Features & Use Cases

Phase-driven architecture planning including requirements gathering, ADRs, and guardrails.
Ash Framework-first domain modeling with multi-app structure and Oban integration guidance.
Handoff-ready artifacts: ADRs, documentation templates, and a repeatable directory layout for project bootstrap.
Strong emphasis on Dave Thomas style architecture over umbrella apps, with explicit separation of concerns.

Quick Start

Design a complete architecture documentation package for a new Elixir/Phoenix project, including ADRs, guardrails, handoff docs, and a ready-to-run directory layout.

Frequently Asked Questions about elixir-architect

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

FAQPage Schema

How do I document Elixir architecture requirements for a Phoenix project using Ash Framework?▼

Elixir architecture documentation captures domain modeling, data layers, and boundaries across the project lifecycle. It applies Ash Framework and Oban integration to produce ADRs, guardrails, and handoff materials for AI-driven implementation.

What is the Dave Thomas multi-app structure and when should I use it instead of umbrella apps?▼

The Dave Thomas structure enforces explicit separation of concerns across multiple applications. It replaces umbrella apps to provide clearer boundaries, producing a repeatable directory layout for project bootstrap.

How do I create ADRs and handoff materials for an Oban and Phoenix application?▼

Creating ADRs and handoff materials involves codifying end-to-end architecture requirements into structured documentation. It generates ready-to-run directory layouts and guardrails for a Director and Implementor AI pair.

Does this architecture planning approach work with Ash Framework and Oban for domain modeling?▼

Architecture planning applies Ash Framework-first domain modeling with Oban integration. It suits senior Elixir/OTP practitioners designing production-ready Phoenix applications.

What is the best way to bootstrap a production-ready Elixir system with ADRs and guardrails?▼

Bootstrapping a production-ready Elixir system uses phase-driven architecture planning. It captures requirements to produce ADRs, guardrails, and starter directories for direct implementation.

Can I use this for AI collaboration handoff in an Elixir project?▼

AI collaboration handoff produces structured architecture documents and templates. It delivers ready-to-run artifacts for a Director and Implementor AI pair.