prjct-cli 1.22.0 → 1.24.0

package/templates/analysis/patterns.md

@@ -1,60 +0,0 @@
----
-allowed-tools: [Read, Glob, Grep]
-description: 'Analyze code patterns and conventions'
----
-
-# Code Pattern Analysis
-
-## Detection Steps
-
-1. **Structure** (5-10 files): File org, exports, modules
-2. **Patterns**: SOLID, DRY, factory/singleton/observer
-3. **Conventions**: Naming, style, error handling, async
-4. **Anti-patterns**: God class, spaghetti, copy-paste, magic numbers
-5. **Performance**: Memoization, N+1 queries, leaks
-
-## Output: analysis/patterns.md
-
-```markdown
-# Code Patterns - {Project}
-
-> Generated: {GetTimestamp()}
-
-## Patterns Detected
-- **{Pattern}**: {Where} - {Example}
-
-## SOLID Compliance
-| Principle | Status | Evidence |
-|-----------|--------|----------|
-| Single Responsibility | ✅/⚠️/❌ | {evidence} |
-| Open/Closed | ✅/⚠️/❌ | {evidence} |
-| Liskov Substitution | ✅/⚠️/❌ | {evidence} |
-| Interface Segregation | ✅/⚠️/❌ | {evidence} |
-| Dependency Inversion | ✅/⚠️/❌ | {evidence} |
-
-## Conventions (MUST FOLLOW)
-- Functions: {camelCase/snake_case}
-- Classes: {PascalCase}
-- Files: {kebab-case/camelCase}
-- Quotes: {single/double}
-- Async: {async-await/promises}
-
-## Anti-Patterns ⚠️
-
-### High Priority
-1. **{Issue}**: {file:line} - Fix: {action}
-
-### Medium Priority
-1. **{Issue}**: {file:line} - Fix: {action}
-
-## Recommendations
-1. {Immediate action}
-2. {Best practice}
-```
-
-## Rules
-
-1. Check patterns.md FIRST before writing code
-2. Match conventions exactly
-3. NEVER introduce anti-patterns
-4. Warn if asked to violate patterns

package/templates/antigravity/SKILL.md

@@ -1,39 +0,0 @@
----
-name: prjct
-description: Project context layer for AI coding agents. Use when user says "p. sync", "p. task", "p. done", "p. ship", or asks about project context, tasks, shipping features, or project state management.
----
-
-# prjct - Context Layer for AI Agents
-
-You are using **prjct**, a context layer for AI coding agents.
-
-## Load Full Instructions
-
-1. Run: `npm root -g` to get the npm global root
-2. Read: `{npmRoot}/prjct-cli/templates/global/ANTIGRAVITY.md`
-3. Follow those instructions for ALL `p. <command>` requests
-
-## Quick Reference
-
-| Command | Action |
-|---------|--------|
-| `p. sync` | Analyze project, generate agents |
-| `p. task "..."` | Start a task |
-| `p. done` | Complete subtask |
-| `p. ship` | Ship with PR + version |
-| `p. pause` | Pause current task |
-| `p. resume` | Resume paused task |
-
-## Critical Rule
-
-**PLAN BEFORE ACTION**: For ANY prjct command, you MUST:
-1. Create a plan showing what will be done
-2. Wait for user approval
-3. Only then execute
-
-Never skip the plan step. This is non-negotiable.
-
-## Note
-
-This skill auto-regenerates with `p. sync` if deleted.
-Full instructions are in the npm package (always up-to-date).

package/templates/architect/discovery.md

@@ -1,67 +0,0 @@
----
-name: architect-discovery
-description: Discovery phase for architecture generation
-allowed-tools: [Read, AskUserQuestion]
----
-
-# Discovery Phase
-
-Conduct discovery for the given idea to understand requirements and constraints.
-
-## Input
-- Idea: {{idea}}
-- Context: {{context}}
-
-## Discovery Steps
-
-1. **Understand the Problem**
-   - What problem does this solve?
-   - Who experiences this problem?
-   - How critical is it?
-
-2. **Identify Target Users**
-   - Who are the primary users?
-   - What are their goals?
-   - What's their technical level?
-
-3. **Define Constraints**
-   - Budget limitations?
-   - Timeline requirements?
-   - Team size?
-   - Regulatory needs?
-
-4. **Set Success Metrics**
-   - How will we measure success?
-   - What's the MVP threshold?
-   - Key performance indicators?
-
-## Output Format
-
-Return structured discovery:
-```json
-{
-  "problem": {
-    "statement": "...",
-    "painPoints": ["..."],
-    "impact": "high|medium|low"
-  },
-  "users": {
-    "primary": { "persona": "...", "goals": ["..."] },
-    "secondary": [...]
-  },
-  "constraints": {
-    "budget": "...",
-    "timeline": "...",
-    "teamSize": 1
-  },
-  "successMetrics": {
-    "primary": "...",
-    "mvpThreshold": "..."
-  }
-}
-```
-
-## Guidelines
-- Ask clarifying questions if needed
-- Be realistic about constraints
-- Focus on MVP scope

