Governs how the OpenBot browser app reads and writes server data — every request goes through client in app/src/lib/client.ts, every read is a queryOptions factory in app/src/lib/ /queries.ts, every write is a mutationOptions factory in app/src/lib/ /mutations.ts, and components consume them through…
The default layout for every OpenBot configuration screen — PageShell and its prose/wide widths, PageSection and PageRows, Item row composition, the settings-row pattern where a summary and a chevron open a dialog, and the size and variant vocabulary. This is what a new screen looks like unless an instruction says…
Use for communication between long-lived CodexLoom Agents: discovering domain owners, deciding when to contact another Agent, sending requests or notifications, replying to an agentmessage, checking queued delivery, and closing a request without a reply. Trigger whenever an Agent receives an agentmessage envelope or…
Send and resolve governed external messages through CodexLoom. Use whenever an Agent receives an external Inbox message from Feishu/Lark, Slack, Parall, or another Connector; must reply, explicitly decline, or defer an external Inbox item; needs to publish proactively to an authorized Conversation Membership; sends…
Configure and verify CodexLoom external platform integrations with the loom CLI. Use when inspecting or changing Connections, Agent Addresses, DM access, group/channel Conversation Memberships, trigger and reply policies, allow/block rules, trust domains, or Inbox/Outbox delivery for Feishu/Lark, Slack, Parall, and…
Governance behavior for AI agents governed by DashClaw. Teaches the governance protocol: when to call guard (risk thresholds), how to interpret decisions (allow/warn/block/requireapproval), when to record actions, how to wait for approvals, and session lifecycle management. Loads org-specific policies and capabilities…
The single command that gets a DashClaw change ON MAIN AND LIVE — it resolves everything blocking production, never defers, and never hands back a checklist. Lands feature branches on main (rebase, gate, merge, push so Vercel deploys), bumps the unified platform+SDK version, and realigns every description of the…
Save current project task progress to local task state file for cross-session continuity. Use when the user asks to save progress, uses an equivalent localized trigger phrase, the session is interrupted, or the user wants to resume work later. Writes to .claude/project-task-state.json so next session can load it via…
MetaKim executable governance dispatcher. It classifies the run, loads only needed references, preserves foundational capabilities and runtime-native abilities, routes owner + weapon + dependency + runtime + OS + verification, and closes only with evidence, intent acceptance, and writeback decision.
Reusable MetaKim file inventory classification flow. It helps separate durable sources, generated evidence, runtime mirrors, temporary state, and risky unknowns before cleanup or commit.
Anti-pattern detector and design rules for AI coding agents. Catches the specific mistakes AI makes when generating UI: gray text on color, nested cards, broken buttons, missing states. Use before shipping any frontend.
A controlled workflow for completing one coding task and submitting an envelope: a record of files read, files changed, patches, checks, and uncertainties. The envelope is an honest summary of the work, not just the code patch.
An independent, read-only check for a code-fix report. It verifies that each claimed check was run against the real contract, rather than trusting a summary or allowing the fixer to alter its own evidence.
Enforces development workflows, quality gates, coding standards, and release processes for the deterministic-agent-control-protocol project. Use when implementing features, fixing bugs, refactoring architecture, adding integrations, updating policies, writing tests, updating documentation, or preparing releases.
Use for implementation-style tasks that modify code, files, pages, or project structure. Inspect first, then output an approval-first execution contract with atomic slices, red lines, green tests, acceptance ladder, commit plan, target artifacts, and a white-box acceptance YAML bridge. Do not edit files.
Use only after a checklist or atomic slices have been explicitly approved. Execute approved slices under the current run mode, preserve atomic discipline, verify, archive one commit per slice, report git state, package evidence for review, and stop on blockers or replanning needs.
Parent policy layer for approval-first coding workflows under both plain and imperial registers. Defines non-negotiable constraints, not the primary auto-trigger workflow.