ash-stack

Files (11)

• SKILL.md
• openai.yaml · agents/
• agent-readiness.md · references/
• docs-workflow.md · references/
• privy-reconciliation.md · references/
• project-profile.md · references/
• regent-integration.md · references/
• review-checklist.md · references/
• shared-contract.md · references/
• source-index.md · references/
• inventory.py · scripts/

SKILL.md (first lines)

# Ash Stack

Use the smallest relevant specialist. Product intent and repository authority come
from the current task; this pack supplies Ash-specific judgment, not a delivery ritual.

Before building or reviewing, run elixir-stack's design check: name the standard
tool (Ash, Ecto, Oban, Phoenix, OTP) for each moving part. Code that rebuilds one is
a defect, however correct it is.

## Shared changes: template first, Sean signs off, all sites at once (founder rule, 28 Oct 2026)

Regents, Patchbay, Keyfleet, Autolaunch and Techtree are five similar Ash sites. A change
more than one of them uses (design-system components and tokens, the shared Elixir
packages in `repos/elixir-utils`, and what `repos/ash-template` wires up for every site)
is built and tested in the library and ash-template first, signed off by Sean, then handed
to all five sites at once, each making its own version, and watched as each goes live.
regent-workflow's "Shared changes" section has the four steps and the rollout files.

Before building a feature in a site monorepo, **check whether ash-template already
implements it, use that implementation, and improve it there if it falls short.** Never
fork a second copy of a shared feature into one site; the ash-template chief owns the
template and the shared skills.

| Work | Reference |
| --- | --- |
| Resources, actions and domain interfaces | [ash-backend](../ash-backend/SKILL.md) |
| Forms, LiveView and presentation | [ash-frontend](../ash-frontend/SKILL.md) |
| Schema changes, SQL and concurrency | [ash-data](../ash-data/SKILL.md) |
| Policies, actors and data exposure | [ash-security](../ash-security/SKILL.md) |
| Regression design or test cleanup | [ash-testing](../ash-testing/SKILL.md) |
| Agent readiness, shared discovery metadata, and building or adopting WebMCP tools | [ash-webmcp](../ash-webmcp/SKILL.md) |
| One resource reacting to another's action: Ash signals, their listeners, and moving a site onto them | [ash-signals](../ash-signals/SKILL.md) |
| Background, retried or scheduled work, webhooks, polling, GenServers, PubSub, HTTP clients and shared Elixir libraries | [elixir-stack](../elixir-stack/SKILL.md) |

For uncertain APIs, use the app's actual Mix root, lockfile and installed dependency
usage rules. [Documentation lookup](references/docs-workflow.md) covers version
mismatches; the [inventory helper](scripts/inventory.py) optionally locates projects
without executing them. Before an edit, open the files the change touches, their callers
and the nearest existing example of the same pattern in the site, even when the request
names none of them; a whole-repository scan is not needed.

In Regent, [integration guidance](references/regent-integration.md) resolves shared
libraries, claims and wallet rules. For Privy bridge/session changes, use
[Privy reconciliation](references/privy-reconciliation.md). Consult the
[shared contract](references/shared-contract.md) only when a boundary is unclear.

From regents-ai/ash-template, MIT.

More from regents-ai/ash-template