package/templates/architect/phases.md

@@ -1,59 +0,0 @@
----
-name: architect-phases
-description: Determine which architecture phases are needed
-allowed-tools: [Read]
----
-
-# Architecture Phase Selection
-
-Analyze the idea and context to determine which phases are needed.
-
-## Input
-- Idea: {{idea}}
-- Discovery results: {{discovery}}
-
-## Available Phases
-
-1. **discovery** - Problem definition, users, constraints
-2. **user-flows** - User journeys and interactions
-3. **domain-modeling** - Entities and relationships
-4. **api-design** - API contracts and endpoints
-5. **architecture** - System components and patterns
-6. **data-design** - Database schema and storage
-7. **tech-stack** - Technology choices
-8. **roadmap** - Implementation plan
-
-## Phase Selection Rules
-
-**Always include**:
-- discovery (foundation)
-- roadmap (execution plan)
-
-**Include if building**:
-- user-flows: Has UI/UX
-- domain-modeling: Has data entities
-- api-design: Has backend API
-- architecture: Complex system
-- data-design: Needs database
-- tech-stack: Greenfield project
-
-**Skip if**:
-- Simple script: Skip most phases
-- Frontend only: Skip api-design, data-design
-- CLI tool: Skip user-flows
-- Existing stack: Skip tech-stack
-
-## Output Format
-
-Return array of needed phases:
-```json
-{
-  "phases": ["discovery", "domain-modeling", "api-design", "roadmap"],
-  "reasoning": "Simple CRUD app needs data model and API"
-}
-```
-
-## Guidelines
-- Don't over-architect
-- Match complexity to project
-- MVP first, expand later

package/templates/checklists/architecture.md

@@ -1,28 +0,0 @@
-# Architecture Checklist
-
-> Applies to ANY system architecture
-
-## Design Principles
-- [ ] Clear separation of concerns
-- [ ] Loose coupling between components
-- [ ] High cohesion within modules
-- [ ] Single source of truth for data
-- [ ] Explicit dependencies (no hidden coupling)
-
-## Scalability
-- [ ] Stateless where possible
-- [ ] Horizontal scaling considered
-- [ ] Bottlenecks identified
-- [ ] Caching strategy defined
-
-## Resilience
-- [ ] Failure modes documented
-- [ ] Graceful degradation planned
-- [ ] Recovery procedures defined
-- [ ] Circuit breakers where needed
-
-## Maintainability
-- [ ] Clear boundaries between layers
-- [ ] Easy to test in isolation
-- [ ] Configuration externalized
-- [ ] Logging and observability built-in

package/templates/checklists/code-quality.md

@@ -1,28 +0,0 @@
-# Code Quality Checklist
-
-> Universal principles for ANY programming language
-
-## Universal Principles
-- [ ] Single Responsibility: Each unit does ONE thing well
-- [ ] DRY: No duplicated logic (extract shared code)
-- [ ] KISS: Simplest solution that works
-- [ ] Clear naming: Self-documenting identifiers
-- [ ] Consistent patterns: Match existing codebase style
-
-## Error Handling
-- [ ] All error paths handled gracefully
-- [ ] Meaningful error messages
-- [ ] No silent failures
-- [ ] Proper resource cleanup (files, connections, memory)
-
-## Edge Cases
-- [ ] Null/nil/None handling
-- [ ] Empty collections handled
-- [ ] Boundary conditions tested
-- [ ] Invalid input rejected early
-
-## Code Organization
-- [ ] Functions/methods are small and focused
-- [ ] Related code grouped together
-- [ ] Clear module/package boundaries
-- [ ] No circular dependencies

package/templates/checklists/data.md

@@ -1,33 +0,0 @@
-# Data Checklist
-
-> Applies to: SQL, NoSQL, GraphQL, File storage, Caching
-
-## Data Integrity
-- [ ] Schema/structure defined
-- [ ] Constraints enforced
-- [ ] Transactions used appropriately
-- [ ] Referential integrity maintained
-
-## Query Performance
-- [ ] Indexes on frequent queries
-- [ ] N+1 queries eliminated
-- [ ] Query complexity analyzed
-- [ ] Pagination for large datasets
-
-## Data Operations
-- [ ] Migrations versioned and reversible
-- [ ] Backup and restore tested
-- [ ] Data validation at boundary
-- [ ] Soft deletes considered (if applicable)
-
-## Caching
-- [ ] Cache invalidation strategy defined
-- [ ] TTL values appropriate
-- [ ] Cache warming considered
-- [ ] Cache hit/miss monitored
-
-## Data Privacy
-- [ ] PII identified and protected
-- [ ] Data anonymization where needed
-- [ ] Audit trail for sensitive data
-- [ ] Data deletion procedures defined

