specweave 0.8.17 → 0.8.18

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.
@@ -0,0 +1,344 @@
1
+ ---
2
+ name: plugin-expert
3
+ description: Expert knowledge of Claude Code's plugin system, marketplace management, and installation commands. Activates for plugin installation, marketplace setup, plugin troubleshooting, plugin commands. Keywords plugin install, plugin marketplace, claude code plugins, plugin management, plugin errors, marketplace add, plugin list.
4
+ ---
5
+
6
+ # Plugin Expert - Claude Code Plugin System Authority
7
+
8
+ **Purpose**: Authoritative source of truth for Claude Code's plugin system, marketplace management, and correct installation syntax.
9
+
10
+ **When to Consult**: ANY time you need to install, manage, or reference Claude Code plugins.
11
+
12
+ ---
13
+
14
+ ## 🚨 CRITICAL: Correct Plugin Installation Format
15
+
16
+ **ALWAYS use this format**:
17
+ ```bash
18
+ /plugin install <plugin-name>
19
+ ```
20
+
21
+ **Examples**:
22
+ ```bash
23
+ # ✅ CORRECT
24
+ /plugin install specweave-github
25
+ /plugin install specweave-jira
26
+ /plugin install specweave-kubernetes
27
+
28
+ # ❌ WRONG - NEVER use @marketplace suffix
29
+ /plugin install specweave-github@specweave
30
+ /plugin install specweave-jira@specweave
31
+ ```
32
+
33
+ **Why this matters**:
34
+ - Claude Code automatically resolves plugins from registered marketplaces
35
+ - The `@marketplace` syntax does NOT exist in Claude Code
36
+ - Using wrong syntax causes installation failures
37
+
38
+ ---
39
+
40
+ ## Official Documentation
41
+
42
+ **Primary Sources** (ALWAYS defer to these):
43
+ 1. **Plugin System**: https://code.claude.com/docs/en/plugins
44
+ 2. **Marketplaces**: https://code.claude.com/docs/en/plugin-marketplaces
45
+ 3. **Blog Post**: https://claude.com/blog/claude-code-plugins
46
+
47
+ ---
48
+
49
+ ## Plugin Commands Reference
50
+
51
+ ### Installation
52
+
53
+ ```bash
54
+ # Install plugin from registered marketplace
55
+ /plugin install <plugin-name>
56
+
57
+ # Examples
58
+ /plugin install specweave
59
+ /plugin install specweave-github
60
+ /plugin install specweave-jira
61
+ ```
62
+
63
+ ### Marketplace Management
64
+
65
+ ```bash
66
+ # List all available marketplaces
67
+ /plugin marketplace list
68
+
69
+ # Add marketplace (GitHub)
70
+ /plugin marketplace add <owner>/<repo>
71
+ # Example: /plugin marketplace add anton-abyzov/specweave
72
+
73
+ # Add marketplace (local directory - development only)
74
+ /plugin marketplace add /path/to/.claude-plugin
75
+
76
+ # Remove marketplace
77
+ /plugin marketplace remove <marketplace-name>
78
+ ```
79
+
80
+ ### Plugin Management
81
+
82
+ ```bash
83
+ # List installed plugins
84
+ /plugin list --installed
85
+
86
+ # List all available plugins from marketplaces
87
+ /plugin list
88
+
89
+ # Get plugin info
90
+ /plugin info <plugin-name>
91
+
92
+ # Uninstall plugin
93
+ /plugin uninstall <plugin-name>
94
+
95
+ # Update plugin
96
+ /plugin update <plugin-name>
97
+ ```
98
+
99
+ ---
100
+
101
+ ## SpecWeave Marketplace Setup
102
+
103
+ ### User Projects (Production)
104
+
105
+ SpecWeave automatically registers the GitHub marketplace during `specweave init`:
106
+
107
+ **File**: `.claude/settings.json`
108
+ ```json
109
+ {
110
+ "extraKnownMarketplaces": {
111
+ "specweave": {
112
+ "source": {
113
+ "source": "github",
114
+ "repo": "anton-abyzov/specweave",
115
+ "path": ".claude-plugin"
116
+ }
117
+ }
118
+ }
119
+ }
120
+ ```
121
+
122
+ **Result**: Claude Code fetches plugins from GitHub on-demand (no local copies)
123
+
124
+ ### SpecWeave Repo (Development)
125
+
126
+ For contributors working on SpecWeave itself:
127
+
128
+ ```bash
129
+ # Add local marketplace (CLI only - settings.json doesn't support local paths)
130
+ /plugin marketplace add ./.claude-plugin
131
+
132
+ # Then install plugins
133
+ /plugin install specweave
134
+ /plugin install specweave-github
135
+ ```
136
+
137
+ ---
138
+
139
+ ## Available SpecWeave Plugins
140
+
141
+ ### Core (Auto-Installed)
142
+
143
+ - **specweave** - Framework essentials (increment planning, PM/Architect agents, living docs)
144
+ - Auto-installed during `specweave init`
145
+ - Provides: 9 skills, 22 agents, 22 commands, 8 hooks
146
+
147
+ ### Issue Trackers
148
+
149
+ - **specweave-github** - GitHub Issues integration
150
+ - Install: `/plugin install specweave-github`
151
+ - Provides: GitHub sync, PR automation, issue tracking
152
+
153
+ - **specweave-jira** - Jira integration
154
+ - Install: `/plugin install specweave-jira`
155
+ - Provides: Jira sync, epic management, sprint tracking
156
+
157
+ - **specweave-ado** - Azure DevOps integration
158
+ - Install: `/plugin install specweave-ado`
159
+ - Provides: ADO work items, boards, sprints
160
+
161
+ ### Tech Stacks
162
+
163
+ - **specweave-frontend** - React, Next.js, Vue, Angular
164
+ - Install: `/plugin install specweave-frontend`
165
+ - Provides: Frontend expert agent, component generation, design system integration
166
+
167
+ - **specweave-kubernetes** - K8s, Helm, kubectl
168
+ - Install: `/plugin install specweave-kubernetes`
169
+ - Provides: K8s expert agent, Helm chart generation, deployment validation
170
+
171
+ - **specweave-ml** - TensorFlow, PyTorch, ML workflows
172
+ - Install: `/plugin install specweave-ml`
173
+ - Provides: ML expert agent, training pipelines, model deployment
174
+
175
+ ### Utilities
176
+
177
+ - **specweave-diagrams** - Mermaid + C4 diagrams
178
+ - Install: `/plugin install specweave-diagrams`
179
+ - Provides: Architecture diagram generation, C4 model support
180
+
181
+ - **specweave-docs-preview** - Docusaurus documentation preview
182
+ - Install: `/plugin install specweave-docs-preview`
183
+ - Provides: Beautiful docs UI, hot reload, Mermaid rendering
184
+
185
+ ---
186
+
187
+ ## Common Mistakes to Avoid
188
+
189
+ ### ❌ Wrong: Using @marketplace Syntax
190
+
191
+ ```bash
192
+ # NEVER DO THIS
193
+ /plugin install specweave-github@specweave
194
+ /plugin install specweave-jira@specweave
195
+ ```
196
+
197
+ **Why wrong**: Claude Code doesn't support `@marketplace` suffix
198
+
199
+ **Correct**:
200
+ ```bash
201
+ /plugin install specweave-github
202
+ /plugin install specweave-jira
203
+ ```
204
+
205
+ ### ❌ Wrong: Using Local Paths in settings.json
206
+
207
+ ```json
208
+ {
209
+ "extraKnownMarketplaces": {
210
+ "specweave": {
211
+ "source": "./.claude-plugin" // ❌ NOT supported
212
+ }
213
+ }
214
+ }
215
+ ```
216
+
217
+ **Why wrong**: `extraKnownMarketplaces` in settings.json only supports remote sources (GitHub, Git)
218
+
219
+ **Correct for development**:
220
+ ```bash
221
+ # Use CLI instead
222
+ /plugin marketplace add ./.claude-plugin
223
+ ```
224
+
225
+ ### ❌ Wrong: Forgetting Marketplace Registration
226
+
227
+ ```bash
228
+ # Install without marketplace registered
229
+ /plugin install specweave-github # ❌ Fails: marketplace not found
230
+ ```
231
+
232
+ **Correct**:
233
+ ```bash
234
+ # 1. Register marketplace first (or ensure settings.json has it)
235
+ /plugin marketplace add anton-abyzov/specweave
236
+
237
+ # 2. Then install plugins
238
+ /plugin install specweave-github
239
+ ```
240
+
241
+ ---
242
+
243
+ ## Troubleshooting
244
+
245
+ ### "Marketplace not found" Error
246
+
247
+ **Symptom**: `/plugin install specweave-xxx` fails with "marketplace not found"
248
+
249
+ **Fix**:
250
+ ```bash
251
+ # Check registered marketplaces
252
+ /plugin marketplace list
253
+
254
+ # If specweave not listed, add it
255
+ /plugin marketplace add anton-abyzov/specweave
256
+
257
+ # Then retry install
258
+ /plugin install specweave-xxx
259
+ ```
260
+
261
+ ### Plugin Not Auto-Activating
262
+
263
+ **Symptom**: Plugin installed but skills/agents not working
264
+
265
+ **Causes**:
266
+ 1. Claude Code needs restart after plugin install
267
+ 2. Skill description keywords don't match user's context
268
+ 3. Plugin has errors (check plugin logs)
269
+
270
+ **Fix**:
271
+ ```bash
272
+ # 1. Verify plugin installed
273
+ /plugin list --installed
274
+
275
+ # 2. Restart Claude Code
276
+
277
+ # 3. Check skill descriptions match your context
278
+ ```
279
+
280
+ ### Installation Hangs or Fails
281
+
282
+ **Symptom**: `/plugin install` hangs or times out
283
+
284
+ **Causes**:
285
+ 1. Network issues (GitHub fetch failed)
286
+ 2. Marketplace not registered
287
+ 3. Plugin doesn't exist in marketplace
288
+
289
+ **Fix**:
290
+ ```bash
291
+ # 1. Check marketplace registered
292
+ /plugin marketplace list
293
+
294
+ # 2. Verify plugin exists
295
+ /plugin list # Shows all available plugins
296
+
297
+ # 3. Check network connectivity
298
+ # Try re-adding marketplace (refreshes cache)
299
+ /plugin marketplace remove specweave
300
+ /plugin marketplace add anton-abyzov/specweave
301
+ ```
302
+
303
+ ---
304
+
305
+ ## How Other Skills Should Use This
306
+
307
+ **Example: increment-planner skill recommending plugins**
308
+
309
+ ```markdown
310
+ **Step 6: Detect Required Plugins**
311
+
312
+ When recommending plugins, ALWAYS use correct format:
313
+
314
+ ✅ CORRECT:
315
+ 📦 Install recommended plugins:
316
+ /plugin install specweave-github
317
+ /plugin install specweave-kubernetes
318
+
319
+ ❌ WRONG:
320
+ /plugin install specweave-github@specweave # NEVER use @marketplace
321
+ ```
322
+
323
+ **Example: Auto-installation in TypeScript**
324
+
325
+ ```typescript
326
+ // ✅ CORRECT
327
+ execFileNoThrowSync('claude', ['plugin', 'install', 'specweave-github']);
328
+
329
+ // ❌ WRONG
330
+ execFileNoThrowSync('claude', ['plugin', 'install', 'specweave-github@specweave']);
331
+ ```
332
+
333
+ ---
334
+
335
+ ## References
336
+
337
+ - **Official Docs**: https://code.claude.com/docs/en/plugins
338
+ - **Marketplaces**: https://code.claude.com/docs/en/plugin-marketplaces
339
+ - **Blog**: https://claude.com/blog/claude-code-plugins
340
+ - **SpecWeave Marketplace**: https://github.com/anton-abyzov/specweave/.claude-plugin
341
+
342
+ ---
343
+
344
+ **Last Updated**: 2025-01-06 (v0.8.18)
@@ -367,8 +367,8 @@ SpecWeave plugins support **dual distribution**:
367
367
  - Works with ALL tools (Claude, Cursor, Copilot, Generic)
