web-developer-persistent-context

Persistent context automatically saves your project decisions, file changes, and progress every 30 seconds, then restores your exact state when you resume in a new session. Start with `node index.js start-session "Project Name"` to begin tracking.

Yes. The Skill logs all decisions with rationale and file modifications with version history. Use search to locate past decisions or changes, then restore your exact context state from any prior session backup.

Separate persistent contexts isolate each project's decisions, file history, and progress. Create distinct sessions per project using `start-session`, then switch between them—each resumes with its own full state intact.

Automatic backups every 30 seconds ensure no work is lost. When you return, check status with `node index.js status` and restore your exact prior state, including all decisions and code changes made before closing.

Cross-session continuity restores context when you resume on the same machine. Multi-device support depends on your backup storage setup—the Skill provides CLI integration and versioned history for flexible recovery options.

Built-in search indexing lets you quickly locate past decisions by rationale, file changes by timestamp, or outputs by project. Query your session history to speed up work recovery without manual log review.