@jakkrichm/create-nexus-devflow 2.0.0 → 2.0.1

package/template/.agents/skills/english-to-thai-translator/SKILL.md

@@ -1,125 +1,125 @@
----
-name: english-to-thai-translator
-description: English to Thai translation with context awareness for software development documentation and user interfaces.
-allowed-tools: Read, Grep, Glob
----
-
-# 🇹🇭 English to Thai Translation Skill
-
-This skill enables AI agents to translate English text to Thai while maintaining technical accuracy and contextual meaning. It's designed specifically for software development environments where precise terminology is crucial.
-
-## 🎯 When to Use This Skill
-
-- Translating technical documentation from English to Thai
-- Localizing user interface elements (buttons, labels, messages)
-- Converting code comments and developer notes
-- Creating multilingual project specifications
-- Translating API documentation or technical requirements
-
-## 📝 Translation Guidelines
-
-### Technical Terminology
-- Maintain consistency with existing project terminology
-- Use appropriate Thai technical terms for software concepts
-- Preserve acronyms and abbreviations when they're standard in Thai context
-- When no direct Thai equivalent exists, use transliteration + explanation
-
-### Style and Tone
-- Keep formal tone for documentation and specifications
-- Use conversational tone for user-facing interfaces
-- Maintain consistent terminology throughout the document
-- Ensure translations are culturally appropriate for Thai audience
-
-### Special Considerations
-- **Code Comments**: Preserve code structure, translate only comments
-- **API Documentation**: Maintain parameter names and technical descriptions
-- **UI Text**: Follow Thai text direction (left-to-right) and spacing conventions
-- **Numbers and Dates**: Use Thai number formats and date conventions
-
-## 🛠️ Usage Examples
-
-### Example 1: Translating Documentation
-```
-Original English:
-"Configure the database connection parameters in the config file."
-
-Thai Translation:
-"ตั้งค่าพารามิเตอร์การเชื่อมต่อฐานข้อมูลในไฟล์กำหนดค่า"
-```
-
-### Example 2: Translating UI Elements
-```
-Original English:
-"Save Changes"
-
-Thai Translation:
-"บันทึกการเปลี่ยนแปลง"
-```
-
-### Example 3: Translating Technical Specifications
-```
-Original English:
-"The system shall validate user input before processing."
-
-Thai Translation:
-"ระบบจะต้องตรวจสอบข้อมูลที่ผู้ใช้ป้อนก่อนประมวลผล"
-```
-
-## 📚 Best Practices
-
-### DO ✅
-- Use proper Thai punctuation and spacing conventions
-- Maintain technical accuracy over literal translation
-- Ensure consistency with existing Thai terminology in the project
-- Preserve code formatting when translating comments
-
-### DON'T ❌
-- Don't translate technical terms without context consideration
-- Don't ignore cultural appropriateness for Thai audience
-- Don't break existing code structure or syntax
-- Don't create overly literal translations that lose meaning
-
-## 🧪 Quality Checks
-
-Before completing translation tasks, verify:
-1. Technical accuracy of translated terminology
-2. Cultural appropriateness of the translation
-3. Consistency with project's existing Thai documentation
-4. Proper formatting and spacing for UI elements
-5. No broken links or references in translated content
-
-## 🔄 Integration with PRPs Framework
-
-This skill works within the DevFlow 2.0 workflow:
-1. During `/10-Define` or `/20-Spec`, it can help create multilingual specifications
-2. In `/30-Plan`, it helps explain technical requirements in Thai
-3. During `/40-Implement`, it translates comments and documentation when needed
-4. In `/50-Verify` or `/60-Report`, it helps ensure translated content remains clear and correct
-
-## 📁 File Structure
-
-The skill is designed to work with:
-- Documentation files (`.md`, `.txt`)
-- Code comments (`.js`, `.ts`, `.py`, `.java`)
-- Configuration files that contain text to be translated
-- User interface text resources
-
-## ⚠️ Limitations
-
-This skill provides general translation capabilities but may require human review for:
-- Highly specialized technical domains
-- Cultural nuances and idioms
-- Creative content requiring artistic interpretation
-- Legal or regulatory documents requiring official translations
-
-## 📋 Language Constraints
-
-This skill is strictly limited to translating between English and Thai languages only. All output must be exclusively in either English or Thai, with no inclusion of:
-- Chinese (or any other language)
-- Mixed language content
-- Transliterations that include non-Thai characters
-- Any foreign language elements
-
-The translation must maintain pure English-to-Thai conversion without introducing additional languages or mixed scripts.
-
-*Generated by Nexus-DevFlow Specialist*
+---
+name: english-to-thai-translator
+description: English to Thai translation with context awareness for software development documentation and user interfaces.
+allowed-tools: Read, Grep, Glob
+---
+
+# 🇹🇭 English to Thai Translation Skill
+
+This skill enables AI agents to translate English text to Thai while maintaining technical accuracy and contextual meaning. It's designed specifically for software development environments where precise terminology is crucial.
+
+## 🎯 When to Use This Skill
+
+- Translating technical documentation from English to Thai
+- Localizing user interface elements (buttons, labels, messages)
+- Converting code comments and developer notes
+- Creating multilingual project specifications
+- Translating API documentation or technical requirements
+
+## 📝 Translation Guidelines
+
+### Technical Terminology
+- Maintain consistency with existing project terminology
+- Use appropriate Thai technical terms for software concepts
+- Preserve acronyms and abbreviations when they're standard in Thai context
+- When no direct Thai equivalent exists, use transliteration + explanation
+
+### Style and Tone
+- Keep formal tone for documentation and specifications
+- Use conversational tone for user-facing interfaces
+- Maintain consistent terminology throughout the document
+- Ensure translations are culturally appropriate for Thai audience
+
+### Special Considerations
+- **Code Comments**: Preserve code structure, translate only comments
+- **API Documentation**: Maintain parameter names and technical descriptions
+- **UI Text**: Follow Thai text direction (left-to-right) and spacing conventions
+- **Numbers and Dates**: Use Thai number formats and date conventions
+
+## 🛠️ Usage Examples
+
+### Example 1: Translating Documentation
+```
+Original English:
+"Configure the database connection parameters in the config file."
+
+Thai Translation:
+"ตั้งค่าพารามิเตอร์การเชื่อมต่อฐานข้อมูลในไฟล์กำหนดค่า"
+```
+
+### Example 2: Translating UI Elements
+```
+Original English:
+"Save Changes"
+
+Thai Translation:
+"บันทึกการเปลี่ยนแปลง"
+```
+
+### Example 3: Translating Technical Specifications
+```
+Original English:
+"The system shall validate user input before processing."
+
+Thai Translation:
+"ระบบจะต้องตรวจสอบข้อมูลที่ผู้ใช้ป้อนก่อนประมวลผล"
+```
+
+## 📚 Best Practices
+
+### DO ✅
+- Use proper Thai punctuation and spacing conventions
+- Maintain technical accuracy over literal translation
+- Ensure consistency with existing Thai terminology in the project
+- Preserve code formatting when translating comments
+
+### DON'T ❌
+- Don't translate technical terms without context consideration
+- Don't ignore cultural appropriateness for Thai audience
+- Don't break existing code structure or syntax
+- Don't create overly literal translations that lose meaning
+
+## 🧪 Quality Checks
+
+Before completing translation tasks, verify:
+1. Technical accuracy of translated terminology
+2. Cultural appropriateness of the translation
+3. Consistency with project's existing Thai documentation
+4. Proper formatting and spacing for UI elements
+5. No broken links or references in translated content
+
+## 🔄 Integration with PRPs Framework
+
+This skill works within the DevFlow 2.0 workflow:
+1. During `/10-Define` or `/20-Spec`, it can help create multilingual specifications
+2. In `/30-Plan`, it helps explain technical requirements in Thai
+3. During `/40-Implement`, it translates comments and documentation when needed
+4. In `/50-Verify` or `/60-Report`, it helps ensure translated content remains clear and correct
+
+## 📁 File Structure
+
+The skill is designed to work with:
+- Documentation files (`.md`, `.txt`)
+- Code comments (`.js`, `.ts`, `.py`, `.java`)
+- Configuration files that contain text to be translated
+- User interface text resources
+
+## ⚠️ Limitations
+
+This skill provides general translation capabilities but may require human review for:
+- Highly specialized technical domains
+- Cultural nuances and idioms
+- Creative content requiring artistic interpretation
+- Legal or regulatory documents requiring official translations
+
+## 📋 Language Constraints
+
+This skill is strictly limited to translating between English and Thai languages only. All output must be exclusively in either English or Thai, with no inclusion of:
+- Chinese (or any other language)
+- Mixed language content
+- Transliterations that include non-Thai characters
+- Any foreign language elements
+
+The translation must maintain pure English-to-Thai conversion without introducing additional languages or mixed scripts.
+
+*Generated by Nexus-DevFlow Specialist*