368
368
 
369
369
  2. **Claude Code Marketplace** (Native `/plugin`):
370
- - `/plugin marketplace add specweave/marketplace`
371
- - `/plugin install github@specweave`
370
+ - `/plugin marketplace add anton-abyzov/specweave`
371
+ - `/plugin install specweave-github`
372
372
  - Best UX for Claude Code users
373
373
 
374
374
  **Plugin Manifests** (both required):
@@ -8,6 +8,35 @@ allowed-tools: Read, Write, Edit, Grep, Glob
8
8
 
9
9
  I am a translation specialist for SpecWeave content. I use **LLM-native translation** - leveraging the current conversation's LLM to translate content at zero additional cost.
10
10
 
11
+ ## Translation Approaches Comparison
12
+
13
+ SpecWeave offers **two approaches** to translation. Choose based on your workflow:
14
+
15
+ | Aspect | **In-Session** (This Skill) | **Automated Hooks** (Optional) |
16
+ |--------|----------------------------|-------------------------------|
17
+ | **Cost** | **$0 (FREE)** | ~$0.003/increment |
18
+ | **Model** | **Any** (Claude, GPT-4, Gemini, DeepSeek, etc.) | Claude only (Haiku/Sonnet/Opus) |
19
+ | **Tool** | **Any** (Claude Code, Cursor, Copilot, ChatGPT, etc.) | Claude Code only |
20
+ | **Trigger** | Manual command or auto-prompt | Automatic after increment planning |
21
+ | **When to Use** | ✅ **Default** - zero cost, maximum flexibility | Optional - convenience for power users |
22
+ | **Setup** | None (works out of the box) | Enable in .specweave/config.json |
23
+
24
+ ### Choose Your Approach
25
+
26
+ **Use In-Session (This Skill)** if:
27
+ - ✅ You want **zero cost**
28
+ - ✅ You're using **any model** (GPT-4o-mini, Gemini Flash, etc.)
29
+ - ✅ You're using **any tool** (Cursor, Copilot, ChatGPT, etc.)
30
+ - ✅ You want control over when translation happens
31
+
32
+ **Use Automated Hooks** if:
33
+ - You're a Claude Code power user
34
+ - You want hands-off automation
35
+ - You're willing to pay ~$0.003/increment
36
+ - You want specs auto-translated after creation
37
+
38
+ **Note**: Both approaches produce identical quality. The primary difference is automation level and cost.
39
+
11
40
  ## Core Capabilities
