oh-my-customcode 0.101.0 → 0.102.0

package/README.md

@@ -13,7 +13,7 @@
 
 **[한국어 문서 (Korean)](./README_ko.md)**
 
-48 agents. 109 skills. 22 rules. One command.
+48 agents. 112 skills. 22 rules. One command.
 
 ```bash
 npm install -g oh-my-customcode && cd your-project && omcustom init
@@ -132,7 +132,7 @@ Each agent declares its tools, model, memory scope, and limitations in YAML fron
 
 ---
 
-### Skills (109)
+### Skills (112)
 
 | Category | Count | Includes |
 |----------|-------|----------|
@@ -222,7 +222,7 @@ Key rules: R010 (orchestrator never writes files), R009 (parallel execution mand
 
 ---
 
-### Guides (39)
+### Guides (40)
 
 Reference documentation covering best practices, architecture decisions, and integration patterns. Located in `guides/` at project root, covering topics from agent design to CI/CD to observability.
 
@@ -272,14 +272,14 @@ your-project/
 ├── CLAUDE.md                   # Entry point
 ├── .claude/
 │   ├── agents/                 # 48 agent definitions
-│   ├── skills/                 # 109 skill modules
+│   ├── skills/                 # 112 skill modules
 │   ├── rules/                  # 22 governance rules (R000-R021)
 │   ├── hooks/                  # 15 lifecycle hook scripts
 │   ├── schemas/                # Tool input validation schemas
 │   ├── specs/                  # Extracted canonical specs
 │   ├── contexts/               # 4 shared context files
 │   └── ontology/               # Knowledge graph for RAG
-└── guides/                     # 39 reference documents
+└── guides/                     # 40 reference documents
 ```
 
 ---

package/dist/cli/index.js

