strategic-compact

To preserve context during long Apex development sessions, use strategic manual compaction at logical boundaries like after org exploration or completing a feature to keep critical metadata and planning artifacts intact.

Context collapse happens during extended Salesforce Apex workflows because the session accumulates excessive metadata, requiring deliberate compaction at logical boundaries to prevent the loss of critical org context and planning artifacts.

Compact context in Apex development by applying the skill across org exploration, planning, implementation, and domain transitions, enforcing a PreToolUse hook with configurable thresholds to trigger deliberate manual compaction.

Yes, you can configure compact thresholds and reminder cadence for Salesforce session context management to balance productivity and context preservation during ongoing Apex development.

Yes, context compaction works across domain transitions like Apex to LWC by applying deliberate manual compaction at these boundaries to preserve critical org context and metadata.

The best way to manage context across multiple Salesforce development sessions is using strategic compaction to save and restore plan-state across sessions, ensuring continuity of planning artifacts and org metadata.