specweave 0.11.0 → 0.12.0

package/plugins/specweave/skills/translator/SKILL.md.bak

@@ -1,172 +0,0 @@
----
-name: translator
-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.
-allowed-tools: Read, Write, Edit, Grep, Glob
----
-
-# Translator Skill
-
-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.
-
-## Core Capabilities
-
-### 1. **In-Session Translation** (Zero Cost!)
-- Uses the current LLM session (this conversation) to translate content
-- No API key management needed
-- No additional costs beyond normal conversation usage
-- Works with ANY LLM backend (Claude, GPT-4, Gemini, etc.)
-
-### 2. **Context-Aware Translation**
-- Preserves markdown formatting
-- Keeps code blocks unchanged
-- Maintains SpecWeave framework terms in English (e.g., "increment", "spec.md", "tasks.md")
-- Keeps technical terms in English when appropriate (e.g., "TypeScript", "npm", "git")
-
-### 3. **Content Type Handling**
-- **CLI Messages**: Short prompts, error messages, success messages
-- **Templates**: CLAUDE.md, AGENTS.md, README.md templates
-- **Documentation**: User guides, architecture docs
-- **Living Docs**: Strategic documents, ADRs, RFCs
-
-## Supported Languages
-
-- 🇬🇧 English (en) - Default
-- 🇷🇺 Russian (ru) - Русский
-- 🇪🇸 Spanish (es) - Español
-- 🇨🇳 Chinese (zh) - 中文
-- 🇩🇪 German (de) - Deutsch
-- 🇫🇷 French (fr) - Français
-- 🇯🇵 Japanese (ja) - 日本語
-- 🇰🇷 Korean (ko) - 한국어
-- 🇧🇷 Portuguese (pt) - Português
-
-## When I Activate
-
-I auto-activate when you mention:
-- "Translate to [language]"
-- "Convert to [language]"
-- "Multilingual support"
-- "i18n" or "internationalization"
-- Specific language names (Russian, Spanish, Chinese, etc.)
-- "Localization" or "locale"
-
-## How to Use Me
-
-### Simple Translation
-
-```
-User: "Translate this error message to Russian: File not found"
-Me: "Файл не найден"
-```
-
-### Template Translation
-
-```
-User: "Translate the CLAUDE.md template to Spanish"
-Me: *Reads template, translates while preserving structure, writes back*
-```
-
-### Living Docs Translation
-
-```
-User: "Translate the PRD to German"
-Me: *Translates spec.md, preserves framework terms, maintains formatting*
-```
-
-## Translation Rules
-
-### ✅ **Always Translate**:
-- User-facing messages
-- Documentation prose
-- Instructions and explanations
-- Success/error messages
-
-### ⏸️ **Keep in English**:
-- Framework terms: "increment", "spec.md", "plan.md", "tasks.md", "COMPLETION-SUMMARY.md"
-- SpecWeave commands: "/specweave:inc", "/specweave:do", "/specweave:progress"
-- Technical terms: "TypeScript", "npm", "git", "API", "CLI"
-- File names and paths: `.specweave/`, `src/`, `CLAUDE.md`
-- Code blocks and examples
-
-### 🔧 **Context-Dependent**:
-- Variable names in code (usually keep English)
-- Comments in code (translate if requested)
-- Technical acronyms (HTTP, JSON, REST - keep English)
-
-## Example Translations
-
-### CLI Message (English → Russian)
-
-**English**: "✅ Increment created successfully! Next: Run /specweave:do to start implementation."
-
-**Russian**: "✅ Increment успешно создан! Далее: Запустите /specweave:do для начала реализации."
-
-**Note**: "Increment" kept in English (framework term), "/specweave:do" kept as-is (command)
-
-### Documentation (English → Spanish)
-
-**English**: 
-```markdown
-## Increment Lifecycle
-
-An increment is a complete feature with:
-- spec.md - WHAT and WHY
-- plan.md - HOW to implement
-- tasks.md - WORK to do
-```
-
-**Spanish**:
-```markdown
-## Ciclo de Vida del Increment
-
-Un increment es una funcionalidad completa con:
-- spec.md - QUÉ y POR QUÉ
-- plan.md - CÓMO implementar
-- tasks.md - TRABAJO a realizar
-```
-
-**Note**: "Increment", "spec.md", "plan.md", "tasks.md" kept in English (framework terms)
-
-## Quality Guidelines
-
-1. **Accuracy**: Translate meaning, not just words
-2. **Natural**: Sound like a native speaker wrote it
-3. **Consistency**: Use same terms throughout
-4. **Context**: Understand SpecWeave concepts before translating
-5. **Formatting**: Preserve markdown, code blocks, links
-
-## Workflow
-
-When you ask me to translate:
-
-1. **Detect Context**: What type of content is this?
-2. **Read Source**: If it's a file, I'll read it first
-3. **Apply Rules**: Follow translation rules above
-4. **Translate**: Use the current LLM session (this conversation)
-5. **Preserve Structure**: Maintain formatting, code blocks, etc.
-6. **Write Back**: If requested, save translated content
-
-## Limitations
-
-**What I DON'T Do**:
-- ❌ Use external translation APIs (everything is LLM-native)
-- ❌ Translate code itself (only comments/strings if requested)
-- ❌ Change framework structure or behavior
-- ❌ Translate incrementally (full content at once for consistency)
-
-**What I DO Best**:
-- ✅ Translate documentation and user-facing content
-- ✅ Maintain technical accuracy
-- ✅ Preserve SpecWeave conventions
-- ✅ Work with ANY LLM (Claude, GPT-4, Gemini, etc.)
-
-## Tips for Best Results
-
-1. **Be Specific**: "Translate CLAUDE.md to Russian" > "Translate this"
-2. **Provide Context**: Mention if it's CLI, docs, or living docs
-3. **Request Preservation**: "Keep framework terms in English" (I do this by default)
-4. **Batch Translate**: Give me multiple files at once for consistency
-
----
-
-**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!