arcane

How to store, organize, retrieve, and collect information in the arcane-vault knowledge base. Covers the 4-layer progressive-disclosure structure, canonical vocabulary, entity authoring rules, the GLOSSARY-based term resolution protocol, and the daily vault-builder collection process. Apply when reading from or writing to the vault, when documenting architecture or decisions, and when running the daily vault collection agent.

How work flows through the Arcane repos — when to file an epic vs a standalone issue vs a multi-epic initiative, how epic branches and long-lived initiative dev branches work, how sub-PRs route, who merges what, when main is touched, and how agents log decisions for the founder's final review. Apply when filing any issue or PR, when deciding which branch to target, when reviewing/merging, and when implementing a sub-issue of an epic or initiative.

Cloud worker that picks up a single GitHub issue and turns it into a single pull request. Triggered by GitHub Actions on `issues:[labeled]` with `claude-ready`, gated by either sender = `martinjms` (standalone path) OR the issue carrying `claude-working` (orchestrator dispatch path). Use this skill whenever the worker workflow fires; it's invoked via `/arcane-worker` from `.github/workflows/claude-issue.yml`. Determines mode automatically — fresh PR creation, continuing an existing PR with new retry guidance, or posting a BLOCKER on the parent epic PR — based on issue body and current PR state.

Central dispatcher and reviewer for an Arcane epic's sub-issues and sub-PRs. Triggered by GitHub Actions on labeled/unlabeled issues, opened/closed/synchronized PRs, submitted PR reviews, and created issue comments — but only when the event touches an active epic (epic issue or epic PR carries `orchestration-active`, OR sub-issue carries `claude-working`/`action-required`, OR PR base is an `epic/*` branch). Reads GitHub state, identifies which of 11 situations matches, executes that situation's playbook via `gh` CLI, and exits. **One decision per invocation. Stateless across invocations.** Use this skill whenever the orchestrator workflow fires; the workflow YAML invokes it via `/arcane-orchestrator`. Standalone (non-epic) issues are explicitly out of scope — those go through arcane-worker directly.

Format GitHub comments, issues, and pull requests for fast readability. Use for any text destined for GitHub — issue bodies, PR descriptions, review comments, status updates. Covers markdown style, posting safety, and linking rules. For the structure of issue/PR content (sections, length, level of detail), use `arcane-issue-pr-writing`.

Structure GitHub issues, PRs, epics, and review comments for fast comprehension. Covers what sections to include, how long they should be, what level of detail goes where, and how to use collapsibles to keep top sections short. For markdown style and posting mechanics, use `arcane-github-formatting`.