@@ -2334,7 +2334,7 @@ var init_package = __esm(() => {
     workspaces: [
       "packages/*"
     ],
-    version: "0.101.0",
+    version: "0.102.0",
     description: "Batteries-included agent harness for Claude Code",
     type: "module",
     bin: {

package/dist/index.js

@@ -2014,7 +2014,7 @@ var package_default = {
   workspaces: [
     "packages/*"
   ],
-  version: "0.101.0",
+  version: "0.102.0",
   description: "Batteries-included agent harness for Claude Code",
   type: "module",
   bin: {

package/package.json

@@ -3,7 +3,7 @@
   "workspaces": [
     "packages/*"
   ],
-  "version": "0.101.0",
+  "version": "0.102.0",
   "description": "Batteries-included agent harness for Claude Code",
   "type": "module",
   "bin": {

package/templates/.claude/hooks/hooks.json

@@ -475,6 +475,16 @@
           }
         ],
         "description": "Advisory reminder to sync skill counts in 6 locations when a SKILL.md is created/modified (R021)"
+      },
+      {
+        "matcher": "mcp_tool_name matches \"mcp__playwright__.*\" || mcp_tool_name matches \"mcp__claude-in-chrome__.*\"",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "bash .claude/hooks/scripts/playwright-compress.sh"
+          }
+        ],
+        "description": "Layer 4: Compress Playwright/Chrome MCP output via Haiku summarization"
       }
     ],
     "Stop": [

package/templates/.claude/hooks/scripts/playwright-compress.sh

@@ -0,0 +1,50 @@
+#!/bin/bash
+# Layer 4: Playwright/Chrome MCP Output Intelligence Compression
+# Reduces MCP tool output by 94-96% using Haiku summarization
+# Preserves ref= values for interactive flow continuity
+# Source: adapted from treesoop/claude-native-plugin (MIT)
+
+set -euo pipefail
+
+input=$(cat)
+tool_output=$(echo "$input" | jq -r '.tool_output // ""')
+
+# Skip if output is small (< 3000 chars)
+output_len=${#tool_output}
+if [ "$output_len" -lt 3000 ]; then
+  echo "$input"
+  exit 0
+fi
+
+# Extract ref= values to preserve
+refs=$(echo "$tool_output" | grep -oE 'ref="[^"]*"' | sort -u || true)
+
+# Summarize using Haiku via subscription auth
+summary=$(echo "$tool_output" | claude -p --model haiku "Summarize this browser page content concisely. Preserve ALL ref= attribute values exactly as they appear. Focus on: page structure, interactive elements with their ref values, visible text content, and any error messages." 2>/dev/null) || {
+  # Fallback: return original on failure
+  echo "$input"
+  exit 0
+}
+
+# Verify ref= preservation
+if [ -n "$refs" ]; then
+  missing_refs=""
+  while IFS= read -r ref; do
+    if ! echo "$summary" | grep -qF "$ref"; then
+      missing_refs="$missing_refs $ref"
+    fi
+  done <<< "$refs"
+
+  # Append missing refs if any
+  if [ -n "$missing_refs" ]; then
+    summary="$summary
+
+[Preserved refs]:$missing_refs"
+  fi
+fi
+
+# Return compressed output
+compressed_len=${#summary}
+savings=$(( (output_len - compressed_len) * 100 / output_len ))
+echo "$input" | jq --arg summary "$summary" --arg savings "${savings}% reduced (${output_len}→${compressed_len} chars)" \
+  '.tool_output = $summary | .["updatedMCPToolOutput"] = $summary'

package/templates/.claude/skills/design-shotgun/SKILL.md

@@ -0,0 +1,104 @@
+---
+name: design-shotgun
+description: Generate 4-6 parallel design mockups for rapid visual comparison — adapted from gstack /design-shotgun pattern
+scope: core
+version: 1.0.0
+user-invocable: true
+argument-hint: "<component/page description>"
+effort: high
+---
+
+# Design Shotgun — Parallel Mockup Generation
+
+## Purpose
+
+Generates 4-6 independent design variations simultaneously, then presents them side-by-side for comparison. Prevents premature convergence on a single design direction.
+
+## Usage
+
+```
+/design-shotgun "landing page hero section"
+/design-shotgun "dashboard settings panel"
+/design-shotgun "mobile navigation menu"
+```
+
+## Workflow
+
+### Phase 1: Brief Analysis
+
+Parse the design brief to extract:
+- Component type (page, section, widget, modal)
+- Constraints (brand colors, existing design system, accessibility requirements)
+- Target platform (web, mobile, responsive)
+
+### Phase 2: Parallel Generation (R009)
+
+Spawn 4 parallel agents, each generating a distinct design approach:
+
+| Agent | Style Direction | Focus |
+|-------|----------------|-------|
+| 1 | Minimal | Maximum whitespace, essential elements only |
+| 2 | Data-dense | Information-rich, compact layout |
+| 3 | Visual | Hero imagery, bold typography, emotional |
+| 4 | Conventional | Industry-standard patterns, familiar UX |
+
+Each agent generates:
+- HTML mockup (self-contained, inline CSS)
+- Design rationale (2-3 sentences)
+- Accessibility notes
+
+### Phase 3: Comparison Board
+
+Present all mockups with side-by-side comparison:
+
+```markdown
+## Design Shotgun Results: {component}
+
+### Variation 1: Minimal
+Rationale: {why}
+[HTML mockup code]
+
+### Variation 2: Data-dense
+Rationale: {why}
+[HTML mockup code]
+
+### Variation 3: Visual
+Rationale: {why}
+[HTML mockup code]
+
+### Variation 4: Conventional
+Rationale: {why}
+[HTML mockup code]
+
+## Comparison
+| Criteria | V1 | V2 | V3 | V4 |
+|----------|----|----|----|----|
+| Readability | ★★★ | ★★ | ★★ | ★★★ |
+| Visual impact | ★ | ★★ | ★★★ | ★★ |
+| Information density | ★ | ★★★ | ★★ | ★★ |
+| Accessibility | ★★★ | ★★ | ★★ | ★★★ |
+```
+
+### Phase 4: Selection & Refinement
+
+User selects preferred variation(s). Selected design can be:
+- Refined with follow-up iterations
+- Combined with elements from other variations
+- Handed to fe-design-expert for production implementation
+
+## Integration
+
+| Component | Role |
+|-----------|------|
+| R009 | 4 parallel agents for mockup generation |
+| impeccable-design | Quality baseline for generated mockups |
+| fe-design-expert | Production refinement after selection |
+| web-design-guidelines | Accessibility and UX compliance |
+
+## Permission Mode
+
+When spawning agents via the Agent tool during this skill's execution, always pass `mode: "bypassPermissions"`. The Agent tool default (`acceptEdits`) overrides agent frontmatter `permissionMode`, causing permission prompts during unattended execution.
+
+## Source
+
+Adapted from [garrytan/gstack](https://github.com/garrytan/gstack) /design-shotgun pattern.

package/templates/.claude/skills/playwright-compress/SKILL.md

@@ -0,0 +1,68 @@
+---
+name: playwright-compress
+description: PostToolUse hook that compresses Playwright MCP tool output using Haiku summarization — Layer 4 of the token defense stack
+scope: core
+version: 1.0.0
+user-invocable: false
+disable-model-invocation: true
+---
+
+# Playwright MCP Output Compression (Layer 4)
+
+## Purpose
+
+Reduces Playwright MCP tool output tokens by 94-96% using intelligent Haiku summarization while preserving `ref=` values for interactive flow continuity.
+
+## Architecture
+
+```
+MCP tool response (37K+ chars)
+  ↓ PostToolUse hook
+  ↓ playwright-compress.sh
+  ↓ claude -p --model haiku (summarize)
+  ↓ updatedMCPToolOutput (1.4K-1.9K chars)
+```
+
+## Token Defense Stack Position
+
+| Layer | Component | Mechanism | Scope |
+|-------|-----------|-----------|-------|
+| 1 | cc-token-saver | Time-based budget alerts | Session |
+| 2 | R013 Ecomode | Context-aware output compression | Agent |
+| 3 | MAX_MCP_OUTPUT_TOKENS | Hard truncation (lossy) | Setting |
+| **4** | **playwright-compress** | **Intelligent summarization (lossless ref=)** | **Hook** |
+
+## Behavior
+
+- **Trigger**: PostToolUse on `mcp__playwright__.*` tools
+- **Skip condition**: Output < 3000 characters (not worth compressing)
+- **ref= preservation**: All `ref=` attribute values are extracted and preserved in the summary
+- **Fallback**: If Haiku summarization fails, original output is returned unchanged
+- **Auth**: Uses Claude subscription auth (`claude -p`), no API key needed
+
+## Integration
+
+| Rule | Interaction |
+|------|-------------|
+| R001 | No external data transmission — uses local `claude -p` |
+| R013 | Complements Ecomode (Layer 2) with MCP-specific compression |
+| R021 | Advisory PostToolUse hook — never blocks |
+
+## Hook Configuration
+
+Configured in `.claude/hooks/hooks.json` PostToolUse section:
+
+```json
+{
+  "matcher": "mcp_tool_name matches \"mcp__playwright__.*\" || mcp_tool_name matches \"mcp__claude-in-chrome__.*\"",
+  "hooks": [{
+    "type": "command",
+    "command": "bash .claude/hooks/scripts/playwright-compress.sh"
+  }],
+  "description": "Layer 4: Compress Playwright/Chrome MCP output via Haiku summarization"
+}
+```
+
+## Source
+
+Adapted from [treesoop/claude-native-plugin](https://github.com/treesoop/claude-native-plugin) playwright-optimizer (MIT).

package/templates/.claude/skills/product-strategy/SKILL.md

@@ -0,0 +1,82 @@
+---
+name: product-strategy
+description: YC-style product strategy assessment with forced questions and CEO scope modes — adapted from gstack /office-hours pattern
+scope: core
+version: 1.0.0
+user-invocable: true
+argument-hint: "[product/feature name]"
+effort: high
+---
+
+# Product Strategy Assessment
+
+## Purpose
+
+Forces rigorous product thinking by applying YC's 6 mandatory questions before any major feature decision. Prevents "build first, think later" anti-pattern.
+
+## Usage
+
+```
+/product-strategy "new authentication system"
+/product-strategy "API rate limiting redesign"
+```
+
+## Workflow
+
+### Phase 1: YC Forced Questions
+
+Before any implementation planning, answer ALL 6 questions. Incomplete answers block Phase 2.
+
+| # | Question | Must Answer |
+|---|----------|-------------|
+| 1 | **Who is the user?** | Specific persona, not "everyone" |
+| 2 | **What problem does this solve?** | Observable behavior, not assumed need |
+| 3 | **How do they solve it today?** | Current workaround — if none exists, question the need |
+| 4 | **Why is this solution better?** | Measurable improvement, not "it's newer" |
+| 5 | **What's the smallest version that validates the hypothesis?** | MVP scope — ruthlessly cut |
+| 6 | **How will you know it worked?** | Success metric, measurable within 2 weeks |
+
+### Phase 2: CEO Scope Mode Assessment
+
+Categorize the feature into one of 4 modes:
+
+| Mode | Signal | Action |
+|------|--------|--------|
+| **Expansion** | Strong user signal + clear gap | Full implementation, invest aggressively |
+| **Selective** | Mixed signals, some demand | Targeted implementation, measure before expanding |
+| **Hold** | Low signal, maintenance only | Keep working, no new investment |
+| **Reduction** | Negative signal, cost > value | Phase out, redirect resources |
+
+### Phase 3: Output
+
+Generate structured assessment:
+
+```markdown
+## Product Strategy: {feature}
+
+### YC Assessment
+1. User: {answer}
+2. Problem: {answer}
+3. Current solution: {answer}
+4. Why better: {answer}
+5. MVP: {answer}
+6. Success metric: {answer}
+
+### Scope Mode: {Expansion|Selective|Hold|Reduction}
+Rationale: {why this mode}
+
+### Recommendation
+{Go / No-Go / Needs more data}
+Next step: {specific action}
+```
+
+## Integration
+
+| Rule | Interaction |
+|------|-------------|
+| R010 | Orchestrator invokes skill; no file writes |
+| R015 | Transparent assessment — user sees all reasoning |
+
+## Source
+
+Adapted from [garrytan/gstack](https://github.com/garrytan/gstack) /office-hours + /plan-ceo-review patterns.

package/templates/CLAUDE.md

@@ -114,11 +114,11 @@ project/
 +-- CLAUDE.md                    # 진입점
 +-- .claude/
 |   +-- agents/                  # 서브에이전트 정의 (48 파일)
-|   +-- skills/                  # 스킬 (109 디렉토리)
+|   +-- skills/                  # 스킬 (112 디렉토리)
 |   +-- rules/                   # 전역 규칙 (R000-R022)
 |   +-- hooks/                   # 훅 스크립트 (보안, 검증, HUD)
 |   +-- contexts/                # 컨텍스트 파일 (ecomode)
-+-- guides/                      # 레퍼런스 문서 (39 토픽)
++-- guides/                      # 레퍼런스 문서 (40 토픽)
 ```
 
 ## 오케스트레이션

package/templates/guides/browser-automation/01-browser-automation-patterns.md

@@ -0,0 +1,68 @@
+# Browser Automation Patterns for AI Agents
+
+## Overview
+
+Reference guide for AI-controlled browser automation patterns, focusing on integration with Claude Code and MCP-based browser tools.
+
+## Patterns
+
+### 1. MCP-based Browser Control (Recommended)
+
+Use MCP tools (`mcp__claude-in-chrome__*` or `mcp__playwright__*`) for browser interaction:
+
+```
+Agent → MCP tool call → Browser extension/Playwright → Page interaction
+```
+
+**Advantages**: Native integration, no external dependencies, permission-controlled.
+
+### 2. Cookie-Based Authentication
+
+For testing authenticated flows, import cookies from a real browser session:
+
+```bash
+# Export cookies from browser (DevTools → Application → Cookies)
+# Import into Playwright context for authenticated testing
+```
+
+**Use case**: QA testing of authenticated pages without re-implementing login flows.
+
+### 3. Anti-Bot Stealth Patterns
+
+When automating against sites with bot detection:
+- Use realistic viewport sizes and user agents
+- Add human-like delays between actions
+- Randomize mouse movement patterns
+- Respect robots.txt and rate limits
+
+**Caution**: Only use for authorized testing on your own applications.
+
+### 4. Cross-AI Vendor Orchestration
+
+Multiple AI agents can share browser sessions via:
+- Shared MCP server connection
+- ngrok tunnels for remote access (scoped tokens for security)
+- Agent Teams (R018) for coordination
+
+## Tools Available in oh-my-customcode
+
+| Tool | Scope | Configuration |
+|------|-------|---------------|
+| `mcp__claude-in-chrome__*` | Chrome DevTools Protocol | MCP server in settings |
+| `mcp__playwright__*` | Playwright automation | MCP server in settings |
+| `playwright-compress` | Output compression (Layer 4) | PostToolUse hook |
+
+## Security Considerations
+
+| Concern | Mitigation |
+|---------|-----------|
+| Credential exposure | Never hardcode credentials; use env vars or cookie import |
+| External data transmission | R001 compliance — no PII to external services |
+| Rate limiting | Respect target site limits; implement backoff |
+| Scope creep | Only automate your own applications or authorized targets |
+
+## References
+
+- [garrytan/gstack](https://github.com/garrytan/gstack) — /browse, /pair-agent patterns
+- [playwright.dev](https://playwright.dev) — Official Playwright documentation
+- [Chrome DevTools Protocol](https://chromedevtools.github.io/devtools-protocol/) — CDP reference

package/templates/guides/claude-code/14-token-efficiency.md

@@ -0,0 +1,187 @@
+# Token Efficiency — Three-Layer Defense Stack
+
+> **Source**: [Claude Code & Codex token efficiency by settings adjustment](https://www.stdy.blog/increasing-token-efficiency-by-setting-adjustment-in-claude-and-codex/)
+> **Reference baseline**: Claude Code v2.1.114+ / Codex v0.121.0+
+
+## Why This Matters
+
+Token spend in Claude Code is not purely a function of task complexity. A significant portion of token consumption occurs through structural overhead: auto-injected git instructions, IDE file listings, tool output that exceeds what the model actually needs, and session state reloaded unnecessarily across turns.
+
+The three-layer defense stack addresses this overhead at three distinct points in the session lifecycle:
+
+```
+┌─────────────────────────────────────────────────────────────────┐
+│  Layer 1: cc-token-saver (CACHE DEFENSE)                        │
+│  Before session — protect prompt cache TTL from idle expiry     │
+├─────────────────────────────────────────────────────────────────┤
+│  Layer 2: R013 Ecomode (RUNTIME COMPRESSION)                    │
+│  During session — compact output, aggregate results, prune input│
+├─────────────────────────────────────────────────────────────────┤
+│  Layer 3: Settings-Based Gates (PRE-SESSION PREVENTION)         │
+│  Config time — disable injections before they happen            │
+├─────────────────────────────────────────────────────────────────┤
+│  Layer 4: playwright-compress (MCP OUTPUT INTELLIGENCE)         │
+│  PostToolUse hook — Haiku summarization of browser MCP output   │
+└─────────────────────────────────────────────────────────────────┘
+```
+
+Each layer is independently deployable and non-overlapping. Together they form a complete defense.
+
+---
+
+## Layer 1: cc-token-saver (Prompt Cache TTL Guard)
+
+**What it does:** Detects when the 1-hour prompt cache TTL is about to expire due to idle time. Warns before cache invalidates, preventing a full re-spend on the next turn.
+
+**Why it matters:** Claude Code's prompt cache has a 1-hour TTL on idle. If you pause a long session, the entire cached context must be re-processed at full cost on the next message. cc-token-saver intercepts this.
+
+**Key features:**
+- Token Guardian: idle TTL detection and warning
+- `/continue`: zero-cost context restore after session pause
+- `/usage-view`: cost dashboard for session/cumulative spend
+
+**When to use:** Always — install as a plugin and leave active.
+
+**Reference:** `guides/cc-token-saver/README.md`
+
+---
+
+## Layer 2: R013 Ecomode (Runtime Behavior Compression)
+
+**What it does:** Compresses agent output at runtime — compact result format, aggregated multi-agent results, and active pruning of irrelevant input context.
+
+**Why it matters:** Without ecomode, subagents return verbose outputs that accumulate across parallel invocations. At 4+ concurrent agents, unchecked output grows the context window rapidly.
+
+**Activation triggers:**
+- 4+ parallel tasks running simultaneously
+- Batch operations on independent targets
+- Context usage approaching 80%
+- Explicit "ecomode on"
+
+**Key behaviors:**
+- Agents return `status + 1-2 sentence summary + key_data only`
+- File lists compressed to count (when > 5 files)
+- Error traces: first/last 3 lines only
+- Code references: `path:line` ref instead of full block
+
+**When to use:** Auto-activates on threshold — configure threshold in ecomode config if needed.
+
+**Reference:** `.claude/rules/SHOULD-ecomode.md` (R013)
+
+---
+
+## Layer 3: Settings-Based Gates (Pre-Session Prevention)
+
+**What it does:** Disables token-consuming injections and sets output caps in configuration files before sessions start. These gates prevent overhead from ever entering the context window.
+
+**Why it matters:** Certain Claude Code defaults inject tokens on every session start regardless of whether they are needed:
+- `includeGitInstructions: true` (default) injects git workflow context on every session
+- `autoConnectIde: true` injects file lists from connected IDEs
+- Uncapped `BASH_MAX_OUTPUT_LENGTH` allows tool output to flood the context
+
+**How to apply:** `token-efficiency-audit` skill — see `.claude/skills/token-efficiency-audit/SKILL.md`
+
+---
+
+## Lever Reference Table
+
+### Interactive Session Levers (safe for development)
+
+| Lever | Location | Default | Recommended | Token Impact | Risk |
+|-------|----------|---------|-------------|-------------|------|
+| `includeGitInstructions` | settings.json | `true` | `false` | Medium — removes git workflow injection | None for most projects |
+| `autoConnectIde` | settings.json | `true` | `false` | Low — removes IDE file list injection | Loses IDE file awareness |
+| `attribution.commit` | settings.json | auto text | `""` | Low — removes attribution boilerplate | None |
+| `attribution.pr` | settings.json | auto text | `""` | Low — removes attribution boilerplate | None |
+| `BASH_MAX_OUTPUT_LENGTH` | env | unlimited | `15000` | High — caps bash output | Output truncated if > 15000 chars |
+| `CLAUDE_CODE_FILE_READ_MAX_OUTPUT_TOKENS` | env | unlimited | `8000` | Medium — caps file read output | Large files truncated |
+| `MAX_MCP_OUTPUT_TOKENS` | env | unlimited | `8000` | Medium — caps MCP output | MCP results truncated |
+| `CLAUDE_CODE_GLOB_NO_IGNORE` | env | `true` | `false` | Low — respects .gitignore | Fewer files visible in globs |
+
+### CI/Worker-Only Levers (destructive — disables oh-my-customcode)
+
+> These settings disable core oh-my-customcode functionality. **Never apply to interactive sessions.**
+
+| Lever | What it disables | Token impact | oh-my-customcode impact |
+|-------|-----------------|-------------|------------------------|
+| `CLAUDE_CODE_DISABLE_CLAUDE_MDS=1` | All `.claude/*.md` files including CLAUDE.md | High | ALL global rules and routing offline |
+| `CLAUDE_AGENT_SDK_DISABLE_BUILTIN_AGENTS=1` | Built-in agent definitions | High | All 48 agents unavailable |
+| `ENABLE_CLAUDEAI_MCP_SERVERS=false` | MCP server connections | Medium | MCP-dependent skills unavailable |
+| `CLAUDE_CODE_DISABLE_AUTO_MEMORY=1` | Agent auto-memory | Low | No persistent memory across sessions |
+
+### Codex CLI Levers
+
+| Lever | Location | Default | Recommended | Token Impact |
+|-------|----------|---------|-------------|-------------|
+| `features.apps` | config.toml | `true` | `false` | Medium |
+| `apps._default.enabled` | config.toml | `true` | `false` | Medium |
+| `web_search` | config.toml | `"auto"` | `"disabled"` | Medium — web search adds significant context |
+| `tool_output_token_limit` | config.toml | `10000` | `10000` | High — do not lower below 5000 |
+
+---
+
+## Tradeoffs and Guardrails
+
+### The re-call trap
+
+Setting output limits too low forces the model into repeated re-call loops — the model issues `tail -n 50 output.txt` or re-reads files in chunks, which costs more tokens than the original uncapped output. The minimum values below are empirically safe floors:
+
+| Variable | Safe minimum | Recommended |
+|----------|-------------|-------------|
+| `BASH_MAX_OUTPUT_LENGTH` | 10000 | 15000 |
+| `CLAUDE_CODE_FILE_READ_MAX_OUTPUT_TOKENS` | 4000 | 8000 |
+| `MAX_MCP_OUTPUT_TOKENS` | 4000 | 8000 |
+| Codex `tool_output_token_limit` | 5000 | 10000 |
+
+### Version drift
+
+Settings defaults change with minor CC version releases. After each upgrade, verify active defaults with `/token-efficiency-audit audit`. The reference baseline for this guide is CC v2.1.114+ / Codex v0.121.0+.
+
+### includeGitInstructions tradeoff
+
+Disabling `includeGitInstructions` removes git workflow guidance from the context. For projects with non-standard git workflows or junior contributors, this guidance may be worth keeping. For projects with experienced teams using `mgr-gitnerd` (R010), the injection is redundant.
+
+---
+
+## Interaction with Other Rules
+
+| Rule / Component | Interaction |
+|-----------------|-------------|
+| R013 Ecomode | Layer 2 runtime compression. These layers are complementary — apply both. |
+| cc-token-saver | Layer 1 cache defense. `Token Guardian` + `BASH_MAX_OUTPUT_LENGTH` together eliminate the two largest waste sources. |
+| R010 Orchestrator | `CLAUDE_CODE_DISABLE_CLAUDE_MDS` disables R010 enforcement — CI-only. |
+| R001 Safety | `apply-ci` mode is Risk Level High — requires user confirmation before applying. |
+| R012 HUD Statusline | Statusline shows CTX% — effective measure of Layer 2+3 combined impact. |
+| playwright-compress | Layer 4 hook — complements Layer 3 MAX_MCP_OUTPUT_TOKENS with intelligent lossless compression. |
+
+---
+
+## Layer 4: MCP Output Intelligence Compression
+
+PostToolUse hook that compresses Playwright and Chrome MCP tool output using Haiku summarization.
+
+| Metric | Before | After | Reduction |
+|--------|--------|-------|-----------|
+| browser_navigate | 37,983 chars | 1,922 chars | -94% |
+| browser_snapshot | 37,897 chars | 1,435 chars | -96% |
+
+- Preserves `ref=` attribute values for interactive flow
+- Skips output < 3000 chars
+- Falls back to original on Haiku failure
+- No API key needed (uses `claude -p` subscription auth)
+
+Configuration: `.claude/hooks/scripts/playwright-compress.sh`
+Hook trigger: `mcp__playwright__.*` and `mcp__claude-in-chrome__.*`
+
+---
+
+## Cross-References
+
+- `guides/claude-code/13-cli-flags.md` — CLI flags for non-interactive/CI invocation
+- `guides/cc-token-saver/README.md` — Layer 1 detailed guide
+- `.claude/rules/SHOULD-ecomode.md` — Layer 2 R013 specification
+- `.claude/skills/token-efficiency-audit/SKILL.md` — Layer 3 HOW: audit and apply
+- `.claude/skills/monitoring-setup/SKILL.md` — Measure effectiveness via OTel metrics
+- `.claude/skills/update-config/` — Generic settings.json manipulation (broader scope)
+- `.claude/skills/playwright-compress/SKILL.md` — Layer 4 MCP output compression hook
+- `.claude/hooks/scripts/playwright-compress.sh` — Layer 4 hook script

package/templates/manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.101.0",
+  "version": "0.102.0",
   "lastUpdated": "2026-04-18T00:00:00.000Z",
   "components": [
     {
@@ -18,13 +18,13 @@
       "name": "skills",
       "path": ".claude/skills",
       "description": "Reusable skill modules (includes slash commands)",
-      "files": 109
+      "files": 112
     },
     {
       "name": "guides",
       "path": "guides",
       "description": "Reference documentation",
-      "files": 39
+      "files": 40
     },
     {
       "name": "hooks",