prjct-cli 0.4.9 → 0.5.0

package/templates/workflows/context.md

@@ -1,72 +0,0 @@
----
-title: prjct context
-invocable_name: p:context
-description: Show project context and recent activity using global prjct architecture
----
-
-# Steps
-
-1. Read project config from `.prjct/prjct.config.json`
-2. Extract all metadata: projectId, dataPath, author, timestamps
-3. Read recent actions from `~/.prjct-cli/projects/{projectId}/memory/context.jsonl` (last 10)
-4. Read current task from `~/.prjct-cli/projects/{projectId}/core/now.md`
-5. Read project context from `~/.prjct-cli/projects/{projectId}/core/context.md`
-6. Calculate summary statistics
-7. Format and display comprehensive context
-
-# Response Format
-
-```
-📁 Project Context
-
-🆔 Project: {project-id}
-👤 Author: {name} ({github-username})
-📧 Email: {email}
-📍 Project Path: {absolute-path}
-💾 Data Location: ~/.prjct-cli/projects/{id}/
-
-📊 Current State:
-🎯 Focus: {current task or "No task set"}
-📝 Queued: X tasks
-💡 Ideas: Y ideas captured
-🚀 Shipped: Z features (A this week)
-
-🕒 Recent Activity (Last 10 Actions):
-- {timestamp} | {author}: {action 1}
-- {timestamp} | {author}: {action 2}
-- {timestamp} | {author}: {action 3}
-- {timestamp} | {author}: {action 4}
-- {timestamp} | {author}: {action 5}
-- {timestamp} | {author}: {action 6}
-- {timestamp} | {author}: {action 7}
-- {timestamp} | {author}: {action 8}
-- {timestamp} | {author}: {action 9}
-- {timestamp} | {author}: {action 10}
-
-⏱️  Session Info:
-- Initialized: {created timestamp}
-- Last Activity: {lastSync timestamp}
-- Active Days: X days
-
-🔧 Configuration:
-- Version: 0.2.1
-- Global Architecture: Enabled
-- Multi-Editor Sync: Active
-```
-
-# Action Types in Memory Log
-
-Log entries include:
-- Task changes: now, done
-- Feature ships: ship
-- Idea captures: idea
-- Context updates: context
-- Progress checks: recap, progress
-
-# Global Architecture Notes
-
-- **Config Location**: `{project}/.prjct/prjct.config.json`
-- **Memory Location**: `~/.prjct-cli/projects/{id}/memory/context.jsonl`
-- **Context File**: `~/.prjct-cli/projects/{id}/core/context.md`
-- **Author Tracking**: Every action includes author for team visibility
-- **Use Case**: Team coordination, session restoration, debugging

package/templates/workflows/design.md

@@ -1,88 +0,0 @@
----
-title: prjct design
-invocable_name: p:design
-description: Design system architecture, APIs, and component interfaces
----
-
-# Steps
-
-1. Read project config from `.prjct/prjct.config.json`
-2. Extract `projectId` and `author` from config
-3. Parse design target and type (architecture, api, component, database, flow)
-4. Generate appropriate ASCII diagrams and visual representations
-5. Create technical specifications with technology stack and patterns
-6. Generate implementation templates and interfaces
-7. Save designs to `~/.prjct-cli/projects/{id}/designs/` directory
-8. Display formatted design with overview, specs, and implementation guide
-9. Link designs to tasks and track implementation progress
-10. Log design creation to memory with author and timestamp
-
-# Response Format
-
-```
-🎨 ✨ Design Complete! ✨ 🎨
-
-📐 Design: [Target Name]
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-🏗️ Architecture Overview:
-[ASCII diagram or description]
-
-📋 Technical Specifications:
-• Technology Stack: [stack details]
-• Design Patterns: [patterns used]
-• Key Components: [component list]
-
-📦 Implementation Guide:
-1. Set up project structure
-2. Implement core models
-3. Build API endpoints
-4. Create UI components
-
-📁 Files Created:
-• ~/.prjct-cli/projects/{id}/designs/[target]-architecture.md
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-✅ Design ready for implementation!
-
-💡 Next: /p:now "Implement [target]"
-```
-
-# Design Types
-
-### Architecture
-- System architecture diagrams
-- Component relationships
-- Data flow and communication patterns
-- Scalability considerations
-
-### API
-- Endpoint specifications
-- Request/response schemas
-- Authentication and authorization
-- Rate limiting and caching
-
-### Component
-- Component interfaces
-- Props and state management
-- Lifecycle and hooks
-- Styling and theming
-
-### Database
-- Schema design
-- Entity relationships
-- Indexing strategy
-- Migration plans
-
-### Flow
-- User journey diagrams
-- State machine flows
-- Process workflows
-- Integration flows
-
-# Global Architecture Notes
-
-- **Data Location**: `~/.prjct-cli/projects/{id}/designs/`
-- **Config Location**: `{project}/.prjct/prjct.config.json`
-- **Author Tracking**: All designs logged with author information
-- **Design Versioning**: Designs linked to tasks for implementation tracking