package/templates/checklists/documentation.md

@@ -1,33 +0,0 @@
-# Documentation Checklist
-
-> Applies to ALL projects
-
-## Essential Docs
-- [ ] README with quick start
-- [ ] Installation instructions
-- [ ] Configuration options documented
-- [ ] Common use cases shown
-
-## Code Documentation
-- [ ] Public APIs documented
-- [ ] Complex logic explained
-- [ ] Architecture decisions recorded (ADRs)
-- [ ] Diagrams for complex flows
-
-## Operational Docs
-- [ ] Deployment process documented
-- [ ] Troubleshooting guide
-- [ ] Runbooks for common issues
-- [ ] Changelog maintained
-
-## API Documentation
-- [ ] All endpoints documented
-- [ ] Request/response examples
-- [ ] Error codes explained
-- [ ] Authentication documented
-
-## Maintenance
-- [ ] Docs updated with code changes
-- [ ] Version-specific documentation
-- [ ] Broken links checked
-- [ ] Examples tested and working

package/templates/checklists/infrastructure.md

@@ -1,33 +0,0 @@
-# Infrastructure Checklist
-
-> Applies to: Cloud, On-prem, Hybrid, Edge
-
-## Deployment
-- [ ] Infrastructure as Code (Terraform, Pulumi, CloudFormation, etc.)
-- [ ] Reproducible environments
-- [ ] Rollback strategy defined
-- [ ] Blue-green or canary deployment option
-
-## Observability
-- [ ] Logging strategy defined
-- [ ] Metrics collection configured
-- [ ] Alerting thresholds set
-- [ ] Distributed tracing (if applicable)
-
-## Security
-- [ ] Secrets management (not in code)
-- [ ] Network segmentation
-- [ ] Least privilege access
-- [ ] Encryption at rest and in transit
-
-## Reliability
-- [ ] Backup strategy defined
-- [ ] Disaster recovery plan
-- [ ] Health checks configured
-- [ ] Auto-scaling rules (if applicable)
-
-## Cost Management
-- [ ] Resource sizing appropriate
-- [ ] Unused resources identified
-- [ ] Cost monitoring in place
-- [ ] Budget alerts configured

package/templates/checklists/performance.md

@@ -1,33 +0,0 @@
-# Performance Checklist
-
-> Applies to: Backend, Frontend, Mobile, Database
-
-## Analysis
-- [ ] Bottlenecks identified with profiling
-- [ ] Baseline metrics established
-- [ ] Performance budgets defined
-- [ ] Benchmarks before/after changes
-
-## Optimization Strategies
-- [ ] Algorithmic complexity reviewed (O(n) vs O(n²))
-- [ ] Appropriate data structures used
-- [ ] Caching implemented where beneficial
-- [ ] Lazy loading for expensive operations
-
-## Resource Management
-- [ ] Memory usage optimized
-- [ ] Connection pooling used
-- [ ] Batch operations where applicable
-- [ ] Async/parallel processing considered
-
-## Frontend Specific
-- [ ] Bundle size optimized
-- [ ] Images optimized
-- [ ] Critical rendering path optimized
-- [ ] Network requests minimized
-
-## Backend Specific
-- [ ] Database queries optimized
-- [ ] Response compression enabled
-- [ ] Proper indexing in place
-- [ ] Connection limits configured

package/templates/checklists/security.md

@@ -1,33 +0,0 @@
-# Security Checklist
-
-> ALWAYS ON - Applies to ALL applications
-
-## Input/Output
-- [ ] All user input validated and sanitized
-- [ ] Output encoded appropriately (prevent injection)
-- [ ] File uploads restricted and scanned
-- [ ] No sensitive data in logs or error messages
-
-## Authentication & Authorization
-- [ ] Strong authentication mechanism
-- [ ] Proper session management
-- [ ] Authorization checked at every access point
-- [ ] Principle of least privilege applied
-
-## Data Protection
-- [ ] Sensitive data encrypted at rest
-- [ ] Secure transmission (TLS/HTTPS)
-- [ ] PII handled according to regulations
-- [ ] Data retention policies followed
-
-## Dependencies
-- [ ] Dependencies from trusted sources
-- [ ] Known vulnerabilities checked
-- [ ] Minimal dependency surface
-- [ ] Regular security updates planned
-
-## API Security
-- [ ] Rate limiting implemented
-- [ ] Authentication required for sensitive endpoints
-- [ ] CORS properly configured
-- [ ] API keys/tokens secured

