cntx-ui 3.0.4 → 3.0.6

package/templates/activities/activities.json

@@ -1,219 +0,0 @@
-[
-  {
-    "title": "Create Project Bundles with Agent Assistance",
-    "description": "Set up organized bundles for a new codebase using agent assistance to analyze project structure and suggest appropriate file groupings.",
-    "desired_outcome": "Complete bundle coverage with logical groupings, clear documentation, and automated suggestions for new files. Improved context efficiency for LLM consumption.",
-    "references": [
-      ".cntx/activities/activities/create-project-bundles/README.md",
-      ".cntx/activities/activities/create-project-bundles/tasks.md",
-      ".cntx/activities/activities/create-project-bundles/progress.md"
-    ],
-    "status": "todo",
-    "tags": ["bundles", "agent-collaboration", "setup"],
-    "tasks": [
-      {
-        "title": "Project Analysis and Discovery",
-        "description": "Analyze project directory structure and identify main folders, file types, and architectural patterns.",
-        "status": "todo"
-      },
-      {
-        "title": "Bundle Strategy Design",
-        "description": "Propose initial bundle structure based on project analysis and define naming conventions.",
-        "status": "todo"
-      },
-      {
-        "title": "Bundle Configuration Implementation",
-        "description": "Create bundle definitions in .cntx/bundle-states.json and set up automatic file categorization rules.",
-        "status": "todo"
-      },
-      {
-        "title": "Documentation and Refinement",
-        "description": "Document bundle purposes, create usage guidelines, and refine structure based on testing.",
-        "status": "todo"
-      }
-    ]
-  },
-  {
-    "title": "API Audit, Refinement, and Documentation",
-    "description": "Review all existing API endpoints, refine their design for consistency and efficiency, and generate comprehensive documentation.",
-    "desired_outcome": "All API endpoints are consistent, efficient, and well-documented. API documentation is up-to-date and easily accessible.",
-    "references": [
-      ".cntx/activities/activities/api-audit/README.md",
-      ".cntx/activities/activities/api-audit/tasks.md",
-      ".cntx/activities/activities/api-audit/progress.md"
-    ],
-    "status": "todo",
-    "tags": ["general", "api"],
-    "tasks": [
-      {
-        "title": "Example",
-        "description": "lorem ipsum dolor sit amet, consectetur adipiscing elit.",
-        "status": "todo"
-      }
-    ]
-  },
-  {
-    "title": "Agent Stories: Research and Optimization",
-    "description": "Create a comprehensive research activity to systematically test and discover optimal patterns for agent interactions with cntx-ui through the .cntx directory and MCP server.",
-    "desired_outcome": "Comprehensive coverage of agent interaction scenarios, documented best practices, and an actionable plan for continuous agent testing through the 'Agent Stories Cycle'.",
-    "references": [
-      ".cntx/activities/activities/agent-stories/README.md",
-      ".cntx/activities/activities/agent-stories/tasks.md",
-      ".cntx/activities/activities/agent-stories/progress.md"
-    ],
-    "status": "todo",
-    "tags": ["general", "agent"],
-    "tasks": [
-      {
-        "title": "Current State Analysis",
-        "description": "Analyze existing agent instructions, MCP server tools, and interaction patterns.",
-        "status": "todo"
-      }
-    ]
-  },
-  {
-    "title": "Heuristics Configuration Refactor",
-    "description": "Transform hardcoded heuristics into a configurable, agent-manageable system. Extract all code categorization logic into centralized configuration with agent activity framework integration.",
-    "desired_outcome": "All heuristics are externalized to configuration, agents can automatically refine categorization rules, and the system maintains complete backward compatibility while enabling intelligent self-improvement.",
-    "references": [
-      ".cntx/activities/activities/heuristics-refactor/README.md"
-    ],
-    "status": "todo",
-    "tags": ["general", "refactor"],
-    "tasks": [
-      {
-        "title": "Extract Purpose Detection Heuristics",
-        "description": "Extract hardcoded purpose detection patterns from semantic-splitter.js to heuristics-config.json",
-        "status": "todo"
-      },
-      {
-        "title": "Extract Bundle Suggestion Logic",
-        "description": "Extract bundle suggestion heuristics from BundleList.tsx to centralized config",
-        "status": "todo"
-      },
-      {
-        "title": "Create HeuristicsManager Service",
-        "description": "Build centralized service for loading and applying heuristics with caching and validation",
-        "status": "todo"
-      },
-      {
-        "title": "Implement Heuristics API Endpoints",
-        "description": "Create REST API for reading, updating, and managing heuristics configuration",
-        "status": "todo"
-      },
-      {
-        "title": "Build Agent Activity Framework",
-        "description": "Implement activity scheduler and execution system for agent-driven heuristics refinement",
-        "status": "todo"
-      },
-      {
-        "title": "Verify Backward Compatibility",
-        "description": "Ensure all existing functionality works identically after refactor",
-        "status": "todo"
-      }
-    ]
-  },
-  {
-    "title": "VS Code Extension",
-    "description": "Adapt the existing cntx-ui tool into a VS Code extension, providing an integrated experience within the editor.",
-    "desired_outcome": "A functional VS Code extension that embeds the cntx-ui, allowing users to manage their projects without leaving the editor. The extension will share a codebase with the standalone web application.",
-    "references": [
-      ".cntx/activities/activities/vscode-extension/README.md",
-      ".cntx/activities/activities/vscode-extension/tasks.md",
-      ".cntx/activities/activities/vscode-extension/progress.md"
-    ],
-    "status": "todo",
-    "tags": ["vscode", "feature"],
-    "tasks": [
-      {
-        "title": "Project Scaffolding",
-        "description": "Set up the basic file structure for a VS Code extension, including package.json, extension.ts, and a webpack.config.js.",
-        "status": "todo"
-      },
-      {
-        "title": "Implement Webview Panel",
-        "description": "Create the command and logic to open a WebviewPanel that loads the existing web/dist/index.html.",
-        "status": "todo"
-      },
-      {
-        "title": "Create Communication Bridge",
-        "description": "Develop an abstraction layer that handles messaging between the webview and the extension host, supporting both postMessage and WebSockets.",
-        "status": "todo"
-      },
-      {
-        "title": "Implement Activation Events",
-        "description": "Configure the extension to activate when a .cntx directory is found, when the Activity Bar icon is clicked, or when a command is run.",
-        "status": "todo"
-      },
-      {
-        "title": "Add Activity Bar Icon",
-        "description": "Create an icon for the extension and configure it to appear in the VS Code Activity Bar.",
-        "status": "todo"
-      },
-      {
-        "title": "Implement Command Palette Actions",
-        "description": "Add the cntx-ui: Start Server, cntx-ui: Stop Server, and cntx-ui: Open UI commands to the Command Palette.",
-        "status": "todo"
-      },
-      {
-        "title": "Build Initial Dashboard UI",
-        "description": "Create the simple dashboard view with controls for the server, a health status indicator, and a list of bundles.",
-        "status": "todo"
-      },
-      {
-        "title": "Backend Integration",
-        "description": "Connect the dashboard UI to the reused backend logic to control the server and fetch the bundle list.",
-        "status": "todo"
-      },
-      {
-        "title": "Documentation",
-        "description": "Update the project's README.md with instructions on how to build, run, and debug the new VS Code extension.",
-        "status": "todo"
-      },
-      {
-        "title": "Packaging and Testing",
-        "description": "Create a .vsix package for the extension and test its installation and functionality in a clean VS Code environment.",
-        "status": "todo"
-      }
-    ]
-  },
-  {
-    "title": "cntx-ui Init Defaults",
-    "description": "Define and implement a comprehensive default template for the .cntx directory, established by `cntx-ui init`.",
-    "desired_outcome": "A single command initializes a fully functional .cntx directory with all necessary defaults, compatible with the UI.",
-    "references": [
-      ".cntx/activities/activities/cntx-ui-init-defaults/README.md",
-      ".cntx/activities/activities/cntx-ui-init-defaults/tasks.md",
-      ".cntx/activities/activities/cntx-ui-init-defaults/progress.md"
-    ],
-    "status": "todo",
-    "tags": ["init", "defaults", "scaffolding"],
-    "tasks": [
-      {
-        "title": "Define Default .cntx Structure & Content",
-        "description": "Create templates for config, hidden-files, semantic-cache, activities, and agent-rules.",
-        "status": "todo"
-      },
-      {
-        "title": "Extend Existing cntx-ui init Command",
-        "description": "Modify the `init` command to copy the default .cntx structure to the user's project.",
-        "status": "todo"
-      },
-      {
-        "title": "Integrate Minimal Default Activities & Agent Rules",
-        "description": "Ensure the sample activities and agent rules are correctly loaded and displayed.",
-        "status": "todo"
-      },
-      {
-        "title": "Testing & Validation",
-        "description": "Write tests for the `init` command and verify the created .cntx directory.",
-        "status": "todo"
-      },
-      {
-        "title": "Documentation & Release Preparation",
-        "description": "Update documentation and prepare for release of the new `init` functionality.",
-        "status": "todo"
-      }
-    ]
-  }
-]

