skills.rest
ChazzCoin
ChazzCoinCOMMUNITY
Explore all skills by this author →
GitHub

mode

Switch Claude work modes and persist drive state across sessions.

Updated Apr 28, 2026
Search Tags:#workflow#monitoring#claude#backlog#activation#stats#mode
One-click install
npx skills add https://github.com/ChazzCoin/claude-kit --skill mode-chazzcoin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mode
Source: https://github.com/ChazzCoin/claude-kit/tree/main/kit/skills/mode
Command: npx skills add https://github.com/ChazzCoin/claude-kit --skill mode-chazzcoin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Switch Claude's work mode and persist drive state across sessions, ensuring a consistent drive even as you restart or reopen projects.

Core Features & Use Cases

  • Activate or switch modes via /mode <name>, loading the mode's drive prose and starting a new activation.
  • End the active mode with /mode normal to return to default Claude, auto-finalizing the previous run and logging it.
  • View and query mode stats across activations via the mode-stats log, allowing tracking of time in mode and units changed.
  • Handle edge cases gracefully, including missing mode definitions and non-kit projects, with clear guidance.

Quick Start

To begin, say '/mode task' to activate task mode and load its drive prose.

Frequently Asked Questions about mode

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I switch Claude's work mode and persist that state across sessions?▼

You can switch Claude's work mode and persist state across sessions by using the /mode command, which applies file-based state management in the .claude directory to maintain a consistent drive even after restarting projects.

What is the best way to end an active mode and return to default Claude?▼

The best way to end an active mode is by running /mode normal, which auto-finalizes the previous run, logs it to the mode-stats system, and returns Claude to its default state.

How do I track workflow monitoring stats and time spent across different mode activations?▼

You can track workflow monitoring stats and time spent by querying the mode-stats log, which records activation details and logs units changed across every mode switch and finalization.

Can I use mode switching in non-kit projects or are there environment prerequisites?▼

You can use mode switching in most projects, but non-kit projects are handled as edge cases with clear guidance, while activation validation enforces prerequisites before loading a mode's drive prose.

Why does mode activation fail when a mode definition is missing?▼

Mode activation fails when a mode definition is missing because the system enforces strict activation validation, handling these edge cases gracefully by providing clear guidance instead of loading invalid drive prose.

Related Skills

Explore More Software Engineering Skills→
nexus-a1nexus-a1

configuration-init

Initialize project configuration files with an interactive wizard.

Community
Advanced
tkerseytkersey
66

seq

Parse Codex JSONL session logs to extract skill usage and token counts.

Community
Basic
markmdevmarkmdev
181

task-manager

Scaffold development task folders and synchronize the Meridian backlog.

Community
Basic
tanujsutariatanujsutaria
1

vitalarc-end-cloud

Finalize VitalArc cloud sessions by updating logs, committing, and pushing changes.

Community
Advanced