codex-fluent

# Codex Fluent Keep Codex feeling fast, light, and pleasant to use over months of heavy daily work. This skill is about **operational fluency** — the subjective experience of Codex staying responsive, starting quickly, and not forcing you to fight accumulated context and state. ## Core Philosophy - Fresh small state = speed and low mental load. - Old work must be preserved, but moved out of the active path. - **Handoffs are non-negotiable** before archiving anything you might still need. - Never delete. Archive with clear restore paths. ## When to Use This Skill - Codex feels laggy on startup or when switching sessions. - You have many long-running or old chats you rarely touch but don't want to lose. - Before big maintenance or after noticing session directory growth. - After a `codex-retrospective` session where Codex itself flagged repeated context bloat or "I keep having to re-explain the current state". ## Safety Rules (Hard) 1. **Inspect first, always.** The first invocation must be report-only. 2. **Handoff before archive.** For any active repo chat you might continue, a high-quality handoff document + reactivation prompt must exist before it is moved to archive. 3. **Backup before mutate.** All changes must be preceded by a timestamped backup. 4. **Archive, never delete.** Sessions, logs, and worktrees are moved to dedicated archive directories (`~/.codex/archived_sessions/`, `archived_worktrees/`, `archived_logs/`). 5. Codex must be closed (or you explicitly ...