docs: Add directory analysis navigation rules to CLI workflow guides

- Add explicit directory analysis rule to gemini-unified.md for cd navigation
- Add directory analysis rule to codex-unified.md with --cd flag option
- Improve clarity for users when analyzing specific directories

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

.claude/workflows/codex-unified.md

@@ -8,6 +8,7 @@ type: technical-guideline
 
 -   **Purpose**: An AI-powered CLI tool for automated codebase analysis, intelligent code generation, and autonomous development workflows.
 -   **Key Characteristic**: **No `--all-files` flag** - requires explicit `@` pattern references for file inclusion.
+-   **Directory Analysis Rule**: When user intends to analyze specific directory (cd XXX), use: `codex --cd XXX exec "@{**/*} prompt"` or `cd XXX && codex exec "@{**/*} prompt"`
 -   **Default Mode**: `--full-auto` autonomous development mode (RECOMMENDED for all tasks).
 -   **Primary Triggers**:
     -   When user needs automated code generation or refactoring.

.claude/workflows/gemini-unified.md

@@ -7,6 +7,7 @@ type: technical-guideline
 ### 🚀 Command Overview: `gemini`
 
 -   **Purpose**: A CLI tool for comprehensive codebase analysis, context gathering, and pattern detection across multiple files.
+-   **Directory Analysis Rule**: When user intends to analyze specific directory (cd XXX), always navigate first: `cd XXX && gemini --all-files -p "prompt"`
 -   **Primary Triggers**:
     -   When user intent is to "analyze", "get context", or "understand the codebase".
     -   When a task requires understanding relationships between multiple files.