session-management

Context preservation across .NET coding sessions is managed by loading and persisting handoff files, memory rules, and evolving instincts. The skill reads `.claude/handoff.md` at session start and captures pending work or learned conventions at session end.

.NET solution detection for MCP tooling works by locating `.slnx` or `.sln` files in the repository. Once the correct solution file is detected, MCP tooling is automatically bootstrapped so it can be used from the first prompt.

Resuming pending tasks without handoff or memory files is supported through graceful degradation. The session start protocol avoids hard failure when expected files or solutions are absent, allowing work to continue safely.

Capturing learned conventions before ending a coding session is handled by the session end protocol. It records completed and pending work, updates `MEMORY.md` with new rules, evolves `.claude/instincts.md` confidence scores, and checks for uncommitted changes.

Session management for .NET requires either a `.slnx` or `.sln` solution file for bootstrapping MCP tooling. If neither solution file is present, the skill degrades gracefully rather than throwing a hard failure.

Context preservation at session end accounts for uncommitted changes by running explicit checks before wrapping up. The protocol summarizes pending work and flags uncommitted changes for user approval to prevent losing work-in-progress state.