package/templates/activities/lib/.markdownlint.jsonc

@@ -1,18 +0,0 @@
-{
-  // https://github.com/markdownlint/markdownlint/blob/main/docs/RULES.md
-  "default": true,
-  // Trailing spaces
-  "MD009": false,
-  // Line length (default: 80)
-  "MD013": false,
-  // Duplicate headings (e.g., nested headings)
-  "MD024": false,
-  // Ordered list item prefix
-  "MD029": {
-    "style": "ordered"
-  },
-  // Fenced code blocks should be surrounded by blank lines
-  "MD031": false,
-  // Emphasis as heading (e.g., table of contents)
-  "MD036": false
-}

package/templates/activities/lib/create-activity.mdc

@@ -1,63 +0,0 @@
----
-description: 
-globs: 
-alwaysApply: false
----
-# Rule: Generating an Activity Definition
-
-## Goal
-
-To guide an AI assistant in creating a detailed Activity Definition in Markdown format, based on an initial user prompt. The Activity should be clear, actionable, and suitable for a junior developer to understand and implement the feature or improvement for the cntx-ui project.
-
-## Process
-
-1.  **Receive Initial Prompt:** The user provides a brief description or request for a new feature, improvement, or functionality for cntx-ui.
-2.  **Ask Clarifying Questions:** Before writing the Activity, the AI *must* ask clarifying questions to gather sufficient detail. The goal is to understand the "what" and "why" of the activity, not necessarily the "how" (which the developer will figure out). Make sure to provide options in letter/number lists so I can respond easily with my selections.
-3.  **Generate Activity:** Based on the initial prompt and the user's answers to the clarifying questions, generate an Activity using the structure outlined below.
-4.  **Save Activity:** Save the generated document as `activity-[feature-name].md` inside the `.cntx/activities/[activity-name]/` directory.
-
-## Clarifying Questions (Examples)
-
-The AI should adapt its questions based on the prompt, but here are some common areas to explore:
-
-*   **Problem/Goal:** "What problem does this activity solve for cntx-ui users?" or "What is the main goal we want to achieve with this activity?"
-*   **Target User:** "Who is the primary user of this feature? (e.g., developers using cntx-ui, AI assistants, end users of bundled applications)"
-*   **Core Functionality:** "Can you describe the key actions a user should be able to perform with this feature?"
-*   **User Stories:** "Could you provide a few user stories? (e.g., As a [type of user], I want to [perform an action] so that [benefit].)"
-*   **Acceptance Criteria:** "How will we know when this activity is successfully implemented? What are the key success criteria?"
-*   **Scope/Boundaries:** "Are there any specific things this activity *should not* do (non-goals)?"
-*   **Data Requirements:** "What kind of data does this feature need to display or manipulate? (e.g., bundle configurations, file metadata, semantic chunks)"
-*   **Design/UI:** "Are there any existing design patterns in cntx-ui to follow?" or "Can you describe the desired look and feel?"
-*   **Edge Cases:** "Are there any potential edge cases or error conditions we should consider?"
-
-## Activity Structure
-
-The generated Activity should include the following sections:
-
-1.  **Introduction/Overview:** Briefly describe the activity and the problem it solves for cntx-ui. State the goal.
-2.  **Goals:** List the specific, measurable objectives for this activity.
-3.  **User Stories:** Detail the user narratives describing activity usage and benefits.
-4.  **Functional Requirements:** List the specific functionalities the activity must have. Use clear, concise language (e.g., "The system must allow users to configure bundle rules."). Number these requirements.
-5.  **Non-Goals (Out of Scope):** Clearly state what this activity will *not* include to manage scope.
-6.  **Design Considerations (Optional):** Link to existing UI components, describe UI/UX requirements, or mention relevant cntx-ui components/styles if applicable.
-7.  **Technical Considerations (Optional):** Mention any known technical constraints, dependencies, or suggestions (e.g., "Should integrate with the existing bundle management system").
-8.  **Success Metrics:** How will the success of this activity be measured? (e.g., "Improve bundle generation speed by 20%", "Reduce configuration errors by 50%").
-9.  **Open Questions:** List any remaining questions or areas needing further clarification.
-
-## Target Audience
-
-Assume the primary reader of the Activity is a **junior developer** working on cntx-ui. Therefore, requirements should be explicit, unambiguous, and avoid jargon where possible. Provide enough detail for them to understand the activity's purpose and core logic.
-
-## Output
-
-*   **Format:** Markdown (`.md`)
-*   **Location:** `.cntx/activities/activities/[activity-name]/`
-*   **Filename:** `README.md`
-
-## Final instructions
-
-1. Do NOT start implementing the Activity
-2. Make sure to ask the user clarifying questions
-3. Take the user's answers to the clarifying questions and improve the Activity
-4. Consider how this activity fits into the broader cntx-ui ecosystem of file bundling and AI development tools
-5. **REQUIRED**: After creating the activity README.md, update `.cntx/activities/activities.json` to register the new activity with proper title, description, desired_outcome, references, status, and tasks

