clavix 2.8.2 → 3.0.1

package/dist/templates/agents/copilot-instructions.md

@@ -1,18 +1,18 @@
 # Clavix Workflows for GitHub Copilot
 
-These instructions enhance GitHub Copilot's understanding of the Clavix prompt engineering framework and workflow commands available in this project.
+These instructions enhance GitHub Copilot's understanding of the Clavix universal prompt intelligence toolkit and workflow commands available in this project.
 
 ## About Clavix
 
-Clavix is a CLEAR Framework-validated prompt engineering toolkit that helps improve prompts, generate PRDs, and manage implementation workflows. The CLEAR Framework (Concise, Logical, Explicit, Adaptive, Reflective) is an academically-validated approach developed by Dr. Leo Lo at the University of New Mexico.
+Clavix is a universal prompt intelligence toolkit that helps improve prompts, generate PRDs, and manage implementation workflows. It automatically detects intent and applies quality-based optimization patterns without requiring users to learn any specific framework.
 
 ## Available Commands
 
 When working with this project, you can use the following Clavix commands:
 
 ### Prompt Improvement
-- `clavix fast "<prompt>"` - Quick CLEAR analysis (C/L/E components) with improved prompt output. CLI auto-saves; slash commands require manual saving per template instructions.
-- `clavix deep "<prompt>"` - Comprehensive CLEAR analysis (all 5 components: C/L/E/A/R) with alternatives and validation. CLI auto-saves; slash commands require manual saving per template instructions.
+- `clavix fast "<prompt>"` - Quick quality assessment (5 dimensions) with improved prompt output. CLI auto-saves; slash commands require manual saving per template instructions.
+- `clavix deep "<prompt>"` - Comprehensive analysis with alternatives, edge cases, and validation checklists. CLI auto-saves; slash commands require manual saving per template instructions.
 
 ### Strategic Planning
 - `clavix prd` - Interactive PRD generation through Socratic questioning
@@ -62,12 +62,12 @@ Clavix now automatically saves optimized prompts from fast/deep commands for lat
 
 ### Quick Prompt Improvement
 1. User provides a rough prompt
-2. Run `clavix fast "<prompt>"` for quick CLEAR-validated improvements
+2. Run `clavix fast "<prompt>"` for quick quality-based improvements
 3. Use the optimized prompt for better results
 
 ### Comprehensive Prompt Analysis
 1. User has a complex requirement
-2. Run `clavix deep "<prompt>"` for full CLEAR analysis
+2. Run `clavix deep "<prompt>"` for comprehensive analysis
 3. Review alternative variations and validation checklists
 4. Select the best approach
 
@@ -82,15 +82,15 @@ Clavix now automatically saves optimized prompts from fast/deep commands for lat
 2. Discuss requirements naturally with the user
 3. Run `clavix summarize` to extract structured requirements and prompts
 
-## CLEAR Framework Components
+## Quality Dimensions
 
-When analyzing or improving prompts, apply these CLEAR Framework principles:
+When analyzing or improving prompts, consider these 5 quality dimensions:
 
-- **[C] Concise**: Remove verbosity, pleasantries, unnecessary qualifiers
-- **[L] Logical**: Ensure coherent sequencing (context → requirements → constraints → output)
-- **[E] Explicit**: Add clear specifications for persona, format, tone, success criteria
-- **[A] Adaptive**: Provide alternative phrasings and flexible structures
-- **[R] Reflective**: Include validation checklists and quality criteria
+- **Clarity**: Is the objective clear and unambiguous?
+- **Efficiency**: Is the prompt concise without losing critical information?
+- **Structure**: Is information organized logically (context → requirements → constraints → output)?
+- **Completeness**: Are all necessary specifications provided (persona, format, tone, success criteria)?
+- **Actionability**: Can AI take immediate action on this prompt?
 
 ## Output Locations
 
@@ -103,7 +103,7 @@ Clavix stores artifacts in the `.clavix/` directory:
 ## Best Practices
 
 1. **Start with the right mode**: Use fast mode for simple prompts, deep mode for complex requirements, and PRD mode for strategic planning
-2. **Leverage CLEAR Framework**: Always consider the 5 CLEAR components when crafting prompts
+2. **Focus on quality**: Always consider the 5 quality dimensions (Clarity, Efficiency, Structure, Completeness, Actionability) when crafting prompts
 3. **Document requirements**: Use PRD workflow for significant features to ensure clear requirements
 4. **Track progress**: Use implement command to maintain structured task execution
 5. **Archive completed work**: Keep project organized by archiving finished projects
@@ -114,6 +114,6 @@ When users ask for help with prompts or requirements:
 1. Suggest running the appropriate Clavix command
 2. Explain the expected output and benefits
 3. Help interpret Clavix-generated outputs
-4. Apply CLEAR Framework principles in your responses
+4. Apply quality assessment principles in your responses
 
 This integration makes GitHub Copilot aware of Clavix workflows and can suggest using Clavix commands when appropriate.

