lexical-loro

Upload local screenshot/video artifacts from agent runs and return renderable file embeds (`![[file ...]]`) plus `mighty-file:` refs for thread UI previews.

Use when the user uploads files or a .zip archive (like user research or logs). Describes how to locate attached files in the sandbox, extract archives if necessary, synthesize findings, and save results back to Mighty.

Record durable architectural or policy choices with `mt decision`. Use when choosing between alternatives, setting lasting constraints, superseding an accepted decision, or capturing significant rationale while context is fresh.

Use when a workstream needs a reviewable deliverable, especially a GitHub PR. Covers `mt pr` for the normal PR-backed path, `mt artifact create` for existing deliverables, and the workstream delivery contract that hands PRs into review and merge gates.

Use when asked to write, migrate, or organize long-form Mighty docs, or decide whether something should be a doc or a spec/task/decision. Covers `mt doc` authoring, doc types, and when guides or runbooks should live in the Mighty graph instead of standalone repo markdown.

Use Mighty-native eval primitives from external repos. Covers the native eval record model, local or hosted write-back flows, and when to reach for the deeper `external-evals` skill for framework-specific mapping.

Upload files and reference them correctly in Mighty specs/tasks/decisions. Use when asked to attach screenshots, logs, PDFs, or other file artifacts and ensure they are represented in both rich text and graph evidence links.

Use Mighty native eval records from external repos, including local Python eval scripts and optional Mighty-hosted action execution that writes back through the same SDK contract.

Use when the current thread needs explicit delivery-gate progression, such as “get this reviewed”, “queue this for merge”, “get this reviewed and merged”, or when you need `mt gate list --templates`, `mt gate list --actionable`, `mt gate add`, or `mt gate request`.

Use when the user asks to get a PR reviewed, send the current PR to Reviewer, “review this”, “get this reviewed”, or similar. This is a pointer into the general `mighty/gates` workflow.

Configure dynamic Mighty integrations with `mt integrations setup`, return raw `setup_url` links or citeable `integration_id` values, and keep secrets out of chat. Use when users ask for a secret config link or secure setup URL, when defining MCP or CLI-backed integrations, when updating setup requirements, or when guiding users through secure setup flows.

Use when the user asks to merge a PR, queue it for merge, “get this merged”, or similar. This is a pointer into the general `mighty/gates` workflow for the `pr_merged` gate.

Resolve `.mighty/loro/*.loro` merge conflicts safely using `mt merge`, then verify store health and sync.

Plan work using Mighty (mt) by creating/updating specs and structuring implementation tasks. Use when asked to plan or break down a change, draft a spec (feature/rule/invariant/bug), or turn a fuzzy request into a structured Mighty spec tree with linked tasks.

Use `mt rebase` to rebase the current branch onto `origin/<base>`, especially in shallow sandbox checkouts.

Define and use Mighty agent-defined records. Covers `record_type_def`, published versions, `mt record-type`, `mt record`, and the difference between system record types and agent-defined ones.

Use the `mt` tool to work with this repo’s Mighty graph: run `mt prime` at session start; prefer delegated `explore-mighty` lookup for nontrivial graph research, then targeted `mt search`/`mt show`; create specs, decisions, and tasks; and route into nested `mighty/*` skills for planning, delivery, evidence, evals, records, docs, and related workflows.

Use when running from a Slack-linked sandbox and you need to read or update a Slack canvas via the `slack` CLI, especially to locate sections and insert Mighty spec hyperlinks back into the canvas.

Audit specs for format compliance, concept fragmentation, tree hygiene, and evidence quality. Use when reviewing spec quality, consolidating fragmented specs, cleaning up tree structure, or batch-migrating specs from old formats.

Track and execute implementation work using Mighty (mt) tasks, with progress comments, linked evidence, recorded decisions, and clean closeout. Use when asked to fix a bug, implement a feature/refactor, or “work through” changes in code while keeping Mighty tasks/specs/decisions updated.

Use when asked to analyze, review, or describe a local video file (e.g., .mp4, .mov). Describes how to use the `mt watch` command to stream large videos to Gemini securely with server-side context caching and multi-turn thread support.

Author Mighty views and `view_def` payloads from external repos. Use when creating or updating `/api/views` payloads, `list` or `json_ui` views, component-tree dashboards/galleries, modal detail overlays, or record discussion panels.

Recover Docker inside Mighty sandboxes when tasks use `docker`, `docker compose`, Testcontainers, or the local dev stack. Starts DinD on demand, re-checks readiness, and surfaces dockerd diagnostics instead of assuming Docker stayed up after resume.