clavix 5.0.1 → 5.1.0

package/dist/templates/slash-commands/_components/agent-protocols/self-correction.md

@@ -1,61 +0,0 @@
-## Self-Correction Protocol
-
-**DETECT**: If you find yourself doing any of these 6 mistake types:
-
-### Mistake Type 1: Implementation Code
-- Writing function/class definitions for the user's feature
-- Creating component implementations
-- Generating API endpoint code
-- Writing test files for the user's feature
-- Creating database schemas/migrations
-- Writing configuration files for deployment
-- **Reading project files to "understand context" before showing analysis**
-- **Exploring the codebase before outputting optimized prompt**
-
-### Mistake Type 2: Skipping Quality Assessment
-- Not scoring all 6 quality dimensions
-- Providing optimization without quality analysis
-- Jumping directly to improved prompt without showing scores
-
-### Mistake Type 3: Wrong Depth Selection
-- Not suggesting comprehensive depth when quality scores are low
-- Not recommending `/clavix:prd` for strategic decisions
-- Ignoring triage indicators and escalation factors
-
-### Mistake Type 4: Incomplete Pattern Application
-- Not applying all applicable patterns for the detected intent
-- Skipping patterns without explanation
-- Not showing which patterns were applied
-
-### Mistake Type 5: Missing Validation (Comprehensive Depth)
-- Not generating validation checklist in comprehensive depth
-- Not identifying edge cases
-- Not providing alternative approaches
-
-### Mistake Type 6: Capability Hallucination
-- Claiming features Clavix doesn't have
-- Inventing pattern names that don't exist
-- Describing workflows that aren't documented
-
-**STOP**: Immediately halt the incorrect action
-
-**CORRECT**: Output an acknowledgment:
-> "I was about to [describe action]. Let me return to [fast/deep] prompt analysis."
-
-**RESUME**: Return to the appropriate Clavix workflow for this mode
-
----
-
-## Anti-Implementation Tripwires
-
-**Before your next tool call or action, check:**
-
-| Action | Tripwire | Response |
-|--------|----------|----------|
-| About to read project files | STOP | "I don't need to explore the codebase for prompt optimization" |
-| About to write code files | STOP | "Only `.clavix/` files are allowed in optimization mode" |
-| About to run build/test commands | STOP | "Project commands are for `/clavix:execute`, not optimization" |
-| About to make git commits | STOP | "Git operations belong in implementation mode" |
-| Haven't shown optimized prompt yet | STOP | "I need to show the analysis first" |
-
-**If any tripwire triggers:** Output the response and return to prompt analysis.

package/dist/templates/slash-commands/_components/agent-protocols/state-assertion.md

@@ -1,51 +0,0 @@
-## Mode State Assertion (Mandatory)
-
-**At the start of every Clavix workflow, assert your current mode state.**
-
-### State Assertion Format
-
-Output this block before beginning any analysis:
-
-```
-**CLAVIX MODE: [Mode Name]**
-Mode: [planning|implementation]
-Purpose: [Brief purpose description]
-Implementation: [BLOCKED|ALLOWED]
-```
-
-### Mode State Definitions
-
-| Mode | Type | Implementation | Purpose |
-|------|------|----------------|---------|
-| /clavix:improve | planning | BLOCKED | Prompt optimization (smart depth selection) |
-| /clavix:prd | planning | BLOCKED | PRD development |
-| /clavix:plan | planning | BLOCKED | Task breakdown generation |
-| /clavix:start | planning | BLOCKED | Requirements gathering |
-| /clavix:summarize | planning | BLOCKED | Requirements extraction |
-| /clavix:implement | implementation | ALLOWED | Feature implementation |
-| /clavix:execute | implementation | ALLOWED | Prompt execution |
-
-### Why State Assertion Matters
-
-1. **Prevents mode confusion**: Agent explicitly acknowledges what it can/cannot do
-2. **Blocks premature implementation**: Implementation BLOCKED modes cannot write feature code
-3. **Enables self-monitoring**: Agent can detect drift from declared state
-4. **Provides audit trail**: User sees what mode agent thinks it's in
-
-### Example Assertions
-
-**Planning Mode (Implementation BLOCKED):**
-```
-**CLAVIX MODE: Improve**
-Mode: planning
-Purpose: Optimizing user prompt with pattern-based analysis
-Implementation: BLOCKED - I will analyze and improve the prompt, not implement it
-```
-
-**Implementation Mode (Implementation ALLOWED):**
-```
-**CLAVIX MODE: Implementation**
-Mode: implementation
-Purpose: Implementing tasks from PRD/prompt
-Implementation: ALLOWED - I will write production code following specifications
-```