package/templates/activities/lib/generate-tasks.mdc

@@ -1,64 +0,0 @@
----
-description: 
-globs: 
-alwaysApply: false
----
-# Rule: Generating a Task List from a PRD
-
-## Goal
-
-To guide an AI assistant in creating a detailed, step-by-step task list in Markdown format based on an existing Product Requirements Document (PRD). The task list should guide a developer through implementation.
-
-## Output
-
-- **Format:** Markdown (`.md`)
-- **Location:** `/tasks/`
-- **Filename:** `tasks-[prd-file-name].md` (e.g., `tasks-prd-user-profile-editing.md`)
-
-## Process
-
-1.  **Receive PRD Reference:** The user points the AI to a specific PRD file
-2.  **Analyze PRD:** The AI reads and analyzes the functional requirements, user stories, and other sections of the specified PRD.
-3.  **Phase 1: Generate Parent Tasks:** Based on the PRD analysis, create the file and generate the main, high-level tasks required to implement the feature. Use your judgement on how many high-level tasks to use. It's likely to be about 5. Present these tasks to the user in the specified format (without sub-tasks yet). Inform the user: "I have generated the high-level tasks based on the PRD. Ready to generate the sub-tasks? Respond with 'Go' to proceed."
-4.  **Wait for Confirmation:** Pause and wait for the user to respond with "Go".
-5.  **Phase 2: Generate Sub-Tasks:** Once the user confirms, break down each parent task into smaller, actionable sub-tasks necessary to complete the parent task. Ensure sub-tasks logically follow from the parent task and cover the implementation details implied by the PRD.
-6.  **Identify Relevant Files:** Based on the tasks and PRD, identify potential files that will need to be created or modified. List these under the `Relevant Files` section, including corresponding test files if applicable.
-7.  **Generate Final Output:** Combine the parent tasks, sub-tasks, relevant files, and notes into the final Markdown structure.
-8.  **Save Task List:** Save the generated document in the `/tasks/` directory with the filename `tasks-[prd-file-name].md`, where `[prd-file-name]` matches the base name of the input PRD file (e.g., if the input was `prd-user-profile-editing.md`, the output is `tasks-prd-user-profile-editing.md`).
-
-## Output Format
-
-The generated task list _must_ follow this structure:
-
-```markdown
-## Relevant Files
-
-- `path/to/potential/file1.ts` - Brief description of why this file is relevant (e.g., Contains the main component for this feature).
-- `path/to/file1.test.ts` - Unit tests for `file1.ts`.
-- `path/to/another/file.tsx` - Brief description (e.g., API route handler for data submission).
-- `path/to/another/file.test.tsx` - Unit tests for `another/file.tsx`.
-- `lib/utils/helpers.ts` - Brief description (e.g., Utility functions needed for calculations).
-- `lib/utils/helpers.test.ts` - Unit tests for `helpers.ts`.
-
-### Notes
-
-- Unit tests should typically be placed alongside the code files they are testing (e.g., `MyComponent.tsx` and `MyComponent.test.tsx` in the same directory).
-- Use `npx jest [optional/path/to/test/file]` to run tests. Running without a path executes all tests found by the Jest configuration.
-
-## Tasks
-
-- [ ] 1.0 Parent Task Title
-  - [ ] 1.1 [Sub-task description 1.1]
-  - [ ] 1.2 [Sub-task description 1.2]
-- [ ] 2.0 Parent Task Title
-  - [ ] 2.1 [Sub-task description 2.1]
-- [ ] 3.0 Parent Task Title (may not require sub-tasks if purely structural or configuration)
-```
-
-## Interaction Model
-
-The process explicitly requires a pause after generating parent tasks to get user confirmation ("Go") before proceeding to generate the detailed sub-tasks. This ensures the high-level plan aligns with user expectations before diving into details.
-
-## Target Audience
-
-Assume the primary reader of the task list is a **junior developer** who will implement the feature.