package/templates/workflows/done.md

@@ -1,20 +0,0 @@
----
-title: prjct done
-invocable_name: p:done
-description: Complete task
----
-
-# Steps
-
-1. Get projectId + author from `.prjct/prjct.config.json`
-2. Read + calculate duration from `~/.prjct-cli/projects/{id}/core/now.md`
-3. Clear `core/now.md`
-4. Update `progress/metrics.md`
-5. Log to `memory/context.jsonl` with author + duration
-6. Check `core/next.md` for next task
-7. Response:
-   ```
-   ✅ {task} ({duration})
-   Next: {task}
-   → /p:now {next}
-   ```

package/templates/workflows/fix.md

@@ -1,201 +0,0 @@
----
-title: prjct fix
-invocable_name: p:fix
-description: Quick troubleshooting and automatic fixes using global prjct architecture
----
-
-# Steps
-
-1. Read project config from `.prjct/prjct.config.json`
-2. Extract `projectId` and `author` from config
-3. Parse issue description from arguments
-4. Analyze problem type:
-   - Build/compilation errors
-   - Test failures
-   - Runtime errors
-   - Configuration issues
-   - Dependency problems
-5. Read project context from `~/.prjct-cli/projects/{projectId}/analysis/repo-summary.md`
-6. Read recent activity from `~/.prjct-cli/projects/{projectId}/memory/context.jsonl`
-7. Identify potential causes and solutions
-8. Apply automatic fixes where possible
-9. Provide manual fix instructions for complex issues
-10. Log fix attempt to memory
-11. Display results and next steps
-
-# Response Format
-
-```
-🔧 Quick Fix: {issue-description}
-
-🔍 Diagnosis:
-Problem Type: {error-type}
-Location: {file-or-component}
-Severity: {High/Medium/Low}
-
-{if-automatic-fix-available}
-✅ Auto-Fix Applied:
-
-Changes Made:
-- {change-1}
-- {change-2}
-- {change-3}
-
-Verification:
-{run-verification-command}
-
-Status: {Success/Partial/Failed}
-{endif}
-
-{if-manual-fix-needed}
-🛠️  Manual Fix Required:
-
-Steps to Fix:
-1. {step-1}
-2. {step-2}
-3. {step-3}
-
-Why This Fix:
-{explanation-of-the-fix}
-
-Verification:
-{verification-commands}
-{endif}
-
-📚 Related Resources:
-- {documentation-link}
-- {stack-overflow-link}
-- {similar-issue-in-memory}
-
-💡 Prevention:
-{how-to-avoid-this-issue-in-future}
-
-{if-fixed}
-✅ Issue Resolved!
-Ready to continue? Use /p:now
-{endif}
-
-{if-not-fixed}
-🤔 Still having issues?
-- Get more help: /p:stuck "{detailed-description}"
-- Save for later: /p:idea "Investigate {issue}"
-{endif}
-```
-
-# Common Fixes
-
-## Build Errors
-
-**Missing Dependencies**:
-```
-Auto-Fix: npm install / yarn install
-Verification: npm run build
-```
-
-**Type Errors**:
-```
-Analysis: Check type definitions
-Manual Fix: Add type imports or fix type mismatches
-```
-
-**Import Errors**:
-```
-Auto-Fix: Update import paths
-Verification: Check compilation
-```
-
-## Test Failures
-
-**Outdated Snapshots**:
-```
-Auto-Fix: npm test -- -u
-Verification: Run tests again
-```
-
-**Missing Mocks**:
-```
-Manual Fix: Add mock definitions
-Guide: Provide mock template
-```
-
-**Async Issues**:
-```
-Analysis: Identify async/await problems
-Manual Fix: Add proper async handling
-```
-
-## Runtime Errors
-
-**Environment Variables**:
-```
-Auto-Check: .env file exists
-Manual Fix: Add missing variables
-Template: Provide .env.example
-```
-
-**API Errors**:
-```
-Analysis: Check endpoint and auth
-Debug Steps: Test with curl/Postman
-Fix: Update API configuration
-```
-
-## Configuration Issues
-
-**Linter Errors**:
-```
-Auto-Fix: npm run lint -- --fix
-Verification: Check linter output
-```
-
-**Formatting**:
-```
-Auto-Fix: npm run format
-Apply: Prettier/ESLint auto-fix
-```
-
-## Dependency Problems
-
-**Version Conflicts**:
-```
-Analysis: Check package.json
-Resolution: Update peer dependencies
-Command: npm install --legacy-peer-deps
-```
-
-**Lock File Issues**:
-```
-Auto-Fix: Remove lock file, reinstall
-Fresh Install: npm ci
-```
-
-# Fix Strategies
-
-1. **Identify Root Cause**: Don't just fix symptoms
-2. **Try Safe Fixes First**: Non-destructive approaches
-3. **Verify Each Fix**: Test before moving on
-4. **Document Solution**: Log to memory for future reference
-5. **Prevent Recurrence**: Suggest preventive measures
-
-# Safety Protocols
-
-- **Backup First**: Suggest git commit before major fixes
-- **Incremental**: Apply one fix at a time
-- **Reversible**: Provide rollback instructions
-- **Tested**: Verify each fix works
-
-# Integration with Workflow
-
-- If fix takes >15min, suggest `/p:task "Fix {issue}"`
-- Log successful fixes for pattern recognition
-- Update project analysis if configuration changes
-- Suggest `/p:stuck` if automatic fix fails
-
-# Global Architecture Notes
-
-- **Project Analysis**: `~/.prjct-cli/projects/{id}/analysis/repo-summary.md`
-- **Recent History**: `~/.prjct-cli/projects/{id}/memory/context.jsonl`
-- **Config Source**: `{project}/.prjct/prjct.config.json`
-- **Memory Logging**: Record all fix attempts and outcomes
-- **Pattern Learning**: Build knowledge base of common fixes
-- **Use Case**: Rapid problem resolution, reducing debugging time

