context-discovery

# Context Discovery ## When to Use Use this skill **before and during implementation** when: - Starting work on an unfamiliar module or feature - The task involves multiple files or systems - You need to understand existing patterns before coding - Previous decisions or discussions may be relevant - You want to avoid duplicating existing functionality ## What It Does Leverages available MCP tools to proactively discover context about the codebase, existing patterns, decisions, and related work. Instead of relying solely on grep/read cycles, it uses purpose-built discovery tools. ## Discovery Workflow ### Step 1: File Discovery Find the relevant files using `fff`: ``` fff auth # Find auth-related files fff "*order*" # Find order-related files by pattern fff config # Find config files ``` Scan the results to identify the module structure. `fff` returns frecency-ranked results — the files you access most appear first. ### Step 2: Pattern Discovery via `sem` Once you know the relevant files, use `sem` to understand the code's history and structure: ``` sem blame path/to/file.ts # See who changed each line and when sem diff main..HEAD -- path/ # See what changed in this area sem summary path/to/ # Get a summary of the module ``` `sem` provides entity-level diffs (function-level, not just file-level), making it easier to understand what actually changed. ### Step 3: Historical Context...