Files
shancheas f2f0be111a chore: update .gitignore and improve coding standards documentation
- Added .cursor/sessions/* to .gitignore to prevent session files from being tracked.
- Enhanced coding standards in SKILL.md by adding semicolons to TypeScript examples for consistency.
- Improved formatting in continuous learning, detail layout, and other SKILL.md files for better readability.

These changes aim to streamline development processes and maintain code quality across the project.
2026-08-25 17:50:17 +07:00

2.0 KiB

name, description
name description
strategic-compact Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.

Strategic Compact Skill

Suggests manual /compact at strategic points in your workflow rather than relying on arbitrary auto-compaction.

Why Strategic Compaction?

Auto-compaction triggers at arbitrary points:

  • Often mid-task, losing important context
  • No awareness of logical task boundaries
  • Can interrupt complex multi-step operations

Strategic compaction at logical boundaries:

  • After exploration, before execution - Compact research context, keep implementation plan
  • After completing a milestone - Fresh start for next phase
  • Before major context shifts - Clear exploration context before different task

How It Works

The suggest-compact.sh script runs on PreToolUse (Edit/Write) and:

  1. Tracks tool calls - Counts tool invocations in session
  2. Threshold detection - Suggests at configurable threshold (default: 50 calls)
  3. Periodic reminders - Reminds every 25 calls after threshold

Hook Setup

Already wired in .cursor/hooks.json as an afterFileEdit command:

{
  "version": 1,
  "hooks": {
    "afterFileEdit": [
      {
        "command": "node .cursor/scripts/hooks/suggest-compact.js"
      }
    ]
  }
}

Configuration

Environment variables:

  • COMPACT_THRESHOLD - Tool calls before first suggestion (default: 50)

Best Practices

  1. Compact after planning - Once plan is finalized, compact to start fresh
  2. Compact after debugging - Clear error-resolution context before continuing
  3. Don't compact mid-implementation - Preserve context for related changes
  4. Read the suggestion - The hook tells you when, you decide if
  • The Longform Guide - Token optimization section
  • Memory persistence hooks - For state that survives compaction