Build skills

Regent's sites are built from Ash Template, and these are the guides its builders follow: what to reach for, the rules each part keeps, and how to check the work. They are written for coding agents, and people can read every one of them here.

• ash-stack: Choose an Ash workflow for cross-layer features or refactors.
• ash-backend: Design or simplify Ash resources, actions and domain interfaces.
• ash-data: Change AshPostgres schemas or diagnose SQL and concurrency behavior.
• ash-frontend: Build or refine AshPhoenix forms and LiveView interfaces.
• ash-security: Change or review Ash authorization, trusted scopes and field exposure.
• ash-testing: Design Ash regression tests or remove redundant test coupling.
• ash-webmcp: Use when making Ash sites agent-ready, or building WebMCP browser tools into an Ash/Phoenix site.
• animejs: Motion on Regent's Phoenix LiveView and Ash sites with Anime.js v4 (npm animejs) and the shared motion kit, written as TypeScript hook islands. Use for any animation, transition or motion work on a Regent site (entrances, presses, drawers, lists, counts, celebrations after an action) and whenever code uses animejs — animate, timelines, timers, stagger, easings and springs, splitText, SVG morph/draw/motion path, draggable, animatable, onScroll, auto layout, Scope, engine, utils, WAAPI or the three.js adapter — or a LiveView hook animates server-rendered DOM. Also for choosing between CSS, LiveView JS commands and Anime.js, and for motion that does not play.
• onchain-buttons: Buttons that make a person's wallet act on Regent's Phoenix LiveView and Ash sites — send a transaction (approve, stake, bid, buy, claim, settle, launch) or sign (x402 payment, typed data). Use when adding, changing, reviewing or debugging any wallet or on-chain button, its TypeScript hook, the chain switch, the wallet's answer, the server's check of the result, or the words shown for each outcome.
• chain-events: Watching a chain for contract events on Regent's Phoenix and Ash sites, saving each one to the database once, and showing the saved rows on LiveView pages as they arrive. Use when adding or changing an event watcher, its cursor, the tables it fills, how a reorg or disagreement is handled, how pages hear about new rows, the "catching up" notice, or chain reads the server makes at the latest block.

Start with ash-stack: it says which of the others a task needs. Each skill links to its own reference pages.

For agents

An agent can fetch every skill at once from the skills index, which lists each one as a single download with a fingerprint to check it against. The agent guide explains how.