claude-slim 2.2.1 → 2.2.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "claude-slim",
3
- "version": "2.2.1",
3
+ "version": "2.2.2",
4
4
  "description": "Analyze and reduce Claude Code token overhead",
5
5
  "type": "module",
6
6
  "bin": {
@@ -41,26 +41,28 @@ bash "${CLAUDE_PLUGIN_ROOT}/skills/claude-slim/scripts/scan.sh"
41
41
 
42
42
  After getting the scan JSON, YOU must interpret and present results to the user. Do NOT just dump raw CLI output. Present a full diagnostic report in the user's language.
43
43
 
44
+ > **Templates below are shown in English for readability. Always translate headers, labels, and prompts into the user's detected language when rendering.**
45
+
44
46
  ### 2-1. Environment Snapshot Table
45
47
 
46
48
  Show a summary table:
47
49
 
48
- | 항목 | 수치 | 토큰 |
49
- |------|------|------|
50
- | 로컬 스킬 | N (XKB) | X tok |
51
- | 플러그인 | N (M 스킬) | ~X tok |
50
+ | Item | Count | Tokens |
51
+ |------|-------|--------|
52
+ | Local skills | N (XKB) | X tok |
53
+ | Plugins | N (M skills) | ~X tok |
52
54
  | CLAUDE.md | XKB | X tok |
53
- | 메모리 파일 | N (XKB) | ~X tok |
54
- | **세션 시작 오버헤드** | | **~X tok** |
55
+ | Memory files | N (XKB) | ~X tok |
56
+ | **Session startup overhead** | | **~X tok** |
55
57
 
56
58
  ### 2-2. Plugin Detail Table
57
59
 
58
60
  List each plugin with skill count and a judgment:
59
61
 
60
- | 플러그인 | 스킬 | 비고 |
61
- |----------|:-------:|------|
62
- | omc | 36 | 코어 플러그인. 유지 |
63
- | temp_local_... | 1 | **실패한 설치 잔여물. 삭제 대상** |
62
+ | Plugin | Skills | Notes |
63
+ |--------|:------:|-------|
64
+ | omc | 36 | Core plugin. Keep. |
65
+ | temp_local_... | 1 | **Failed install remnant. Cleanup target.** |
64
66
 
65
67
  Annotate each with status: actively used, possibly unused, or cleanup target. Flag `temp_local_*` entries as failed install remnants.
66
68
 
@@ -68,18 +70,18 @@ Annotate each with status: actively used, possibly unused, or cleanup target. Fl
68
70
 
69
71
  Group issues by tier and explain EACH one with context and recommendation:
70
72
 
71
- **Tier 1 — 즉시 정리 (위험 없음):**
73
+ **Tier 1 — Immediate cleanup (zero risk):**
72
74
  These are safe to remove with zero risk: broken symlinks, empty templates, .skill/ duplicates, temp_local_* cache. Pre-selected. Explain why each is safe.
73
75
 
74
- **Tier 2 — 정리 추천:**
76
+ **Tier 2 — Recommended cleanup:**
75
77
  These are recommended but need user judgment. For each issue, explain:
76
78
  - What is it and why it's flagged
77
79
  - What happens if you remove it (safe? any side effects?)
78
80
  - How many tokens it saves
79
81
 
80
- Example: "frontend-design 로컬과 플러그인에 있습니다. 로컬 제거해도 플러그인 버전이 남으니 안전하게 제거 가능. ~823 tok 절감."
82
+ Example: "frontend-design exists both locally and in a plugin. Removing the local copy is safe because the plugin version remains. Saves ~823 tok."
81
83
 
82
- **Tier 3 — 선택 사항 (사용자 판단):**
84
+ **Tier 3 — Optional (user judgment):**
83
85
  These are large skills that cost tokens but might be in active use. For each:
84
86
  - Show size and token cost
85
87
  - Judge whether the user likely uses it (based on what it does)
@@ -94,7 +96,7 @@ End with a numbered action list, ordered by impact:
94
96
 
95
97
  Show estimated total token savings if all recommended actions are taken.
96
98
 
97
- If subcommand is `scan`, stop here. Ask "정리할까요?" only for the full pipeline.
99
+ If subcommand is `scan`, stop here. Ask a localized equivalent of "Proceed with cleanup?" only for the full pipeline.
98
100
 
99
101
  ---
100
102
 
@@ -133,7 +135,7 @@ cd "${CLAUDE_PLUGIN_ROOT}" && node dist/cli.js restore
133
135
 
134
136
  ## Language
135
137
 
136
- Detect the user's language from their most recent message. Present all reports, analysis, and explanations in that language. The CLI output is machine-readable translate only the user-facing interpretation.
138
+ Detect the user's language from their most recent message. Present all reports, analysis, and explanations in that language — including table headers, tier labels, prompts, and every user-facing string. The CLI output is machine-readable (always English) and must not be echoed verbatim; translate its content into the user's language when you interpret it. The example tables above are written in English only for authoring clarity — do not treat them as a required output format.
137
139
 
138
140
  ## Rules
139
141