claudekit-cli 1.0.0 → 1.1.0

package/docs/project-pdr.md

@@ -1,739 +0,0 @@
-# Product Development Requirements (PDR)
-# ClaudeKit CLI
-
-**Version:** 0.1.0
-**Date:** 2025-10-08
-**Status:** Production Ready
-**Product Owner:** ClaudeKit Team
-**Project Type:** CLI Tool (TypeScript + Bun)
-
----
-
-## Executive Summary
-
-ClaudeKit CLI (`ck`) is a command-line tool that enables developers to quickly bootstrap new projects and update existing projects using releases from private GitHub repositories. The tool provides a seamless developer experience with intelligent authentication, streaming downloads, smart file merging, and secure token management.
-
-**Key Value Propositions:**
-- Zero-configuration setup for users with GitHub CLI authentication
-- Fast project initialization leveraging Bun's performance
-- Safe updates with intelligent conflict resolution
-- Secure token management using OS-native credential stores
-- Beautiful CLI interface with progress tracking
-
----
-
-## Product Vision
-
-### Problem Statement
-
-Developers need a fast, secure way to bootstrap projects from private GitHub repository releases and keep them updated without manually downloading, extracting, and merging files. Existing solutions either lack private repository support, don't handle file conflicts intelligently, or provide poor developer experience.
-
-### Solution
-
-ClaudeKit CLI provides an opinionated, batteries-included solution that:
-1. Handles authentication automatically with multiple fallback strategies
-2. Downloads and extracts releases efficiently with progress tracking
-3. Merges files intelligently while protecting sensitive configurations
-4. Provides clear feedback and actionable error messages
-5. Works seamlessly with existing GitHub workflows
-
-### Target Audience
-
-**Primary Users:**
-- Software developers using ClaudeKit frameworks
-- Development teams needing consistent project scaffolding
-- DevOps engineers automating project setup
-
-**User Personas:**
-
-**1. Solo Developer (Alex)**
-- Wants quick project setup
-- Prefers minimal configuration
-- Values clear documentation
-- Uses GitHub CLI regularly
-
-**2. Team Lead (Sarah)**
-- Needs consistent team setup
-- Requires secure credential management
-- Values automation and reproducibility
-- Manages multiple projects
-
-**3. DevOps Engineer (Marcus)**
-- Automates infrastructure
-- Requires scriptable CLI
-- Needs reliable error handling
-- Values performance and efficiency
-
----
-
-## Functional Requirements
-
-### FR-1: Project Initialization (`ck new`)
-
-**Priority:** Critical
-**User Story:** As a developer, I want to create a new project from a ClaudeKit release so that I can start development quickly.
-
-**Acceptance Criteria:**
-- ✅ User can run `ck new` to create a new project interactively
-- ✅ User can specify target directory with `--dir` option
-- ✅ User can specify kit type with `--kit` option (engineer, marketing)
-- ✅ User can specify version with `--version` option
-- ✅ Tool validates directory doesn't exist or is empty
-- ✅ Tool downloads latest release by default
-- ✅ Tool extracts files to target directory
-- ✅ Tool shows progress during download and extraction
-- ✅ Tool displays next steps after successful creation
-
-**Examples:**
-```bash
-# Interactive mode
-ck new
-
-# With options
-ck new --dir my-app --kit engineer
-
-# Specific version
-ck new --kit engineer --version v1.0.0
-```
-
----
-
-### FR-2: Project Updates (`ck update`)
-
-**Priority:** Critical
-**User Story:** As a developer, I want to update my existing project to the latest ClaudeKit version while preserving my customizations.
-
-**Acceptance Criteria:**
-- ✅ User can run `ck update` to update existing project
-- ✅ User can specify directory with `--dir` option
-- ✅ User can specify kit type with `--kit` option
-- ✅ User can specify version with `--version` option
-- ✅ Tool validates directory exists
-- ✅ Tool detects file conflicts before updating
-- ✅ Tool shows confirmation prompt with conflict summary
-- ✅ Tool protects sensitive files (.env, config files, etc.)
-- ✅ Tool displays update summary after completion
-
-**Examples:**
-```bash
-# Interactive mode
-ck update
-
-# With options
-ck update --kit engineer
-
-# Specific version
-ck update --kit engineer --version v2.0.0
-```
-
----
-
-### FR-3: Authentication Management
-
-**Priority:** Critical
-**User Story:** As a developer, I want authentication to work automatically so that I don't have to manage tokens manually.
-
-**Multi-Tier Fallback Strategy:**
-1. **GitHub CLI** (`gh auth token`) - if available
-2. **Environment Variables** (GITHUB_TOKEN, GH_TOKEN)
-3. **Stored Credentials** (OS keychain)
-4. **User Prompt** (with optional secure storage)
-
-**Acceptance Criteria:**
-- ✅ Tool detects GitHub CLI authentication automatically
-- ✅ Tool reads environment variables if gh CLI unavailable
-- ✅ Tool retrieves tokens from OS keychain
-- ✅ Tool prompts user for token if no auth found
-- ✅ Tool validates token format before use
-- ✅ Tool asks permission before storing token
-- ✅ Tool stores token securely in OS keychain
-- ✅ Tool never logs or exposes tokens
-- ✅ Tool clears invalid tokens automatically
-
-**Token Requirements:**
-- Valid GitHub Personal Access Token (PAT)
-- Minimum permissions: `repo` scope for private repositories
-- Fine-grained PAT with Contents: Read permission (recommended)
-
----
-
-### FR-4: Version Management
-
-**Priority:** High
-**User Story:** As a developer, I want to specify which version to download so that I can control when to upgrade.
-
-**Acceptance Criteria:**
-- ✅ Tool downloads latest release by default
-- ✅ User can specify exact version with `--version` flag
-- ✅ Tool supports version formats: `v1.0.0` and `1.0.0`
-- ✅ Tool shows error if version not found
-- ✅ Tool lists available versions in interactive mode
-- ✅ Tool handles prereleases appropriately
-
----
-
-### FR-5: File Conflict Resolution
-
-**Priority:** High
-**User Story:** As a developer, I want my configuration files protected during updates so that I don't lose my customizations.
-
-**Protected File Patterns:**
-- `.env`, `.env.*` - Environment variables
-- `*.key`, `*.pem`, `*.p12` - Security keys
-- `node_modules/**` - Dependencies
-- `.git/**` - Git repository
-- `dist/**`, `build/**` - Build output
-
-**Acceptance Criteria:**
-- ✅ Tool identifies protected files before merge
-- ✅ Tool skips protected files if they exist
-- ✅ Tool shows which files were skipped
-- ✅ Tool allows custom ignore patterns
-- ✅ Tool handles nested directory structures
-- ✅ Tool shows merge summary with counts
-
----
-
-### FR-6: Progress Tracking
-
-**Priority:** Medium
-**User Story:** As a developer, I want to see download progress so that I know the operation is working.
-
-**Acceptance Criteria:**
-- ✅ Tool shows download progress bar
-- ✅ Tool displays download speed and ETA
-- ✅ Tool shows bytes transferred and total size
-- ✅ Tool shows spinner during extraction
-- ✅ Tool shows completion message
-- ✅ Tool uses colors for better readability
-
----
-
-### FR-7: Error Handling
-
-**Priority:** High
-**User Story:** As a developer, I want clear error messages so that I can fix issues quickly.
-
-**Acceptance Criteria:**
-- ✅ Tool shows actionable error messages
-- ✅ Tool suggests solutions for common errors
-- ✅ Tool handles network timeouts gracefully
-- ✅ Tool handles invalid tokens with clear guidance
-- ✅ Tool handles rate limits appropriately
-- ✅ Tool cleans up temporary files on error
-- ✅ Tool exits with appropriate error codes
-
-**Common Error Scenarios:**
-- Invalid or expired GitHub token
-- Network connection failure
-- Rate limit exceeded
-- Version not found
-- Directory not writable
-- Insufficient disk space
-
----
-
-## Non-Functional Requirements
-
-### NFR-1: Performance
-
-**Priority:** High
-
-**Requirements:**
-- ✅ Startup time < 500ms
-- ✅ Download speed ≥ 10MB/s (on good connections)
-- ✅ Extraction time < 10s for 50MB archive
-- ✅ Memory usage < 100MB during operations
-- ✅ Streaming downloads (no full file in memory)
-- ✅ Efficient file system operations
-
-**Measurement:**
-- Test with 50MB archive on 100Mbps connection
-- Monitor memory usage during operations
-- Benchmark startup time on cold start
-
----
-
-### NFR-2: Security
-
-**Priority:** Critical
-
-**Requirements:**
-- ✅ Secure token storage in OS keychain
-- ✅ No token logging or exposure in errors
-- ✅ Token sanitization in all log output
-- ✅ Path traversal protection during extraction
-- ✅ Input validation for all user inputs
-- ✅ HTTPS-only communication
-- ✅ User consent before storing credentials
-
-**Security Audit Items:**
-- ✅ Token never appears in logs
-- ✅ Tokens stored in OS keychain only
-- ✅ All paths validated and sanitized
-- ✅ No hardcoded credentials
-- ✅ Proper error handling without exposing sensitive data
-
----
-
-### NFR-3: Reliability
-
-**Priority:** High
-
-**Requirements:**
-- ✅ Automatic retry with exponential backoff
-- ✅ Rate limit handling for GitHub API
-- ✅ Network error recovery
-- ✅ Atomic operations (rollback on failure)
-- ✅ Graceful handling of interruptions
-- ✅ Temporary file cleanup
-
-**Reliability Metrics:**
-- 99% success rate for valid operations
-- < 1% failure rate due to tool errors
-- 100% cleanup of temporary files
-
----
-
-### NFR-4: Usability
-
-**Priority:** High
-
-**Requirements:**
-- ✅ Clear, colorized output
-- ✅ Progress indicators for long operations
-- ✅ Interactive prompts with validation
-- ✅ Helpful error messages with solutions
-- ✅ Consistent command interface
-- ✅ Comprehensive help documentation
-
-**Usability Metrics:**
-- Users can complete setup without documentation
-- Error messages provide clear next steps
-- Average time to first successful run < 5 minutes
-
----
-
-### NFR-5: Maintainability
-
-**Priority:** High
-
-**Requirements:**
-- ✅ TypeScript with strict mode
-- ✅ Modular architecture
-- ✅ Comprehensive test coverage (≥80%)
-- ✅ Clear separation of concerns
-- ✅ Consistent code style
-- ✅ Documentation for all public APIs
-
-**Code Quality Metrics:**
-- Test coverage ≥ 80%
-- File size < 500 lines
-- 0 linting errors
-- 0 type errors
-- Clear module boundaries
-
----
-
-### NFR-6: Compatibility
-
-**Priority:** Medium
-
-**Requirements:**
-- ✅ Bun runtime ≥ 1.0.0
-- ✅ macOS support (primary)
-- ⚠️ Linux support (planned)
-- ⚠️ Windows support (planned)
-- ✅ Node.js API compatibility (via Bun)
-
-**Platform Support:**
-- **Primary:** macOS (ARM64, x86_64)
-- **Future:** Linux (x86_64, ARM64)
-- **Future:** Windows (x86_64)
-
----
-
-## User Stories
-
-### Epic 1: Project Setup
-
-**US-1.1: Quick Start**
-> As a new user, I want to create my first project with a single command so that I can start coding immediately.
-
-**Acceptance Criteria:**
-- Run `ck new` and answer prompts
-- Project created in < 30 seconds
-- Clear next steps shown
-
-**US-1.2: Team Onboarding**
-> As a team lead, I want new team members to use consistent project structure so that codebases are uniform.
-
-**Acceptance Criteria:**
-- Documented project creation process
-- Same kit version across team
-- Protected configuration patterns
-
----
-
-### Epic 2: Project Maintenance
-
-**US-2.1: Safe Updates**
-> As a developer, I want to update to the latest version without losing my customizations.
-
-**Acceptance Criteria:**
-- Protected files never overwritten
-- Conflicts shown before update
-- Merge summary displayed
-
-**US-2.2: Version Control**
-> As a developer, I want to specify which version to use so that I can upgrade at my own pace.
-
-**Acceptance Criteria:**
-- Specific version selection
-- Version listing in interactive mode
-- Clear version format support
-
----
-
-### Epic 3: Authentication
-
-**US-3.1: Zero Config Auth**
-> As a GitHub CLI user, I want authentication to work automatically without any setup.
-
-**Acceptance Criteria:**
-- Detect gh CLI token
-- No prompts if gh CLI available
-- Clear feedback on auth method
-
-**US-3.2: Secure Credentials**
-> As a security-conscious developer, I want my tokens stored securely in the OS keychain.
-
-**Acceptance Criteria:**
-- Keychain storage used
-- User consent before storing
-- No plain text token files
-
----
-
-## Technical Specifications
-
-### Technology Stack
-
-**Runtime:**
-- Bun v1.x+ (fast, TypeScript-native runtime)
-
-**Language:**
-- TypeScript 5.x+ (strict mode enabled)
-
-**Core Dependencies:**
-- `cac` - Command parsing
-- `@clack/prompts` - Interactive prompts
-- `@octokit/rest` - GitHub API client
-- `zod` - Runtime validation
-- `keytar` - Secure credential storage
-- `ora` - Spinners
-- `cli-progress` - Progress bars
-- `picocolors` - Colors
-- `tar`, `unzipper` - Archive extraction
-- `fs-extra` - File operations
-- `ignore` - Pattern matching
-
-**Development:**
-- `@biomejs/biome` - Linting and formatting
-- Bun Test - Testing framework
-- TypeScript compiler - Type checking
-
----
-
-### Architecture Patterns
-
-**1. Multi-Tier Authentication:**
-```
-GitHub CLI → Env Vars → Config File → Keychain → User Prompt
-```
-
-**2. Streaming Operations:**
-```
-Download Stream → Disk → Extract Stream → Destination
-```
-
-**3. Modular Design:**
-```
-Commands → Libraries → Utilities
-  ↓          ↓           ↓
-new.ts    auth.ts     config.ts
-update.ts github.ts   logger.ts
-          download.ts
-          merge.ts
-          prompts.ts
-```
-
----
-
-### API Contracts
-
-**Command Options:**
-
-```typescript
-// ck new options
-interface NewCommandOptions {
-  dir?: string;        // Target directory (default: '.')
-  kit?: KitType;       // Kit type: 'engineer' | 'marketing'
-  version?: string;    // Version tag (default: latest)
-}
-
-// ck update options
-interface UpdateCommandOptions {
-  dir?: string;        // Target directory (default: '.')
-  kit?: KitType;       // Kit type: 'engineer' | 'marketing'
-  version?: string;    // Version tag (default: latest)
-}
-```
-
-**Exit Codes:**
-- `0` - Success
-- `1` - General error
-- `2` - Authentication error
-- `3` - Network error
-- `4` - File system error
-
----
-
-## Success Metrics
-
-### Key Performance Indicators (KPIs)
-
-**Adoption Metrics:**
-- Monthly active users
-- Projects created per month
-- Update operations per month
-
-**Performance Metrics:**
-- Average setup time < 30 seconds
-- Download speed ≥ 10MB/s
-- Success rate ≥ 99%
-
-**Quality Metrics:**
-- Test coverage ≥ 80%
-- Zero critical bugs in production
-- User-reported issues < 5 per month
-
-**Developer Experience:**
-- Time to first successful run < 5 minutes
-- Documentation clarity score ≥ 4/5
-- Error resolution time < 2 minutes
-
----
-
-## Release Criteria
-
-### Version 0.1.0 (Initial Release)
-
-**Must Have:**
-- ✅ `ck new` command working
-- ✅ `ck update` command working
-- ✅ Multi-tier authentication
-- ✅ Engineer kit support
-- ✅ Progress tracking
-- ✅ Smart file merging
-- ✅ Test coverage ≥ 80%
-- ✅ Security audit passed
-- ✅ Documentation complete
-
-**Should Have:**
-- ✅ macOS support
-- ✅ Beautiful CLI interface
-- ✅ Comprehensive error handling
-- ✅ Version management
-
-**Could Have:**
-- ⚠️ Linux support
-- ⚠️ Windows support
-- ⚠️ Marketing kit support
-- ⚠️ Auto-update mechanism
-
-**Won't Have (This Release):**
-- Plugin system
-- Template caching
-- Shell completions
-- Analytics/telemetry
-
----
-
-## Future Roadmap
-
-### Version 0.2.0 (Planned)
-- Marketing kit support
-- Linux compatibility
-- Windows compatibility
-- Enhanced error recovery
-
-### Version 0.3.0 (Planned)
-- Self-update mechanism
-- Local template caching
-- Custom kit repositories
-- Shell completion scripts
-
-### Version 1.0.0 (Future)
-- Plugin architecture
-- Community kit registry
-- Advanced merge strategies
-- Performance optimizations
-
----
-
-## Constraints and Assumptions
-
-### Constraints
-
-**Technical:**
-- Bun runtime required (not Node.js compatible)
-- GitHub API rate limits (60/hour unauthenticated, 5000/hour authenticated)
-- OS keychain availability for secure storage
-
-**Business:**
-- Private repository access requires PAT
-- ClaudeKit repositories must follow release pattern
-
-### Assumptions
-
-**User Assumptions:**
-- Users have GitHub account
-- Users can create GitHub PAT
-- Users have Bun installed
-- Users have basic CLI knowledge
-
-**Technical Assumptions:**
-- GitHub API remains stable
-- ClaudeKit releases follow semver
-- Archive formats remain consistent (.tar.gz or .zip)
-- OS keychain APIs remain compatible
-
----
-
-## Risk Management
-
-### High-Priority Risks
-
-**R-1: GitHub API Changes**
-- **Impact:** High
-- **Probability:** Low
-- **Mitigation:** Pin Octokit version, comprehensive error handling, version testing
-
-**R-2: Token Exposure**
-- **Impact:** Critical
-- **Probability:** Low
-- **Mitigation:** Comprehensive sanitization, keychain storage, security audit
-
-**R-3: Rate Limiting**
-- **Impact:** Medium
-- **Probability:** Medium
-- **Mitigation:** Authenticated requests, exponential backoff, user guidance
-
-### Medium-Priority Risks
-
-**R-4: Network Interruptions**
-- **Impact:** Medium
-- **Probability:** Medium
-- **Mitigation:** Retry logic, resume support (future), clear error messages
-
-**R-5: Disk Space Issues**
-- **Impact:** Medium
-- **Probability:** Low
-- **Mitigation:** Pre-flight checks, graceful degradation, cleanup on error
-
----
-
-## Compliance and Legal
-
-### Licensing
-- **License:** MIT
-- **Dependencies:** All MIT or compatible licenses
-- **Distribution:** Open source via npm and GitHub
-
-### Data Privacy
-- **No Analytics:** No usage tracking or telemetry
-- **No PII Collection:** No personal information stored
-- **Local Storage Only:** All data stored on user's machine
-- **Secure Credentials:** Tokens stored in OS keychain only
-
----
-
-## Documentation Requirements
-
-### User Documentation
-- ✅ README with installation and usage
-- ✅ Command reference with examples
-- ✅ Authentication setup guide
-- ✅ Troubleshooting guide
-- ⚠️ FAQ section (planned)
-
-### Developer Documentation
-- ✅ Architecture overview
-- ✅ Code standards
-- ✅ Codebase summary
-- ⚠️ Contributing guide (planned)
-- ⚠️ API documentation (planned)
-
-### Operational Documentation
-- ⚠️ Deployment guide (planned)
-- ⚠️ Release process (planned)
-- ⚠️ Monitoring guide (planned)
-
----
-
-## Acceptance Criteria Summary
-
-### Critical Acceptance Criteria (Must Pass)
-
-**Functionality:**
-- ✅ All 93 tests passing
-- ✅ Both commands (`new`, `update`) working
-- ✅ Multi-tier authentication functional
-- ✅ File merging with conflict detection
-
-**Security:**
-- ✅ No token exposure in logs
-- ✅ Secure keychain storage
-- ✅ Path traversal protection
-- ✅ Input validation
-
-**Quality:**
-- ✅ Test coverage ≥ 80%
-- ✅ 0 type errors
-- ✅ 0 linting errors
-- ✅ Security audit passed
-
-**Documentation:**
-- ✅ README complete
-- ✅ Code standards documented
-- ✅ Architecture documented
-- ✅ Help text comprehensive
-
----
-
-## Sign-Off
-
-### Current Status: ✅ PRODUCTION READY
-
-**Test Results:** 93/93 tests passing (100% pass rate)
-**Type Checking:** 0 errors
-**Security Audit:** Passed (5/5 stars)
-**Code Review:** Approved (5/5 stars)
-**Documentation:** Complete
-
-**Approved By:**
-- Development Team: ✅
-- QA Team: ✅ (93 tests passing)
-- Security Team: ✅ (Security audit passed)
-- Product Owner: ✅
-
-**Release Date:** Ready for deployment
-**Version:** 0.1.0
-**Next Review:** After first production deployment
-
----
-
-**Document Version:** 1.0
-**Last Updated:** 2025-10-08
-**Status:** Final - Production Ready