Generic solo TUI architecture/spec skill. Use this skill whenever the user asks an agent to act as a warden, professional code/architecture advisor, root-cause investigator, AI-friendly spec author, product test pilot, prompt translator, or lightweight coordinator for another TUI, SDK, memory seat, or coding agent. Also use it for concise task relay, Cartooner/product testing, issue investigation, and implementation-ready briefs. Do not use it for canonical project memory, planner fan-out, queue ownership, or thick seat protocol execution.
L3 project-memory hub for patrol, KB maintenance, queue/state tracking, faithful dispatch of operator/warden briefs, and E2E verification. Use when handling operator requests, context queries, decisions, deliveries, queue-drained receipts, or review/latest integration. Do not use for code, review, product-intent rewriting, direct specialist work, or seat lifecycle.
Federated memory oracle: synthesizes facts from ~/.agents/memory KB and preserves operator/warden brief intent during project-memory handoffs. Use when remembered facts, project-history synthesis, cross-seat evidence, queue-state context, or closeout recall are needed. Do not use for implementation, direct specialist work, or guessed facts.
Workflow author and dispatch orchestrator for ClawSeat tasks that need routing across specialist seats. Use when memory provides a brief, when workflow.md must be authored, when assigning owners, fan-out, liveness checks, SWALLOW fallback, or delivery consumption is required. Also use when coordinating review and next-step notifications. Covers workflow decomposition, schema validation, dispatch receipts, and planner summaries. Do NOT use for code implementation, independent review verdicts, visual QA, or project memory authority.
Multi-seat harness: bootstrap roster, start seats, dispatch tasks, complete handoffs with durable ACKs, provision frontstage heartbeat, render CLI operator console for a project profile.
Installer playbook for bootstrapping ClawSeat projects from the repository install flow. Use when the user asks to install ClawSeat, initialize a project, understand install.sh flags, recover an install, or follow docs/INSTALL.md setup steps. Also use when validating installer prerequisites or CLI-first onboarding. Covers install command discovery, environment assumptions, and resume guidance. Do NOT use for post-install task dispatch, normal /cs re-entry, code implementation, or modifying machine profiles without the install procedure.
Memory-driven project-group designer for ClawSeat v3 multi-team projects. Use when the first project memory needs to analyze a repo, recommend a module/layer-based team topology, write reviewable config proposals, or design an autonomous quality-docs testing group. For applying approved roster changes after initial design, pair with clawseat-roster-admin.
Implementation seat for ClawSeat workflow steps assigned by planner. Use when planner dispatches a brief, when you receive a [DISPATCH:] notification, or when fixing bugs, adding features, writing tests, refactoring code, or editing scripts and docs. Also use when implementing schema changes, templates, installers, or configuration from an in-flight workflow. Covers artifact authoring, local validation, and DELIVERY.md handoff with Docs Consulted (`N/A — <reason>` unless external SDK/API/CLI docs used). Do NOT use for code review, visual QA, scheduled patrol sweeps, operator intake, or memory authority decisions.