dokitolisted
Install: claude install-skill sgasser/dokito
# Dokito
Dokito files are the complete model interface. Read and edit `dokito.yaml`,
`context.md`, Projects, Resources, and Tasks directly. Use the CLI only for
machine-local registration and registry discovery, global read-only Project
and Task listings, scope resolution, ULID generation, validation, and the
Web runtime.
## Start work
1. Run `dokito context --json`.
2. Read `data.context`. Use `data.areaRoot`, `data.manifestPath`,
`data.contextPath`, `data.projects.path`, `data.resources.path`, and
`data.tasks.path` as the authoritative local paths.
3. Read `dokito.yaml` directly. Discover model files with `rg --files` inside
only the returned collection paths, and use `rg` for content search.
4. Load only the files relevant to the request. Do not assume that every
Project, Resource, or Task belongs in agent context.
Stay in the resolved Area unless the user explicitly requests broader work.
If scope resolution fails, do not conclude that no Areas exist and do not
propose creating or registering an Area yet. Follow the discovery workflow
below. Canonical checkout paths are machine-local Repository entries beneath
their Area registration; never add them to `dokito.yaml`. When an entry is
absent, that Repository has no local checkout until registration records its
verified sibling or the machine-local path is configured.
## Discover Areas and work from unscoped work
An agent runtime workspace, home directory, or orchestration Repository does
not need to belon