Problem

When a workflow is exported as a command file (.claude/commands/*.md), the filename is derived from the workflow name. Due to case-insensitivity differences between operating systems, uppercase letters in workflow names cause issues:

Current Behavior

1. User creates a workflow named General-worldflow-JP
2. Export generates .claude/commands/general-worldflow-jp.md (lowercase)
3. User tries to run /General-worldflow-JP
4. ❌ Claude Code returns: Unknown skill: General-worldflow-JP

Additionally, on case-insensitive file systems (macOS/Windows), renaming from Test.md to test.md doesn't change the actual filename, causing Git synchronization issues across platforms.

Expected Behavior

1. Workflow names only allow lowercase letters, numbers, hyphens, and underscores
2. Validation error is shown when uppercase letters are entered
3. ✅ Consistent behavior across all platforms

Fixes #415

Solution

Enforce lowercase-only validation for workflow and SubAgentFlow names at multiple levels:

Changes

Validation Rules (src/shared/types/workflow-definition.ts)

• Added WORKFLOW.NAME_PATTERN: /^[a-z0-9_-]+$/
• Updated SUB_AGENT_FLOW.NAME_PATTERN to lowercase only

Extension Host (src/extension/commands/save-workflow.ts)

• Updated validation regex to enforce lowercase

UI Validation (src/webview/src/components/Toolbar.tsx)

• Added real-time validation with error display
• Validation on Save, Export, and Run handlers

SubAgentFlow Dialog (src/webview/src/components/dialogs/SubAgentFlowDialog.tsx)

• Updated pattern to lowercase only

i18n (5 languages)

• Added error messages for invalid workflow names

Impact

• Breaking Change: Existing workflows with uppercase names will need to be renamed
• Users notified in Awaiting feature #333 about this upcoming change
• Cross-platform Git compatibility improved

Testing

• Manual E2E testing completed
• Code quality checks passed (npm run format && npm run lint && npm run check && npm run build)

🤖 Generated with Claude Code