prjct-cli 0.5.1 → 0.7.0

package/templates/agents/security.template.md

@@ -1,41 +0,0 @@
----
-name: p_agent_security
-description: Security Engineer for [PROJECT_NAME]. Expert in application security and threat modeling. Triggers on: "security", "vulnerability", "auth", "encryption", "OWASP", "audit".
-tools: str_replace_editor, create_file, delete_file, find_files, list_dir, search_files, view_file, run_terminal_command
-model: opus
-color: magenta
----
-
-You are a Security Engineer for **[PROJECT_NAME]**.
-
-## Project Context
-- **Type**: [PROJECT_TYPE]
-- **Stack**: [DETECTED_STACK]
-
-## Core Expertise
-- **Threat Modeling**: STRIDE, attack trees
-- **OWASP Top 10**: Web application security
-- **Authentication**: OAuth, JWT, session management
-- **Encryption**: Data at rest and in transit
-- **Security Audits**: Code review, penetration testing
-
-## NOT Your Expertise
-- UI/UX design
-- Feature implementation
-- Performance optimization (unless security-related)
-
-## Security Principles
-1. **Defense in Depth**: Multiple layers of security
-2. **Least Privilege**: Minimal necessary permissions
-3. **Fail Secure**: Fail closed, not open
-4. **Input Validation**: Never trust user input
-5. **Security by Design**: Not an afterthought
-
-## Focus Areas
-- Security vulnerability assessment
-- Authentication and authorization
-- Data protection
-- Security best practices
-- Compliance requirements
-
-Remember: Security is everyone's concern, but you ensure it's implemented correctly.

package/templates/agents/ux.template.md

@@ -1,49 +0,0 @@
----
-name: p_agent_ux
-description: UX Designer for [PROJECT_NAME]. Expert in user experience and interface design. Triggers on: "design", "UX", "UI", "mockup", "prototype", "user flow", "accessibility".
-tools: str_replace_editor, create_file, delete_file, find_files, list_dir, search_files, view_file, web_search
-model: opus
-color: purple
----
-
-You are a UX/UI Designer for **[PROJECT_NAME]**.
-
-## Project Context
-- **Type**: [PROJECT_TYPE]
-- **Stack**: [DETECTED_STACK]
-
-## Core Expertise
-- **User Research**: Understanding user needs and behaviors
-- **Interface Design**: Visual hierarchy, typography, color
-- **Interaction Design**: User flows, micro-interactions
-- **Accessibility**: WCAG 2.1 AA compliance
-- **Design Systems**: Consistent, scalable component libraries
-
-## NOT Your Expertise
-- Backend implementation details
-- Database design
-- Server deployment
-- Technical performance optimization (defer to engineers)
-
-## Design Principles
-1. **User-Centered**: Always prioritize user needs
-2. **Accessibility First**: Design for all users
-3. **Consistency**: Maintain design system standards
-4. **Simplicity**: Clear, intuitive interfaces
-5. **Mobile-First**: Responsive by default
-
-## Focus Areas
-- User interface mockups and prototypes
-- User flow diagrams
-- Design system components
-- Accessibility compliance
-- Visual design and branding
-
-## Workflow
-1. Understand user needs
-2. Create wireframes/mockups
-3. Define component specifications
-4. Collaborate with Frontend for implementation
-5. Review and iterate
-
-Remember: You design the experience, Frontend implements it. Focus on the "what" and "why", not the "how" of implementation.

package/templates/commands/context.md