package/dist/templates/slash-commands/_components/agent-protocols/verification-methods.md

@@ -1,184 +0,0 @@
-## Verification Methods by Category
-
-### Functionality
-**Checklist items about:** Code works, features implemented, requirements met
-
-**Verification approach:**
-1. Run the implemented code/feature
-2. Check expected behavior matches requirements
-3. Verify all user flows complete successfully
-
-**Commands to use:**
-- Run application: `npm start`, `npm run dev`
-- Execute specific feature manually
-- Check output matches expected
-
-**Evidence examples:**
-- "Feature X works as specified"
-- "Login flow completes successfully"
-- "API returns expected response format"
-
----
-
-### Testing
-**Checklist items about:** Tests pass, coverage met, test quality
-
-**Verification approach:**
-1. Run test suite
-2. Check coverage report
-3. Verify no failing tests
-
-**Commands to use:**
-- `npm test` or project test command
-- `npm run coverage` for coverage report
-- Look for test output in terminal
-
-**Evidence examples:**
-- "npm test - 47 tests passing, 0 failed"
-- "Coverage: 85% (exceeds 80% threshold)"
-- "All integration tests pass"
-
----
-
-### Robustness/Edge Cases
-**Checklist items about:** Error handling, edge cases, graceful degradation
-
-**Verification approach:**
-1. Test with edge case inputs (empty, null, max values)
-2. Check error messages are user-friendly
-3. Verify system recovers gracefully
-
-**Manual testing:**
-- Input empty values
-- Input invalid data types
-- Test boundary conditions (min/max values)
-- Test with large datasets
-
-**Evidence examples:**
-- "Empty input shows validation error"
-- "Invalid email format displays helpful message"
-- "System handles 10,000 records without timeout"
-
----
-
-### Quality
-**Checklist items about:** Code style, conventions, no warnings
-
-**Verification approach:**
-1. Run linter
-2. Check for console errors
-3. Review code style
-
-**Commands to use:**
-- `npm run lint` or equivalent
-- Check browser console for errors
-- Review PR diff for style
-
-**Evidence examples:**
-- "npm run lint - 0 errors, 0 warnings"
-- "No console errors in browser"
-- "Code follows project conventions"
-
----
-
-### Accessibility
-**Checklist items about:** Keyboard navigation, screen reader, WCAG
-
-**Verification approach:**
-1. Tab through interface
-2. Check color contrast
-3. Verify alt text on images
-
-**Manual testing:**
-- Navigate using only keyboard
-- Check focus indicators visible
-- Test with screen reader (optional)
-
-**Evidence examples:**
-- "All interactive elements keyboard accessible"
-- "Focus order is logical"
-- "Color contrast meets WCAG AA"
-
----
-
-### Security
-**Checklist items about:** Auth, input sanitization, data protection
-
-**Verification approach:**
-1. Verify authentication required where expected
-2. Test input sanitization
-3. Check sensitive data handling
-
-**Manual testing:**
-- Try accessing protected routes without auth
-- Submit potentially malicious input
-- Check network tab for sensitive data exposure
-
-**Evidence examples:**
-- "Protected routes redirect to login"
-- "SQL injection attempts are sanitized"
-- "Passwords not logged or exposed"
-
----
-
-### Performance
-**Checklist items about:** Response times, resource usage
-
-**Verification approach:**
-1. Check response times
-2. Monitor memory/CPU usage
-3. Test with realistic data volumes
-
-**Tools:**
-- Browser DevTools Performance tab
-- Network tab for response times
-- Lighthouse performance score
-
-**Evidence examples:**
-- "Page load time < 2s"
-- "API response time < 200ms"
-- "Memory usage stable under load"
-
----
-
-### Documentation
-**Checklist items about:** Docs updated, comments present
-
-**Verification approach:**
-1. Check README updates
-2. Verify JSDoc/comments on complex functions
-3. Review API documentation
-
-**Commands to use:**
-- `cat README.md` - check for updates
-- Review changed files for comments
-
-**Evidence examples:**
-- "README updated with new feature"
-- "API endpoints documented"
-- "Complex logic has explanatory comments"
-
----
-
-## Verification Type Detection
-
-**Automated items contain keywords:**
-- compiles, builds, tests pass, lint, typecheck, no errors
-
-**Semi-automated items contain keywords:**
-- renders, displays, console errors, responsive, visual
-
-**Manual items contain keywords:**
-- requirements, edge cases, handles, correctly, properly
-
----
-
-## Confidence Levels
-
-| Level | When to use | Example |
-|-------|-------------|---------|
-| HIGH | Automated tool verification | npm test exit code 0 |
-| MEDIUM | Manual verification with clear evidence | Code review shows implementation |
-| LOW | General assessment without specific evidence | "Looks correct" |
-
-Always prefer higher confidence verification when possible.

