Quick Tour

This page follows one workspace from empty to a published website. Each step is one or two commands; the links go to the full reference. It assumes Ritual is installed and you are in an empty folder.

1. Bring in Your Lists

Import a deck from Archidekt, Moxfield, or MTGGoldfish by its URL:

ritual import https://archidekt.com/decks/12345

Moxfield URLs need a Moxfield-approved User-Agent string; see Moxfield User-Agent Requirement.

Import a collection from another app’s CSV export. A short wizard asks which column holds the card name, set, collector number, and so on, and prints the equivalent command so you can repeat it without prompts:

ritual import binder.csv

Or start lists by hand with new and add-card. A workspace holds any number of decks, collections (cards you own, each with an exact printing), and wanted lists (cards you are looking for).

See import for text files, Arena/MTGO exports, and every CSV option, and import-account to import every deck on an Archidekt account at once.

2. Edit Them

ritual edit

The interactive editor lists your decks, collections, and wanted lists. Add cards with autocomplete over the card database, edit the cards already there, undo mistakes, and save when you are done. One-shot commands such as add-card, move and set-card do the same from scripts.

Prefer a browser? ritual admin starts the admin site on http://localhost:8080, with the same editors plus imports, syncs, history, and site builds.

3. Price Them

ritual price

price opens a browser of every list and its value, down to the card. Prices come from TCGplayer, Cardmarket, Card Kingdom, or Cardhoarder (MTGO tix); priceSources picks which stores you use. sell shows what Card Kingdom’s buylist would pay for your cards.

4. Look Back

Every change to a list is written to its .changes.md log. To read one:

ritual history --show "My Commander Deck"

history without --show opens an editor for compacting a noisy log. diff compares two lists.

5. Sync with Archidekt

Sign in once:

ritual login archidekt

Pull changes made to your decks on Archidekt into the local files:

ritual deck-sync pull

Pull your Archidekt collection into your collection lists:

ritual collection-sync pull

A collection-sync push goes the other way and makes your whole Archidekt collection match your local collection lists, removals included. Preview it with --dry-run first, and use --only additions to send new cards without deleting anything.

deck-sync works per deck; collection-sync treats all your collection lists as one Archidekt collection.

6. Build Your Site

ritual serve --build

This builds the public site into dist/ and serves it at http://localhost:3000. Visitors can browse and filter your lists, look at each card, see prices, plan a trade, and send you edits as a file. The live demo is a site built this way.

dist/ is plain static files, so any web host works. To publish with GitHub Pages, keep the workspace in a GitHub repository and run:

ritual init-site

init-site asks a few questions and writes a GitHub Actions workflow that builds the site and deploys it to GitHub Pages when you push.

7. Hand It to an Assistant

ritual skills install   # teach a coding agent the ritual CLI
ritual mcp              # or expose your lists to an MCP client

Skills are instructions a coding agent such as Claude Code loads when a task matches. The MCP server gives MCP clients tools to read and edit your lists, with the same checks and change history as the admin site.

Where Next

The guides walk one job end to end: publish your site, sync with Archidekt, manage a collection, trade and sell, use Ritual with AI agents, and take edits from your public site.