메뉴
Govern changes to the JM Labs Claude Desktop workspace ecosystem. Use whenever a task touches bootstrap, refresh, sync, export, local overlays, repo-local skills or agents, `workspaces/tasks`, generated `tasklog.md`, task intake flows, or when you need to decide whether an artifact belongs in the core, the workspace instance, or ignored local state.
Operate the JM Labs local admin dashboard and its repair surface. Use whenever the task mentions `dashboard.html`, `admin-app`, `dashboard-doctor.sh`, `dashboard-repair.sh`, the local mini app server, task admin views, filesystem inspection, or safe MCP/config visibility.
Audit parity between the JM Labs core contracts and the live Claude Desktop or Codex environment. Use whenever MCPs, plugins, connectors, local overlays, NotebookLM, Tessl, admin dashboard health, task orchestration scripts, or readiness claims are involved, especially before declaring the workspace healthy.
Curate durable `rag-memory-*` files for JM Labs tasks. Use whenever an input, attachment, ephemeral note, conversation snippet, or admin repair step must be preserved so the workspace can recover context even if the original artifact disappears.
Govern the JM Labs persistent task filesystem and intake workflow. Use whenever the task mentions `workspaces/tasks`, `tasklog.md`, `rag-memory-*`, task intake, task close, task resume, ambiguous inputs, session-state orchestration, or the rule that every new work input must be recoverable from disk.
| name | workspace-governor |
| description | Govern changes to the JM Labs Claude Desktop workspace ecosystem. Use whenever a task touches bootstrap, refresh, sync, export, local overlays, repo-local skills or agents, `workspaces/tasks`, generated `tasklog.md`, task intake flows, or when you need to decide whether an artifact belongs in the core, the workspace instance, or ignored local state. |
Use this skill to keep the JM Labs workspace system coherent while it evolves.
references/placement-rules.md./Users/deonto/jm-claude-desktop-workspace-core/profiles/capabilities/capability-manifest.json./Users/deonto/jm-claude-desktop-workspace-core/contracts/shared-sync-allowlist.json./Users/deonto/jm-claude-desktop-workspace-core/CLAUDE.md for the task orchestration protocol.Classify every proposed artifact into exactly one destination:
core: reusable runtime, contracts, assets, skills, agents, tests, portable docs.workspace: instance-owned docs, operator workflow logs, local operation wrappers.ignored local state: auth, overlays, workspaces/tasks/**, generated tasklog.md, active workspaces, generated reports, local dashboard snapshots.If an artifact seems to belong in two places, the default answer is that the reusable part belongs in the core and the instance-specific part belongs in the workspace.
When asked for analysis or a recommendation, use this structure:
Decision: <core | workspace | ignored-local-state>
Why: <one short paragraph>
Required changes: <files or scripts to update>
Verification: <commands or checks>
workspaces/tasks/** or generated tasklog.md as portable or syncable content.