package/dist/templates/slash-commands/_components/mode-headers/implementation-mode.md

@@ -1,21 +0,0 @@
-## CLAVIX MODE: Implementation
-
-**You are in Clavix implementation mode. You ARE authorized to write code and implement features.**
-
-**YOUR ROLE:**
-{{#ALLOWED_ACTIONS}}
-- ✓ {{.}}
-{{/ALLOWED_ACTIONS}}
-
-**IMPLEMENTATION AUTHORIZED:**
-- ✓ Writing functions, classes, and components
-- ✓ Creating new files and modifying existing ones
-- ✓ Implementing features described in {{SOURCE_TYPE}}
-- ✓ Writing tests for implemented code
-
-**MODE ENTRY VALIDATION:**
-Before implementing, verify:
-1. Source documents exist ({{SOURCE_DOCS}})
-2. Output assertion: "Entering IMPLEMENTATION mode. I will implement {{SOURCE_DESC}}."
-
-For complete mode documentation, see: `.clavix/instructions/core/clavix-mode.md`

package/dist/templates/slash-commands/_components/mode-headers/planning-mode.md

@@ -1,17 +0,0 @@
-## CLAVIX MODE: {{MODE_TYPE}}
-
-**You are in Clavix {{WORKFLOW_TYPE}} mode. You help {{ACTION}}, NOT implement features.**
-
-**YOUR ROLE:**
-{{#ALLOWED_ACTIONS}}
-- ✓ {{.}}
-{{/ALLOWED_ACTIONS}}
-
-**DO NOT IMPLEMENT. DO NOT IMPLEMENT. DO NOT IMPLEMENT.**
-- ✗ DO NOT write application code for the feature
-- ✗ DO NOT implement what the prompt/PRD describes
-- ✗ DO NOT generate actual components/functions
-
-**You are {{DOING_ACTION}}, not building what it describes.**
-
-For complete mode documentation, see: `.clavix/instructions/core/clavix-mode.md`

package/dist/templates/slash-commands/_components/mode-headers/self-correction.md

@@ -1,13 +0,0 @@
-## Self-Correction Protocol
-
-**DETECT**: If you find yourself:
-- Writing function/class definitions for the user's feature
-- Creating component implementations
-- Generating API endpoint code
-
-**STOP**: Immediately halt code generation
-
-**CORRECT**: Output:
-"I apologize - I was implementing instead of {{CORRECT_ACTION}}. Let me return to {{WORKFLOW_ACTION}}."
-
-**RESUME**: Return to the {{WORKFLOW_TYPE}} workflow.

package/dist/templates/slash-commands/_components/references/intent-types.md

@@ -1,39 +0,0 @@
-## Intent Types Reference
-
-Clavix detects 11 primary intent types using pattern-based analysis. This reference is synchronized with `src/core/intelligence/types.ts`.
-
-### Intent Categories
-
-| Intent | Description | Key Indicators |
-|--------|-------------|----------------|
-| **code-generation** | Writing new code or functions | "create", "build", "implement", "write" |
-| **planning** | Designing architecture or breaking down tasks | "design", "architect", "plan", "structure" |
-| **refinement** | Improving existing code or prompts | "improve", "refactor", "optimize", "enhance" |
-| **debugging** | Finding and fixing issues | "fix", "debug", "error", "issue", "bug" |
-| **documentation** | Creating docs or explanations | "document", "explain", "describe", "readme" |
-| **prd-generation** | Creating requirements documents | "PRD", "requirements", "specification", "feature spec" |
-| **testing** | Writing tests, improving test coverage | "test", "coverage", "spec", "unit test", "integration" |
-| **migration** | Version upgrades, porting code | "migrate", "upgrade", "port", "convert", "transition" |
-| **security-review** | Security audits, vulnerability checks | "security", "audit", "vulnerability", "OWASP", "CVE" |
-| **learning** | Conceptual understanding, tutorials | "explain", "how does", "tutorial", "understand" |
-| **summarization** | Extracting requirements from conversations | "summarize", "extract", "requirements from" |
-
-### Intent Detection Confidence Levels
-
-| Confidence | Meaning | Agent Behavior |
-|------------|---------|----------------|
-| 85%+ | High confidence | Proceed with detected intent |
-| 70-84% | Moderate | Show primary + secondary intent |
-| 50-69% | Low | Ask user to confirm |
-| <50% | Uncertain | Present options, ask for clarification |
-
-### Intent-Specific Patterns
-
-Different intents enable different optimization patterns:
-
-- **code-generation**: All core patterns + ErrorToleranceEnhancer
-- **planning**: StructureOrganizer, ScopeDefiner, PrerequisiteIdentifier
-- **debugging**: ErrorToleranceEnhancer, EdgeCaseIdentifier
-- **testing**: ValidationChecklistCreator, EdgeCaseIdentifier
-- **prd-generation**: PRDStructureEnforcer, CompletenessValidator
-- **summarization**: ConversationSummarizer, TopicCoherenceAnalyzer, ImplicitRequirementExtractor

package/dist/templates/slash-commands/_components/sections/file-saving-protocol.md

@@ -1,40 +0,0 @@
-## Saving the {{OUTPUT_TYPE}} (REQUIRED - v5 Agentic-First)
-
-After displaying the {{OUTPUT_DESC}}, you MUST save it using your native tools.
-
-**In v5, you save files directly - no CLI commands involved.**
-
-### Step 1: Create Directory Structure
-```bash
-mkdir -p .clavix/outputs/prompts
-```
-
-### Step 2: Generate Unique {{OUTPUT_TYPE}} ID
-Create a unique identifier using this format:
-- **Format**: `{{OUTPUT_DIR}}-YYYYMMDD-HHMMSS-<random>`
-- **Example**: `{{OUTPUT_DIR}}-20250117-143022-a3f2`
-- Use current timestamp + random 4-character suffix
-
-### Step 3: Save {{OUTPUT_TYPE}} File with Frontmatter
-Use the Write tool to create the {{OUTPUT_TYPE}} file at:
-- **Path**: `.clavix/outputs/prompts/<{{OUTPUT_TYPE}}-id>.md`
-
-**File format:**
-```markdown
----
-id: <{{OUTPUT_TYPE}}-id>
-timestamp: <ISO-8601 timestamp>
-executed: false
-originalPrompt: "<user's original text>"
----
-
-# {{OUTPUT_TYPE}}
-
-<content here>
-```
-
-### Step 4: Verify Saving Succeeded
-Confirm:
-- File exists at `.clavix/outputs/prompts/<{{OUTPUT_TYPE}}-id>.md`
-- File has valid frontmatter with id, timestamp, executed fields
-- Display success message: `✓ {{OUTPUT_TYPE}} saved: <{{OUTPUT_TYPE}}-id>.md`

package/dist/templates/slash-commands/_components/sections/intent-detection.md

@@ -1,24 +0,0 @@
-## Intent Detection
-
-Analyze what the user is trying to achieve:
-
-### Primary Intents
-- **code-generation**: Writing new code or functions
-- **planning**: Designing architecture or breaking down tasks
-- **refinement**: Improving existing code or prompts
-- **debugging**: Finding and fixing issues
-- **documentation**: Creating docs or explanations
-- **prd-generation**: Creating requirements documents
-
-### v4.0 Extended Intents
-- **testing**: Writing tests, improving coverage
-- **migration**: Version upgrades, porting code
-- **security-review**: Security audits, vulnerability checks
-- **learning**: Conceptual understanding, tutorials
-
-### Intent Characteristics
-Track these characteristics for each prompt:
-- **hasCodeContext**: Does the prompt include code snippets?
-- **hasTechnicalTerms**: Does it use specific technologies/frameworks?
-- **isOpenEnded**: Is it exploratory vs. specific?
-- **needsStructure**: Would structured output help?

package/dist/templates/slash-commands/_components/sections/pattern-visibility.md

@@ -1,122 +0,0 @@
-## Patterns Applied
-
-Show which optimization patterns were applied and their effects.
-
-### Compact Output Format
-
-```
-Patterns: [N] applied ([DEPTH] depth)
-  [PATTERN1] → [ONE-LINE EFFECT]
-  [PATTERN2] → [ONE-LINE EFFECT]
-```
-
-### Example Outputs
-
-**Standard depth optimization:**
-```
-Patterns: 4 applied (standard depth)
-  ConcisenessFilter → Removed 3 pleasantries, 2 filler phrases
-  ObjectiveClarifier → Added clear objective statement
-  StructureOrganizer → Reordered to context→requirements→output
-  ActionabilityEnhancer → Replaced 2 vague terms with specifics
-```
-
-**Comprehensive depth optimization:**
-```
-Patterns: 7 applied (comprehensive depth)
-  ConcisenessFilter → Removed 5 pleasantries
-  ObjectiveClarifier → Added objective section
-  StructureOrganizer → Reorganized into 4 sections
-  TechnicalContextEnricher → Added React 18, TypeScript context
-  CompletenessValidator → Flagged 3 missing requirements
-  DomainContextEnricher → Added best practices for React components
-  SuccessCriteriaEnforcer → Added measurable acceptance criteria
-```
-
-### Pattern Impact Indicators
-
-| Impact | Meaning | Example |
-|--------|---------|---------|
-| HIGH | Significant structural changes | "Restructured into 5 sections" |
-| MEDIUM | Moderate additions/clarifications | "Added 3 technical requirements" |
-| LOW | Minor word-level improvements | "Replaced 1 vague term" |
-
-### Available Patterns Reference
-
-**v4.12: Core Patterns (standard + comprehensive, scope='both'):**
-| Pattern | Priority | What It Does |
-|---------|----------|--------------|
-| ObjectiveClarifier | 9 | Adds clear objective/goal statement if missing |
-| AmbiguityDetector | 9 | Identifies and flags ambiguous terms |
-| StructureOrganizer | 8 | Reorders into logical flow: context→requirements→constraints→output |
-| OutputFormatEnforcer | 7 | Adds explicit output format specifications |
-| SuccessCriteriaEnforcer | 7 | Adds measurable success criteria |
-| ContextPrecisionBooster | 6 | Adds precise context when missing |
-| CompletenessValidator | 6 | Identifies and flags missing required elements |
-| TechnicalContextEnricher | 5 | Adds missing technical context (frameworks, tools, versions) |
-| StepDecomposer | 5 | Breaks complex prompts into sequential steps |
-| DomainContextEnricher | 5 | Adds domain-specific best practices |
-| ConcisenessFilter | 4 | Removes pleasantries, filler words, redundant phrases |
-| ActionabilityEnhancer | 4 | Converts vague language to specific, actionable terms |
-
-**v4.12 PRD Mode Patterns (comprehensive only):**
-| Pattern | Priority | What It Does |
-|---------|----------|--------------|
-| PRDStructureEnforcer | 9 | Ensures PRD completeness (PRD mode only) |
-| RequirementPrioritizer | 7 | Separates must-have from nice-to-have requirements |
-| SuccessMetricsEnforcer | 7 | Ensures measurable success criteria exist |
-| UserPersonaEnricher | 6 | Adds missing user context and personas |
-| DependencyIdentifier | 5 | Identifies technical and external dependencies |
-
-**v4.12 Conversational Mode Patterns (comprehensive only):**
-| Pattern | Priority | What It Does |
-|---------|----------|--------------|
-| ConversationSummarizer | 8 | Extracts structured requirements from messages |
-| TopicCoherenceAnalyzer | 6 | Detects topic shifts and multi-topic conversations |
-| ImplicitRequirementExtractor | 5 | Surfaces requirements mentioned indirectly |
-
-### Pattern Selection Logic
-
-Patterns are selected based on:
-1. **Depth**: Standard gets core patterns; comprehensive gets all
-2. **Intent**: Some patterns are intent-specific (e.g., PRDStructureEnforcer for prd-generation)
-3. **Priority**: Higher priority patterns run first (10→1)
-4. **Applicability**: Pattern checks if it can improve the prompt
-
-### Why Patterns Were Skipped
-
-In comprehensive depth, show skipped patterns with reasons:
-
-```
-Skipped patterns:
-  PRDStructureEnforcer - Intent is code-generation, not prd-generation
-  StepDecomposer - Prompt already has clear sequential steps
-```
-
-### Pattern Categories Summary
-
-```
-v4.12: Core patterns (standard + comprehensive, 12 patterns):
-  ObjectiveClarifier, AmbiguityDetector, StructureOrganizer,
-  OutputFormatEnforcer, SuccessCriteriaEnforcer, ContextPrecisionBooster,
-  CompletenessValidator, TechnicalContextEnricher, StepDecomposer,
-  DomainContextEnricher, ConcisenessFilter, ActionabilityEnhancer
-
-PRD mode (comprehensive only, 5 patterns):
-  PRDStructureEnforcer, RequirementPrioritizer, SuccessMetricsEnforcer,
-  UserPersonaEnricher, DependencyIdentifier
-
-Conversational mode (comprehensive only, 3 patterns):
-  ConversationSummarizer, TopicCoherenceAnalyzer, ImplicitRequirementExtractor
-```
-
-### Pattern Count by Depth
-
-| Depth | Patterns Available | Typical Applied |
-|------|-------------------|-----------------|
-| Standard | 12 patterns | 4-8 patterns |
-| Comprehensive | 20 patterns | 8-15 patterns |
-| PRD mode | 17 patterns | 8-12 patterns |
-| Conversational | 15 patterns | 6-10 patterns |
-
-**Note:** v4.12 has 20 total patterns after removing 7 boilerplate patterns that generated static output. Pattern selection varies by intent - some patterns only apply to specific intents (e.g., PRDStructureEnforcer only for prd-generation). Standard depth gets 12 core patterns; comprehensive adds mode-specific patterns.

package/dist/templates/slash-commands/_components/sections/quality-assessment.md

@@ -1,26 +0,0 @@
-## Quality Assessment
-
-Evaluate the prompt across {{DIMENSION_COUNT}} dimensions:
-
-- **Clarity**: Is the objective clear and unambiguous?
-- **Efficiency**: Is the prompt concise without losing critical information?
-- **Structure**: Is information organized logically?
-- **Completeness**: Are all necessary details provided?
-- **Actionability**: Can AI take immediate action on this prompt?
-{{#HAS_SPECIFICITY}}
-- **Specificity**: How concrete and precise is the prompt?
-{{/HAS_SPECIFICITY}}
-
-Score each dimension 0-100%, calculate weighted overall score.
-
-### Quality Dimension Labels
-
-When reporting improvements, use dimension labels:
-- **[Clarity]** - Objective and goal improvements
-- **[Efficiency]** - Conciseness and signal-to-noise improvements
-- **[Structure]** - Organization and flow improvements
-- **[Completeness]** - Missing details added
-- **[Actionability]** - Making prompt executable
-{{#HAS_SPECIFICITY}}
-- **[Specificity]** - Adding concrete details
-{{/HAS_SPECIFICITY}}

package/dist/templates/slash-commands/_components/sections/workflow-navigation.md

@@ -1,13 +0,0 @@
-## Workflow Navigation
-
-**You are here:** {{CURRENT_LOCATION}}
-
-**Common workflows:**
-{{#WORKFLOWS}}
-- {{.}}
-{{/WORKFLOWS}}
-
-**Related commands:**
-{{#RELATED_COMMANDS}}
-- `{{COMMAND}}` - {{DESCRIPTION}}
-{{/RELATED_COMMANDS}}

package/dist/templates/slash-commands/_components/troubleshooting/file-not-saved.md

@@ -1,19 +0,0 @@
-### Issue: {{OUTPUT_TYPE}} Not Saved
-
-**Error: Cannot create directory**
-```bash
-mkdir -p .clavix/outputs/prompts
-```
-
-**Error: Prompt file has invalid frontmatter**
-- Re-save the file with valid YAML frontmatter
-- Ensure id, timestamp, and executed fields are present in frontmatter
-
-**Error: Duplicate {{OUTPUT_TYPE}} ID**
-- Generate a new ID with a different timestamp or random suffix
-- Retry the save operation with the new ID
-
-**Error: File write permission denied**
-- Check directory permissions
-- Ensure `.clavix/` directory is writable
-- Try creating the directory structure again