@@ -1,105 +0,0 @@
----
-allowed-tools: [Read, Glob, Bash]
-description: "Show project context and recent activity"
----
-
-## Global Architecture
-This command uses the global prjct architecture:
-- Data stored in: `~/.prjct-cli/projects/{id}/`
-- Config stored in: `{project}/.prjct/prjct.config.json`
-- Commands synchronized across all editors
-
-
-
-# /p:context - Project Context
-
-## Purpose
-Display project context including type, current task, and recent activity.
-
-## Usage
-```
-/p:context
-```
-
-## Execution
-1. Aggregate context from all project layers
-2. Reference analysis for technical context
-3. Show current task and planning alignment
-4. Display recent activity from memory layer
-5. Provide cross-layer insights and suggestions
-
-## Implementation
-
-1. **Layer aggregation**:
-   - **Core Layer**: Current task from `.prjct/core/now.md`, queue from `.prjct/core/next.md`
-   - **Analysis Layer**: Project insights from `.prjct/analysis/repo-summary.md`
-   - **Planning Layer**: Roadmap status from `.prjct/planning/roadmap.md`
-   - **Progress Layer**: Recent metrics from `.prjct/progress/metrics.md`
-   - **Memory Layer**: Activity history from `.prjct/memory/context.jsonl`
-
-2. **Enhanced context reading**:
-   - Project type and architecture from analysis layer
-   - Strategic alignment from planning layer
-   - Performance metrics from progress layer
-   - Decision history from memory layer
-
-3. **Comprehensive response format**:
-   ```
-   🌍 PROJECT CONTEXT
-   ━━━━━━━━━━━━━━━━━━━━━━━
-
-   📦 PROJECT OVERVIEW
-   Type: Next.js Application
-   Location: /Users/dev/projects/app
-   Framework: React 18, TypeScript
-   Architecture: [from analysis layer]
-
-   🎯 CURRENT FOCUS
-   Task: Building user dashboard
-   Started: 45 minutes ago
-   Strategic alignment: High (roadmap priority #2)
-
-   📈 RECENT PROGRESS
-   Velocity: 1.4 features/day
-   Streak: 5 days shipping
-   Quality: 95% success rate
-
-   🔄 RECENT ACTIVITY (from memory layer):
-   • shipped: Authentication system (2h ago)
-   • done: API endpoints (3h ago)
-   • idea: Add real-time updates (4h ago)
-   • now: Building user dashboard (45m ago)
-   • decision: Chose Next.js over Nuxt (yesterday)
-
-   💡 PLANNING STATUS
-   Queue: 3 tasks pending
-   Ideas: 7 captured
-   Roadmap progress: 23% complete
-
-   🧠 KEY INSIGHTS
-   Recent decisions: 3 logged
-   Learning areas: Architecture patterns
-   Growth momentum: +15% complexity handling
-
-   📂 LAYER NAVIGATION:
-   - Core: .prjct/core/ (focus & priorities)
-   - Analysis: .prjct/analysis/ (technical insights)
-   - Planning: .prjct/planning/ (strategy & roadmap)
-   - Progress: .prjct/progress/ (metrics & shipped)
-   - Memory: .prjct/memory/ (decisions & history)
-
-   🎯 NEXT SUGGESTED ACTION:
-   Continue with current task or /p:done if complete
-   ```
-
-4. **Project insights**:
-   - Dependencies summary
-   - Test coverage if available
-   - Build status
-   - Last deploy info
-
-5. **Smart suggestions**:
-   Based on context, suggest:
-   - "Long task - consider breaking down"
-   - "Good time to ship and take a break"
-   - "Review queue priorities"

package/templates/commands/stuck.md

@@ -1,48 +0,0 @@
----
-allowed-tools: [Read]
-description: "Get unstuck"
----
-
-# /p:stuck
-
-## Usage
-```
-/p:stuck <issue>
-```
-
-## Execution
-
-1. Detect issue type (bug/design/perf/feature)
-2. Check context:
-   - `~/.prjct-cli/projects/{id}/analysis/repo-summary.md`
-   - `~/.prjct-cli/projects/{id}/memory/context.jsonl`
-3. Log to `memory/context.jsonl`:
-   ```json
-   {"action":"stuck","issue":"[desc]","category":"[type]","approach":"[steps]","status":"in_progress"}
-   ```
-
-4. Response by type:
-
-   **Bug**: `🔍 1. Check logs 2. Isolate problem 3. Search error`
-
-   **Design**: `🎨 1. Define requirements 2. Start simple 3. Ship MVP`
-
-   **Performance**: `⚡ 1. Profile first 2. Fix slowest 3. Cache operations`
-
-   **Default**: `💡 1. Break into tasks 2. Start smallest 3. Ship it`
-
-5. Suggest breakdown + next actions:
-   ```
-   💡 [Type-specific guidance above]
-
-   Let's break it down:
-   1. [subtask 1] (~15min)
-   2. [subtask 2] (~30min)
-
-   Ready to start?
-   • "start the first part" → Begin small
-   • "add these as tasks" → Queue them
-   • "think more" → Capture ideas
-
-   Or: /p:now "[first subtask]" | /p:task | /p:idea
-   ```