package/template/.agents/skills/followup/SKILL.md

@@ -3,81 +3,81 @@ name: followup
 description: Followup workflow
 ---
 
----
-description: Follow-up Planning - Extend an existing completed or reviewed task without replacing the existing implementation plan.
----
-
-# Phase 35: Follow-up Planning
-
-## Request: $ARGUMENTS
-
-Use this workflow when the user wants to add more functionality to an existing task after implementation, QA, or human review.
-
-Primary behavior now lives in the `review-followup-routing` skill using `task-followup` mode. Keep this workflow as the compatibility wrapper for extending an existing running ID.
-
-## Prompt Source
-
-Adapted from:
-
-- `followup_planner.md`
-
-## Core Rule
-
-Extend, do not replace.
-
-Preserve existing phases, subtasks, statuses, logs, QA results, and completed context.
-
-## Process
-
-### 1. Load Existing Task
-
-Read:
-
-- `devflow/runs/{ID}-*/10-define.md`
-- `devflow/runs/{ID}-*/20-spec.md`
-- `devflow/runs/{ID}-*/30-plan.md`
-- `devflow/runs/{ID}-*/40-implement.md`
-- `devflow/runs/{ID}-*/50-verify.md` if present
-
-### 2. Classify The Follow-Up
-
-Classify the request:
-
-- extension
-- enhancement
-- integration
-- refinement
-- bug fix after review
-
-### 3. Append New Work
-
-Use plan helpers:
-
-Append the follow-up scope directly to the relevant stage markdown files for the same running ID. Add new phases, subtasks, and validation notes in `30-plan.md` and carry resulting work into later stages.
-
-### 4. Ask For Confirmation
-
-After adding or proposing follow-up subtasks, ask the user to confirm before `/40-Implement`.
-
-## Output
-
-Return:
-
-- follow-up category
-- new phase/subtask plan
-- validation result
-- next command: `/40-Implement {ID}`
-
-## Relationship To DevFlow 2.0
-
-- Classification: Companion command
-- Mainline status: Not a numbered stage
-- Typical entry points: after review, triage, or release follow-up work is identified
-- Typical handoff targets: `/10-Define`, `/20-Spec`, `/30-Plan`, `/40-Implement`
-
-## Sources
-
-- `AGENTS.md`
-- Related commands: `PR-Followup`, `Issue-Triage`, `Human-Feedback`, `/10-Define`, `/20-Spec`, `/40-Implement`
-
-
+---
+description: Follow-up Planning - Extend an existing completed or reviewed task without replacing the existing implementation plan.
+---
+
+# Phase 35: Follow-up Planning
+
+## Request: $ARGUMENTS
+
+Use this workflow when the user wants to add more functionality to an existing task after implementation, QA, or human review.
+
+Primary behavior now lives in the `review-followup-routing` skill using `task-followup` mode. Keep this workflow as the compatibility wrapper for extending an existing running ID.
+
+## Prompt Source
+
+Adapted from:
+
+- `followup_planner.md`
+
+## Core Rule
+
+Extend, do not replace.
+
+Preserve existing phases, subtasks, statuses, logs, QA results, and completed context.
+
+## Process
+
+### 1. Load Existing Task
+
+Read:
+
+- `devflow/runs/{ID}-*/10-define.md`
+- `devflow/runs/{ID}-*/20-spec.md`
+- `devflow/runs/{ID}-*/30-plan.md`
+- `devflow/runs/{ID}-*/40-implement.md`
+- `devflow/runs/{ID}-*/50-verify.md` if present
+
+### 2. Classify The Follow-Up
+
+Classify the request:
+
+- extension
+- enhancement
+- integration
+- refinement
+- bug fix after review
+
+### 3. Append New Work
+
+Use plan helpers:
+
+Append the follow-up scope directly to the relevant stage markdown files for the same running ID. Add new phases, subtasks, and validation notes in `30-plan.md` and carry resulting work into later stages.
+
+### 4. Ask For Confirmation
+
+After adding or proposing follow-up subtasks, ask the user to confirm before `/40-Implement`.
+
+## Output
+
+Return:
+
+- follow-up category
+- new phase/subtask plan
+- validation result
+- next command: `/40-Implement {ID}`
+
+## Relationship To DevFlow 2.0
+
+- Classification: Companion command
+- Mainline status: Not a numbered stage
+- Typical entry points: after review, triage, or release follow-up work is identified
+- Typical handoff targets: `/10-Define`, `/20-Spec`, `/30-Plan`, `/40-Implement`
+
+## Sources
+
+- `AGENTS.md`
+- Related commands: `PR-Followup`, `Issue-Triage`, `Human-Feedback`, `/10-Define`, `/20-Spec`, `/40-Implement`
+
+