package/dist/templates/agents/octo.md

@@ -39,35 +39,39 @@ Detect user intent from keywords and trigger appropriate workflow. Use Octofrien
 ---
 
 ### Fast Prompt Improvement Workflow
-**Trigger Keywords:** improve prompt, quick fix, make better, optimize prompt, fast improvement, CLEAR framework
+**Trigger Keywords:** improve prompt, quick fix, make better, optimize prompt, fast improvement
 
 **When to use:** User wants quick improvements to their prompt
 
 **Process:**
-1. Analyze the prompt using CLEAR Framework (C, L, E components):
-   - **[C] Conciseness**: Identify verbosity, pleasantries, unnecessary words
-   - **[L] Logic**: Check sequencing and coherent flow
-   - **[E] Explicitness**: Verify persona, format, tone, success criteria
+1. Analyze the prompt using quality assessment (5 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?
 
 2. Assess if deep analysis is needed:
    - Prompt < 20 characters?
    - Missing 3+ critical elements?
    - Contains vague words ("app", "system") without context?
-   - Low CLEAR scores (C<60%, L<60%, E<50%)?
+   - Low quality scores (Overall <65%, or any dimension <50%)?
 
    **If YES:** Recommend deep analysis instead and explain why
 
-3. Generate CLEAR-optimized structured prompt with sections:
+3. Generate optimized structured prompt with sections:
    - **Objective**: Clear, specific goal
    - **Requirements**: Detailed, actionable requirements
    - **Technical Constraints**: Technologies, performance, integrations
    - **Expected Output**: What result should look like
    - **Success Criteria**: How to measure completion
 
-4. List **CLEAR Changes Made** with component labels:
-   - [C] "Removed 15 unnecessary words"
-   - [L] "Restructured: context → requirements → output"
-   - [E] "Added explicit persona, format, tone"
+4. List **Improvements Applied** with quality dimension labels:
+   - [Efficiency] "Removed 15 unnecessary words"
+   - [Structure] "Reorganized: context → requirements → output"
+   - [Clarity] "Added explicit persona, format, tone"
+   - [Completeness] "Added missing tech stack and success criteria"
+   - [Actionability] "Converted vague goals into specific requirements"
 
 5. Present optimized prompt in code block for easy copying
 
@@ -76,28 +80,29 @@ Detect user intent from keywords and trigger appropriate workflow. Use Octofrien
 ---
 
 ### Deep Prompt Analysis Workflow
-**Trigger Keywords:** deep analysis, comprehensive review, thorough examination, full CLEAR analysis, deep dive
+**Trigger Keywords:** deep analysis, comprehensive review, thorough examination, deep dive, alternatives
 
-**When to use:** User wants comprehensive prompt analysis with all CLEAR components
+**When to use:** User wants comprehensive prompt analysis with alternatives and validation
 
 **Octofriend Tip:** This is an ideal use case for model switching. Start with a thinking model for comprehensive analysis, then switch to a faster model for formatting the final output.
 
 **Process:**
-1. Apply **Full CLEAR Framework** (C, L, E, A, R):
-   - **[C] Conciseness**: Detailed verbosity analysis
-   - **[L] Logic**: Comprehensive flow analysis
-   - **[E] Explicitness**: Complete specification check
-   - **[A] Adaptive**: Generate 3-5 alternative phrasings and structures
-   - **[R] Reflective**: Create validation checklist, identify edge cases
+1. Apply **comprehensive quality assessment** (5 dimensions):
+   - **Clarity**: Detailed ambiguity analysis
+   - **Efficiency**: Comprehensive verbosity analysis
+   - **Structure**: Complete flow and organization check
+   - **Completeness**: Thorough specification review
+   - **Actionability**: Assess immediate executability
 
-2. Provide **CLEAR Scoring** (0-100% for each component)
+2. Provide **quality scoring** (0-100% for each dimension)
 
 3. Generate multiple outputs:
-   - **Primary optimized prompt** (all CLEAR components applied)
-   - **Alternative variations** (3-5 different approaches with Adaptive component)
-   - **Validation checklist** (Reflective component - edge cases, quality criteria)
+   - **Primary optimized prompt** (all improvements applied)
+   - **Alternative approaches** (3-5 different ways to phrase/structure the request)
+   - **Alternative structures** (step-by-step, template-based, example-driven)
+   - **Validation checklist** (edge cases, quality criteria, verification steps)
 
-4. Explain **CLEAR Changes Made** for each component with examples
+4. Explain **improvements applied** for each quality dimension with examples
 
 5. Identify potential issues and mitigation strategies
 
@@ -263,7 +268,7 @@ When starting implementation with `clavix implement`:
 | Command | Use it for |
 | --- | --- |
 | `clavix init` | Rebuild `.clavix` structure and regenerate provider assets. |
-| `clavix fast` / `clavix deep` | CLEAR-based prompt improvement (quick vs. comprehensive). CLI auto-saves prompts. Slash commands require manual saving per template instructions. |
+| `clavix fast` / `clavix deep` | Quality-based prompt improvement (quick vs. comprehensive). CLI auto-saves prompts. Slash commands require manual saving per template instructions. |
 | `clavix execute` | Execute saved prompts (interactive selection or `--latest` for most recent). |
 | `clavix prompts list` | View saved prompts with lifecycle status (NEW, EXECUTED, OLD, STALE). |
 | `clavix prompts clear` | Cleanup executed/stale prompts (`--executed`, `--stale`, `--fast`, `--deep`). |
@@ -287,10 +292,10 @@ When starting implementation with `clavix implement`:
 → Use PRD Generation Workflow
 
 **User has a prompt and wants quick improvement:**
-→ Use Fast Prompt Improvement (CLEAR C, L, E)
+→ Use Fast Prompt Improvement (quality assessment with 5 dimensions)
 
 **User wants thorough analysis or mentions alternatives/edge cases:**
-→ Use Deep Analysis (Full CLEAR: C, L, E, A, R)
+→ Use Deep Analysis (comprehensive with alternatives and validation)
 → Consider model switching for optimal results
 
 **User wants to discuss/explore before committing:**
@@ -342,8 +347,8 @@ When starting implementation with `clavix implement`:
 - **Use markdown formatting** for all outputs
 - **Be conversational and supportive** - this is a collaborative process
 - **Ask follow-up questions** when requirements are vague or incomplete
-- **Apply CLEAR Framework** systematically in prompt improvement workflows
-- **Reference CLEAR components** ([C], [L], [E], [A], [R]) when explaining changes
+- **Apply quality assessment** systematically in prompt improvement workflows
+- **Reference quality dimensions** (Clarity, Efficiency, Structure, Completeness, Actionability) when explaining changes
 - **Switch models strategically** based on task complexity and thinking requirements
 - **Leverage your multi-turn capabilities** for deep exploration and synthesis
 
@@ -353,7 +358,7 @@ When starting implementation with `clavix implement`:
 
 Your goal is to help users:
 - Create clear, comprehensive PRDs through guided questioning
-- Improve prompts using CLEAR Framework principles
+- Improve prompts using universal prompt intelligence principles
 - Think through requirements systematically
 - Execute implementation plans efficiently
 - Archive completed work properly

package/dist/templates/agents/warp.md

@@ -1,6 +1,6 @@
 ## Clavix Integration for Warp
 
-Clavix helps Warp developers turn rough ideas into CLEAR, AI-ready prompts and Product Requirements Documents without leaving the terminal.
+Clavix helps Warp developers turn rough ideas into quality, AI-ready prompts and Product Requirements Documents without leaving the terminal.
 
 ### Quick start
 - Install globally: `npm install -g clavix`
@@ -9,8 +9,8 @@ Clavix helps Warp developers turn rough ideas into CLEAR, AI-ready prompts and P
 
 ### Common commands
 - `clavix init` – interactive provider setup (regenerates docs & commands)
-- `clavix fast "<prompt>"` – quick CLEAR (C/L/E) analysis and improved prompt. CLI auto-saves; slash commands need manual saving per template instructions.
-- `clavix deep "<prompt>"` – full CLEAR (C/L/E/A/R) analysis with alternatives & checklists. CLI auto-saves; slash commands need manual saving per template instructions.
+- `clavix fast "<prompt>"` – quick quality assessment (5 dimensions) and improved prompt. CLI auto-saves; slash commands need manual saving per template instructions.
+- `clavix deep "<prompt>"` – comprehensive analysis with alternatives, edge cases, and validation checklists. CLI auto-saves; slash commands need manual saving per template instructions.
 - `clavix execute [--latest]` – execute saved prompts from fast/deep. Interactive selection or `--latest` for most recent.
 - `clavix prompts list` – view all saved prompts with age/status (NEW, EXECUTED, OLD, STALE)
 - `clavix prompts clear [--executed|--stale|--fast|--deep]` – cleanup executed or old prompts

package/dist/templates/full-prd-template.hbs

@@ -81,4 +81,4 @@ The following criteria must be met for this project to be considered complete:
 
 ---
 
-*This PRD was generated by Clavix. Edit and refine as needed for your project.*
+*Generated with Clavix Planning Mode – Edit and refine as needed for your project.*

package/dist/templates/prd-questions.md

@@ -1,7 +1,7 @@
 # PRD Question Flow
 
 Generate a focused Product Requirements Document optimized for vibecoding.
-Built with CLEAR framework principles for fast iteration without losing quality.
+Built with Clavix Planning Mode for fast iteration without losing quality.
 
 ## Question 1
 

package/dist/templates/quick-prd-template.hbs

@@ -48,4 +48,4 @@ Focus on creating a well-structured, maintainable, and tested implementation.
 
 ---
 
-*Generated: {{timestamp}} | Use with AI agents for development*
+*Generated with Clavix Planning Mode: {{timestamp}} | Optimized for AI-assisted development*