package/templates/workflows/git.md

@@ -1,192 +0,0 @@
----
-title: prjct git
-invocable_name: p:git
-description: Smart git operations with prjct context using global prjct architecture
----
-
-# Steps
-
-1. Read project config from `.prjct/prjct.config.json`
-2. Extract `projectId` and `author` from config
-3. Parse git subcommand and arguments
-4. Read current task from `~/.prjct-cli/projects/{projectId}/core/now.md`
-5. Read recent activity from `~/.prjct-cli/projects/{projectId}/memory/context.jsonl`
-6. Execute git operation with context-aware behavior
-7. Log git action to memory
-8. Display result with workflow suggestions
-
-# Supported Operations
-
-## /p:git commit [message]
-Smart commit with context-aware message generation
-
-**Without message**:
-- Analyze staged changes
-- Read current task for context
-- Generate meaningful commit message
-- Preview and confirm
-
-**With message**:
-- Use provided message
-- Add task context footer
-- Execute commit
-
-## /p:git status
-Show git status with prjct context
-
-**Output**:
-- Standard git status
-- Current prjct task
-- Suggest next actions
-
-## /p:git push
-Push changes with progress tracking
-
-**Process**:
-- Execute git push
-- Update shipped features if appropriate
-- Log to memory
-- Suggest celebration with /p:ship
-
-## /p:git sync
-Full sync workflow: pull, commit, push
-
-**Process**:
-- Pull latest changes
-- Show conflicts if any
-- Auto-commit with context if no conflicts
-- Push to remote
-- Update prjct state
-
-# Response Formats
-
-## commit
-```
-📝 Git Commit
-
-Current Task: {task-from-now.md}
-
-Staged Changes:
-M  {file1}
-M  {file2}
-A  {file3}
-
-Generated Message:
-{context-aware-commit-message}
-
-Related to: {task-description}
-
-✅ Committed: {commit-hash}
-
-Next Steps:
-- Push changes: /p:git push
-- Ship feature: /p:ship "{feature-name}"
-- Move to next task: /p:done
-```
-
-## status
-```
-📊 Git Status
-
-On branch: {branch}
-Your branch is {ahead/behind/up-to-date}
-
-Changes staged:
-M  {file1}
-M  {file2}
-
-Changes not staged:
-M  {file3}
-
-Untracked files:
-   {file4}
-
-🎯 Current Task: {task-from-now.md}
-
-💡 Suggestions:
-- Ready to commit? /p:git commit
-- Review changes: git diff
-- Stage all: git add .
-```
-
-## push
-```
-🚀 Git Push
-
-Pushing to origin/{branch}...
-
-✅ Pushed successfully!
-{commit-count} commits pushed
-
-📈 Consider:
-{if-significant-work}
-- Ship this feature: /p:ship "{feature-name}"
-- Update progress: /p:progress
-{endif}
-
-- Mark task done: /p:done
-- Start next task: /p:now
-```
-
-## sync
-```
-🔄 Git Sync
-
-1. ⬇️  Pulling latest changes...
-   ✅ {changes} changes pulled
-
-2. 📝 Staging local changes...
-   ✅ {files} files staged
-
-3. 💾 Committing...
-   ✅ Committed: {hash}
-   Message: {auto-generated-message}
-
-4. ⬆️  Pushing to remote...
-   ✅ Pushed successfully!
-
-🎯 Current Task: {task}
-
-All synced! Keep building! 🚀
-```
-
-# Context-Aware Commit Messages
-
-Message generation considers:
-- Current task from now.md
-- Recent actions from memory
-- Changed files and patterns
-- Conventional commit types
-
-Format:
-```
-{type}: {short-description}
-
-{body-explaining-changes}
-
-Task: {current-task-context}
-Author: {author-from-config}
-```
-
-Types: feat, fix, docs, refactor, test, chore, style, perf
-
-# Smart Suggestions
-
-Based on changes:
-- **Multiple features**: "Consider splitting into separate commits"
-- **Breaking changes**: "Update version, add migration notes"
-- **Tests added**: "Great! Test coverage improved"
-- **Docs updated**: "Documentation up to date"
-
-Based on prjct state:
-- **Task complete**: "Use /p:done and /p:ship"
-- **Long-running task**: "Make checkpoint commit?"
-- **Many uncommitted changes**: "Commit frequently for safety"
-
-# Global Architecture Notes
-
-- **Current Task**: `~/.prjct-cli/projects/{id}/core/now.md` - Provides commit context
-- **Memory Logging**: `~/.prjct-cli/projects/{id}/memory/context.jsonl` - Records git actions
-- **Author Info**: From `{project}/.prjct/prjct.config.json`
-- **Integration**: Seamless connection between code changes and task tracking
-- **Use Case**: Context-aware version control, better commit messages, workflow integration

