save-session

To save Salesforce session context, this Skill captures modified files, Apex progress, deployment status, and decisions into a structured markdown file stored in the global session directory. It enforces a dated naming convention and prompts you to confirm the saved contents before closing.

Persisting Claude Code session state involves writing current org context, blockers, and next steps to a dated markdown checkpoint file. This Skill automates that capture at session end, creating a structured handoff document under the canonical global store to prevent context loss.

Yes, while designed for Salesforce development sessions, the structured markdown capture mechanism supports any developer workflow needing to record modified files, decisions, and test status. It writes generic session sections that apply to any codebase requiring context persistence.

The session file naming format uses a YYYY-MM-DD-short-id convention stored under the global sessions directory. This Skill enforces short-id rules and limits each markdown file to roughly 500 lines to prevent collisions across projects and maintain readable checkpoints.

Resuming a Salesforce session from a checkpoint requires referencing the saved markdown file containing your exact next steps, blockers, and modified files. This Skill creates that structured handoff document, allowing a future session to read the file and resume exactly where you left off.

The session persistence file size is limited to roughly 500 lines, and the structure is strictly organized into predefined markdown sections for files, decisions, and next steps. This Skill enforces these constraints to ensure checkpoints remain concise and readable across context resets.