BobbieBarker

ADRs — Development skill for Claude Code

Development community

Your coding agent knows Elixir syntax.

How to install ADRs

This entry records only its repository, not the path inside it, so there is no exact command to give. Open BobbieBarker/adrs and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What ADRs does

Your coding agent knows Elixir syntax. These are the mechanism-level rules it gets wrong. 42 ADRs on OTP, conventions, Ecto, and the official anti-patterns, each with a Wrong example, a Correct example, and the BEAM reason behind the difference. Drops into Cursor and Claude Code.

Alternatives in Development

  • Cashclaw — An autonomous agent that takes work, does work, gets paid, and gets better at it 973 ★
  • Agent Skills Discovery RFC — A mechanism for discovering Agent Skills using the .well-known URI path prefix as specified in RFC 8615 for di 337 ★
  • Obsidian ADR — Generate a decision record when the vault structure changes — the vault knows why it knows what it does 277 ★

README

adrs

Architecture Decision Records, packaged as agent context. ADRs contain independently citable Rules with Correct/Wrong/Why examples, or a complete narrative decision whose sections need to be read together. Written for engineers and shaped for LLMs to consume: the format reads cleanly as a reference and drops into Cursor, Claude Code, Aider, and custom retrieval-based agents so the guidance loads automatically when you write or review code.

The rules are grouped into domains. Each domain is a self-contained set with its own pre-rendered bundles under `dist//`; adopt one or several.

Domains

Domain Covers ADRs
`software-design` Language-agnostic module boundaries, information hiding, cohesion, coupling, and interface costs 1
`elixir-otp` OTP, GenServer, supervision, BEAM scheduling, interprocess data, message routing, stateful-process testing 13
`elixir-conventions` Structural dispatch, runtime algorithm selection, pipeline composition, structs, validation-primitive selection, with chains, streaming, effect compensation, structured errors 9
`elixir-ecto` Transaction boundaries and the commit contract 1
`elixir-resilience` Calls to external services under failure: upstream rate limits, shared backpressure, coordinated recovery 1
`elixir-code-anti-patterns` The official Elixir code anti-patterns 10
`elixir-design-anti-patterns` The official Elixir design anti-patterns 6
`elixir-macro-anti-patterns` The official Elixir meta-programming anti-patterns 5

software-design

How to organize responsibilities so a change can remain local: identify the knowledge a module owns, preserve its invariants, and compare the benefit of a boundary with the unde