package/templates/workflows/help.md

@@ -1,13 +0,0 @@
----
-title: prjct help
-invocable_name: p:help
-description: Interactive guide
----
-
-# Steps
-
-1. Display interactive menu with natural language options
-2. Wait for user response
-3. Detect intent from message
-4. Execute corresponding command or provide guidance
-5. Response includes menu above

package/templates/workflows/idea.md

@@ -1,22 +0,0 @@
----
-title: prjct idea
-invocable_name: p:idea
-description: Quick capture
----
-
-# Steps
-
-1. Get projectId + author from `.prjct/prjct.config.json`
-2. Append to `~/.prjct-cli/projects/{id}/planning/ideas.md` + timestamp
-3. If has action verbs → add to `core/next.md`
-4. Log to `memory/context.jsonl` with author
-5. Response:
-   ```
-   💡 {idea}
-   → Added to queue
-   ```
-   Or:
-   ```
-   💡 {idea}
-   → Saved to backlog
-   ```

package/templates/workflows/init.md

@@ -1,80 +0,0 @@
----
-title: prjct init
-invocable_name: p:init
-description: Initialize prjct in current project with global architecture
----
-
-# Steps
-
-1. Check if project already initialized (`.prjct/prjct.config.json` exists)
-2. If exists, display current configuration and exit
-3. Generate unique project ID from path hash
-4. Detect author information:
-   - Try GitHub CLI: `gh api user` for username
-   - Fallback to git config: `git config user.name` and `git config user.email`
-5. Create global directory structure in `~/.prjct-cli/projects/{id}/`:
-   - `core/` - now.md, next.md, context.md
-   - `progress/` - shipped.md, metrics.md
-   - `planning/` - ideas.md, roadmap.md
-   - `analysis/` - repo-summary.md
-   - `memory/` - context.jsonl
-6. Create local config at `.prjct/prjct.config.json` with:
-   - version: "0.2.1"
-   - projectId
-   - dataPath
-   - author info
-   - timestamps
-7. Detect installed AI editors (Claude Code, Cursor, Codex, Windsurf)
-8. Install commands in all detected editors
-9. Display success message with next steps
-
-# Response Format
-
-```
-✅ prjct initialized successfully!
-
-🆔 Project ID: {hash-id}
-👤 Author: {name} ({github})
-💾 Data location: ~/.prjct-cli/projects/{id}/
-
-📦 Commands installed in:
-- ✓ Claude Code (~/.claude/commands/p/)
-- ✓ Cursor AI (~/.cursor/commands/p/)
-- ✓ OpenAI Codex (AGENTS.md)
-- ✓ Windsurf/Codeium (.windsurf/workflows/)
-
-🚀 Ready to start! Try:
-- /p:now {task} - Set your current focus
-- /p:idea {text} - Capture quick ideas
-- /p:recap - See project overview
-```
-
-# Global Architecture Created
-
-```
-~/.prjct-cli/projects/{id}/
-├── core/
-│   ├── now.md (empty)
-│   ├── next.md (template)
-│   └── context.md (project info)
-├── progress/
-│   ├── shipped.md (empty)
-│   └── metrics.md (initial stats)
-├── planning/
-│   ├── ideas.md (empty)
-│   └── roadmap.md (template)
-├── analysis/
-│   └── repo-summary.md (generated)
-└── memory/
-    └── context.jsonl (init log)
-
-.prjct/
-└── prjct.config.json (project config)
-```
-
-# Error Handling
-
-- If `.prjct/` exists but corrupted: Offer migration
-- If author detection fails: Prompt for manual input
-- If directory creation fails: Check permissions
-- If editor installation fails: Continue with warning