package/templates/checklists/testing.md

@@ -1,33 +0,0 @@
-# Testing Checklist
-
-> Applies to: Unit, Integration, E2E, Performance testing
-
-## Coverage Strategy
-- [ ] Critical paths have high coverage
-- [ ] Happy path tested
-- [ ] Error paths tested
-- [ ] Edge cases covered
-
-## Test Quality
-- [ ] Tests are deterministic (no flaky tests)
-- [ ] Tests are independent (no order dependency)
-- [ ] Tests are fast (optimize slow tests)
-- [ ] Tests are readable (clear intent)
-
-## Test Types
-- [ ] Unit tests for business logic
-- [ ] Integration tests for boundaries
-- [ ] E2E tests for critical flows
-- [ ] Performance tests for bottlenecks
-
-## Mocking Strategy
-- [ ] External services mocked
-- [ ] Database isolated or mocked
-- [ ] Time-dependent code controlled
-- [ ] Random values seeded
-
-## Test Maintenance
-- [ ] Tests updated with code changes
-- [ ] Dead tests removed
-- [ ] Test data managed properly
-- [ ] CI/CD integration working

package/templates/checklists/ux-ui.md

@@ -1,37 +0,0 @@
-# UX/UI Checklist
-
-> Applies to: Web, Mobile, CLI, Desktop, API DX
-
-## User Experience
-- [ ] Clear user journey/flow
-- [ ] Feedback for every action
-- [ ] Loading states shown
-- [ ] Error states handled gracefully
-- [ ] Success confirmation provided
-
-## Interface Design
-- [ ] Consistent visual language
-- [ ] Intuitive navigation
-- [ ] Responsive/adaptive layout (if applicable)
-- [ ] Touch targets adequate (mobile)
-- [ ] Keyboard navigation (web/desktop)
-
-## CLI Specific
-- [ ] Help text for all commands
-- [ ] Clear error messages with suggestions
-- [ ] Progress indicators for long operations
-- [ ] Consistent flag naming conventions
-- [ ] Exit codes meaningful
-
-## API DX (Developer Experience)
-- [ ] Intuitive endpoint/function naming
-- [ ] Consistent response format
-- [ ] Helpful error messages with codes
-- [ ] Good documentation with examples
-- [ ] Predictable behavior
-
-## Information Architecture
-- [ ] Content hierarchy clear
-- [ ] Important actions prominent
-- [ ] Related items grouped
-- [ ] Search/filter for large datasets

package/templates/commands/analyze.md

@@ -1,56 +0,0 @@
----
-allowed-tools: [Read, Grep, Glob, Bash, TodoWrite]
-description: 'Analyze repo + generate summary'
-architecture: 'Write-Through (JSON → MD → Events)'
-storage-layer: true
-source-of-truth: 'storage/analysis.json'
-claude-context: 'context/analysis.md'
----
-
-# /p:analyze - Analyze Repository
-
-## Architecture: Write-Through Pattern
-
-**Source of Truth**: `storage/analysis.json`
-**Claude Context**: `context/analysis.md` (generated)
-
-## Context Variables
-- `{projectId}`: From `.prjct/prjct.config.json`
-- `{globalPath}`: `~/.prjct-cli/projects/{projectId}`
-- `{analysisStoragePath}`: `{globalPath}/storage/analysis.json`
-- `{analysisContextPath}`: `{globalPath}/context/analysis.md`
-
-## Flow
-
-1. Scan structure → Detect tech (package.json, Gemfile, etc.)
-2. Analyze patterns → Git status
-3. Write `storage/analysis.json` (source of truth)
-4. Generate `context/analysis.md` (for Claude)
-
-## Report
-
-- Overview: type, lang, framework
-- Stack: technologies detected
-- Architecture: patterns, entry points
-- Agents: recommend specialists
-
-## Storage Format
-
-### storage/analysis.json
-```json
-{
-  "projectType": "web",
-  "languages": ["typescript", "javascript"],
-  "frameworks": ["react", "next.js"],
-  "entryPoints": ["src/index.ts"],
-  "patterns": ["component-based", "api-routes"],
-  "dependencies": {...},
-  "analyzedAt": "{timestamp}"
-}
-```
-
-## Response
-
-```
-🔍 {project} | Stack: {tech} | Saved: context/analysis.md
-```