package/templates/activities/lib/process-task-list.mdc

@@ -1,52 +0,0 @@
----
-description: 
-globs: 
-alwaysApply: false
----
-# Task List Management
-
-Guidelines for managing task lists in markdown files to track progress on completing a PRD
-
-## Task Implementation
-- **One sub-task at a time:** Do **NOT** start the next sub‑task until you ask the user for permission and they say "yes" or "y"
-- **Completion protocol:**  
-  1. When you finish a **sub‑task**, immediately mark it as completed by changing `[ ]` to `[x]`.
-  2. If **all** subtasks underneath a parent task are now `[x]`, follow this sequence:
-    - **First**: Run the full test suite (`pytest`, `npm test`, `bin/rails test`, etc.)
-    - **Only if all tests pass**: Stage changes (`git add .`)
-    - **Clean up**: Remove any temporary files and temporary code before committing
-    - **Commit**: Use a descriptive commit message that:
-      - Uses conventional commit format (`feat:`, `fix:`, `refactor:`, etc.)
-      - Summarizes what was accomplished in the parent task
-      - Lists key changes and additions
-      - References the task number and PRD context
-      - **Formats the message as a single-line command using `-m` flags**, e.g.:
-
-        ```
-        git commit -m "feat: add payment validation logic" -m "- Validates card type and expiry" -m "- Adds unit tests for edge cases" -m "Related to T123 in PRD"
-        ```
-  3. Once all the subtasks are marked completed and changes have been committed, mark the **parent task** as completed.
-- Stop after each sub‑task and wait for the user's go‑ahead.
-
-## Task List Maintenance
-
-1. **Update the task list as you work:**
-   - Mark tasks and subtasks as completed (`[x]`) per the protocol above.
-   - Add new tasks as they emerge.
-
-2. **Maintain the "Relevant Files" section:**
-   - List every file created or modified.
-   - Give each file a one‑line description of its purpose.
-
-## AI Instructions
-
-When working with task lists, the AI must:
-
-1. Regularly update the task list file after finishing any significant work.
-2. Follow the completion protocol:
-   - Mark each finished **sub‑task** `[x]`.
-   - Mark the **parent task** `[x]` once **all** its subtasks are `[x]`.
-3. Add newly discovered tasks.
-4. Keep "Relevant Files" accurate and up to date.
-5. Before starting work, check which sub‑task is next.
-6. After implementing a sub‑task, update the file and then pause for user approval.

