Start building
Go from a plain-language practice idea to a real package or connector without learning the entire platform first.
You do not need the Chasing Mastery repository, a global CLI, or private host access to author an extension. Start by choosing whether you are defining meaning or observing an external source.
Package or connector?
| Your sentence begins with… | Build | Example |
|---|---|---|
| “One Attempt should…” | Package activity | score a timed puzzle rush |
| “The result should contain…” | Package activity | accuracy, duration, and streak |
| “The member should interact with…” | Package player | chess board, dart board, split controls |
| “The stream should show…” | Package overlay | target, pace, rank, current route |
| “When the game/device/tool emits…” | Station connector | AutoDarts throw, LiveSplit split, browser move |
| “Several modes together should…” | Experience Suite | complete Darts or Chess practice offering |
Most automatic experiences use both artifacts. Design them together, but keep them independently reviewed. The compatibility seam is an exact observation type, contract version, canonical payload schema, and schema digest.
Recommended path
Describe the experience to your coding agent
Choose Codex, ChatGPT, or Claude, install the single Chasing Mastery Author workflow, then ask it to build a package or connector. It will interview you about the Attempt boundary, Measurements, evidence, progression, presentation, and failure states before writing code.
Let the plugin scaffold a standalone project
The generated directory includes source, fixtures, the authoring brief, pinned toolchain archives, and project-local POSIX and Windows launchers. Everything needed to exercise the extension travels with the project.
Iterate in Workbench or Connector Lab
Workbench is the real package host for authoring. Connector Lab is the real zero-grant native harness. Neither is a screenshot mock or a separate simulation model.
Ask for ready
The local toolchain validates design metadata, executes fixtures, checks conformance, packs immutable bytes, and writes a review handoff. Failed proof does not produce a releasable package.
Before you write code
Read the five-minute mental model and choose the correct artifact. Those two pages prevent the most expensive architectural mistakes: putting scoring in a connector, giving an overlay authority, inventing an enclosing practice session, or making historical results incomparable through a later release.