12
41
 
13
42
  ### 1. **In-Session Translation** (Zero Cost!)
@@ -0,0 +1,172 @@
1
+ ---
2
+ name: translator
3
+ description: LLM-native translation skill for SpecWeave content. Activates when translation is needed for CLI messages, templates, documentation, or living docs. Uses the current LLM session for zero-cost translation. Keywords: translate, translation, language, multilingual, i18n, internationalization, Russian, Spanish, Chinese, German, French, localization, translate to.
4
+ allowed-tools: Read, Write, Edit, Grep, Glob
5
+ ---
6
+
7
+ # Translator Skill
8
+
9
+ I am a translation specialist for SpecWeave content. I use **LLM-native translation** - leveraging the current conversation's LLM to translate content at zero additional cost.
10
+
11
+ ## Core Capabilities
12
+
13
+ ### 1. **In-Session Translation** (Zero Cost!)
14
+ - Uses the current LLM session (this conversation) to translate content
15
+ - No API key management needed
16
+ - No additional costs beyond normal conversation usage
17
+ - Works with ANY LLM backend (Claude, GPT-4, Gemini, etc.)
18
+
19
+ ### 2. **Context-Aware Translation**
20
+ - Preserves markdown formatting
21
+ - Keeps code blocks unchanged
22
+ - Maintains SpecWeave framework terms in English (e.g., "increment", "spec.md", "tasks.md")
23
+ - Keeps technical terms in English when appropriate (e.g., "TypeScript", "npm", "git")
24
+
25
+ ### 3. **Content Type Handling**
26
+ - **CLI Messages**: Short prompts, error messages, success messages
27
+ - **Templates**: CLAUDE.md, AGENTS.md, README.md templates
28
+ - **Documentation**: User guides, architecture docs
29
+ - **Living Docs**: Strategic documents, ADRs, RFCs
30
+
31
+ ## Supported Languages
32
+
33
+ - 🇬🇧 English (en) - Default
34
+ - 🇷🇺 Russian (ru) - Русский
35
+ - 🇪🇸 Spanish (es) - Español
36
+ - 🇨🇳 Chinese (zh) - 中文
37
+ - 🇩🇪 German (de) - Deutsch
38
+ - 🇫🇷 French (fr) - Français
39
+ - 🇯🇵 Japanese (ja) - 日本語
40
+ - 🇰🇷 Korean (ko) - 한국어
41
+ - 🇧🇷 Portuguese (pt) - Português
42
+
43
+ ## When I Activate
44
+
45
+ I auto-activate when you mention:
46
+ - "Translate to [language]"
47
+ - "Convert to [language]"
48
+ - "Multilingual support"
49
+ - "i18n" or "internationalization"
50
+ - Specific language names (Russian, Spanish, Chinese, etc.)
51
+ - "Localization" or "locale"
52
+
53
+ ## How to Use Me
54
+
55
+ ### Simple Translation
56
+
57
+ ```
58
+ User: "Translate this error message to Russian: File not found"
59
+ Me: "Файл не найден"
60
+ ```
61
+
62
+ ### Template Translation
63
+
64
+ ```
65
+ User: "Translate the CLAUDE.md template to Spanish"
66
+ Me: *Reads template, translates while preserving structure, writes back*
67
+ ```
68
+
69
+ ### Living Docs Translation
70
+
71
+ ```
72
+ User: "Translate the PRD to German"
73
+ Me: *Translates spec.md, preserves framework terms, maintains formatting*
74
+ ```
75
+
76
+ ## Translation Rules
77
+
78
+ ### ✅ **Always Translate**:
79
+ - User-facing messages
80
+ - Documentation prose
81
+ - Instructions and explanations
82
+ - Success/error messages
83
+
84
+ ### ⏸️ **Keep in English**:
85
+ - Framework terms: "increment", "spec.md", "plan.md", "tasks.md", "COMPLETION-SUMMARY.md"
86
+ - SpecWeave commands: "/specweave:inc", "/specweave:do", "/specweave:progress"
87
+ - Technical terms: "TypeScript", "npm", "git", "API", "CLI"
88
+ - File names and paths: `.specweave/`, `src/`, `CLAUDE.md`
89
+ - Code blocks and examples
90
+
91
+ ### 🔧 **Context-Dependent**:
92
+ - Variable names in code (usually keep English)
93
+ - Comments in code (translate if requested)
94
+ - Technical acronyms (HTTP, JSON, REST - keep English)
95
+
96
+ ## Example Translations
97
+
98
+ ### CLI Message (English → Russian)
99
+
100
+ **English**: "✅ Increment created successfully! Next: Run /specweave:do to start implementation."
101
+
102
+ **Russian**: "✅ Increment успешно создан! Далее: Запустите /specweave:do для начала реализации."
103
+
104
+ **Note**: "Increment" kept in English (framework term), "/specweave:do" kept as-is (command)
105
+
106
+ ### Documentation (English → Spanish)
107
+
108
+ **English**:
109
+ ```markdown
110
+ ## Increment Lifecycle
111
+
112
+ An increment is a complete feature with:
113
+ - spec.md - WHAT and WHY
114
+ - plan.md - HOW to implement
115
+ - tasks.md - WORK to do
116
+ ```
117
+
118
+ **Spanish**:
119
+ ```markdown
120
+ ## Ciclo de Vida del Increment
121
+
122
+ Un increment es una funcionalidad completa con:
123
+ - spec.md - QUÉ y POR QUÉ
124
+ - plan.md - CÓMO implementar
125
+ - tasks.md - TRABAJO a realizar
126
+ ```
127
+
128
+ **Note**: "Increment", "spec.md", "plan.md", "tasks.md" kept in English (framework terms)
129
+
130
+ ## Quality Guidelines
131
+
132
+ 1. **Accuracy**: Translate meaning, not just words
133
+ 2. **Natural**: Sound like a native speaker wrote it
134
+ 3. **Consistency**: Use same terms throughout
135
+ 4. **Context**: Understand SpecWeave concepts before translating
136
+ 5. **Formatting**: Preserve markdown, code blocks, links
137
+
138
+ ## Workflow
139
+
140
+ When you ask me to translate:
141
+
142
+ 1. **Detect Context**: What type of content is this?
143
+ 2. **Read Source**: If it's a file, I'll read it first
144
+ 3. **Apply Rules**: Follow translation rules above
145
+ 4. **Translate**: Use the current LLM session (this conversation)
146
+ 5. **Preserve Structure**: Maintain formatting, code blocks, etc.
147
+ 6. **Write Back**: If requested, save translated content
148
+
149
+ ## Limitations
150
+
151
+ **What I DON'T Do**:
152
+ - ❌ Use external translation APIs (everything is LLM-native)
153
+ - ❌ Translate code itself (only comments/strings if requested)
154
+ - ❌ Change framework structure or behavior
155
+ - ❌ Translate incrementally (full content at once for consistency)
156
+
157
+ **What I DO Best**:
158
+ - ✅ Translate documentation and user-facing content
159
+ - ✅ Maintain technical accuracy
160
+ - ✅ Preserve SpecWeave conventions
161
+ - ✅ Work with ANY LLM (Claude, GPT-4, Gemini, etc.)
162
+
163
+ ## Tips for Best Results
164
+
165
+ 1. **Be Specific**: "Translate CLAUDE.md to Russian" > "Translate this"
166
+ 2. **Provide Context**: Mention if it's CLI, docs, or living docs
167
+ 3. **Request Preservation**: "Keep framework terms in English" (I do this by default)
168
+ 4. **Batch Translate**: Give me multiple files at once for consistency
169
+
170
+ ---
171
+
172
+ **Remember**: I'm using the current LLM session for translation, so there are **zero additional costs** beyond the normal conversation. This is the power of LLM-native multilingual support!
@@ -2,6 +2,7 @@
2
2
  .specweave/cache/
3
3
  .specweave/increments/*/logs/ # Gitignored, but structure preserved
4
4
  .specweave/increments/*/test-results/
5
+ .specweave/docs-site-internal/ # Generated Docusaurus site for internal docs
5
6
  .claude-plugin/ # Plugin marketplace (framework files)
6
7
  plugins/ # Plugin implementations (framework files)
7
8