package/templates/agent-rules/capabilities/activities-system.md

@@ -1,147 +0,0 @@
-# Activities System Capabilities
-
-## Overview
-The activities system provides structured task management for agents, tracking progress on complex development activities through defined workflows and documentation.
-
-## When Available
-- Check for activities endpoint: `GET /api/activities`
-- Look for activities directory: `.cntx/activities/activities/`
-- Verify activity definitions and progress tracking
-
-## Core Capabilities
-
-### Activity Discovery
-**Endpoint**: `GET /api/activities`
-
-**Provides**:
-- List of all available activities
-- Activity status and progress percentages
-- Activity metadata (name, description, category)
-- Complete file contents (README, progress, tasks, notes)
-
-### Activity Execution (Future)
-**Endpoints**: 
-- `POST /api/activities/{id}/execute` (planned)
-- `POST /api/activities/{id}/stop` (planned)
-
-**Will provide**:
-- Programmatic activity execution
-- Progress monitoring and updates
-- Result collection and reporting
-
-## Activity Structure
-
-### Standard Activity Format
-Each activity contains:
-- **README.md**: Activity definition, goals, requirements
-- **progress.md**: Current status, completion tracking
-- **tasks.md**: Detailed task breakdown with priorities
-- **notes.md**: Implementation decisions, technical notes
-
-### Activity Metadata
-- **Status**: pending, in_progress, completed, failed
-- **Progress**: Percentage completion (0-100%)
-- **Category**: Type of activity (refactoring, feature, analysis, etc.)
-- **Priority**: Task importance (high, medium, low)
-
-## Activity Types and Use Cases
-
-### Development Activities
-- **Feature implementation**: Adding new functionality
-- **Refactoring**: Code organization and cleanup
-- **Migration**: Technology or pattern updates
-- **Optimization**: Performance and efficiency improvements
-
-### Analysis Activities
-- **Architecture review**: System design evaluation
-- **Code analysis**: Pattern discovery and documentation
-- **Dependency audit**: Library and framework assessment
-- **Security review**: Vulnerability analysis
-
-### Maintenance Activities
-- **Documentation updates**: Keeping docs current
-- **Test coverage**: Ensuring adequate testing
-- **Cleanup tasks**: Removing deprecated code
-- **Configuration updates**: Settings and environment management
-
-## Progress Tracking
-
-### Status Indicators
-- **✅ Completed**: Task finished successfully
-- **🚧 In Progress**: Currently being worked on
-- **⏳ Pending**: Not yet started
-- **❌ Failed**: Encountered blocking issues
-
-### Progress Calculation
-Based on task completion percentages from tasks.md:
-- Parse task status indicators
-- Calculate completion ratio
-- Update overall activity progress
-- Track progress over time
-
-### Completion Criteria
-Activities are considered complete when:
-- All defined tasks are finished
-- Success criteria are met
-- Documentation is updated
-- Results are validated
-
-## Agent Integration
-
-### Activity-Driven Development
-Agents can use activities to:
-- **Structure complex work**: Break down large tasks into manageable pieces
-- **Track progress**: Monitor completion status and identify blockers
-- **Coordinate effort**: Understand what work is planned vs in progress
-- **Learn from context**: Use existing activities as templates
-
-### Activity Creation Process
-1. **Define goals**: Clear objectives and success criteria
-2. **Break down tasks**: Specific, actionable work items
-3. **Estimate effort**: Time and complexity assessments
-4. **Track progress**: Regular status updates and milestone tracking
-5. **Document results**: Lessons learned and outcomes
-
-### Progress Monitoring
-- **Real-time updates**: Activity status reflects current work
-- **Milestone tracking**: Key progress points and deliverables
-- **Blocker identification**: Issues preventing progress
-- **Completion validation**: Ensuring work meets requirements
-
-## Integration with Other Systems
-
-### Vector Search + Activities
-- Use vector search to find activity-related code
-- Reference activities in code discovery and explanation
-- Connect implementation work to activity goals
-
-### Bundle System + Activities
-- Scope activities by bundle boundaries
-- Use bundle organization to plan activity tasks
-- Track activity impact across bundle boundaries
-
-## Performance Characteristics
-
-### Speed
-- **Activity listing**: ~30ms
-- **Activity details**: ~50ms (includes file contents)
-- **Token efficiency**: High (structured, relevant content)
-
-### Use Cases
-- **Project planning**: Understanding planned and ongoing work
-- **Context switching**: Quickly understanding current development state
-- **Progress reporting**: Communicating status to stakeholders
-- **Knowledge transfer**: Sharing implementation context and decisions
-
-## Best Practices
-
-### Activity-Aware Assistance
-- **Check activity context** when helping with development tasks
-- **Reference related activities** when explaining code or suggesting changes
-- **Respect activity boundaries** and existing work in progress
-- **Contribute to activity documentation** when making related changes
-
-### Integration Patterns
-- **Planning**: Activities → Bundle scope → Vector search → Implementation
-- **Execution**: Activity tasks → Code discovery → Implementation → Progress update
-- **Review**: Activity completion → Validation → Documentation → Lessons learned