vibefast-cli 0.7.0 → 0.7.1

package/2/.claude/commands/create-tech-stack.md

@@ -1,345 +0,0 @@
----
-allowed-tools: Read, Glob, Grep, Write, MultiEdit, TodoWrite, Bash
-description: Generate comprehensive technical stack documentation from codebase analysis
----
-
-# Generate Tech Stack Documentation
-
-**User Request:** $ARGUMENTS
-
-## Context
-
-- Project root: !`pwd`
-- Package.json: @package.json
-- Node version: !`node --version 2>/dev/null || echo "Node.js not found"`
-- TypeScript config: @tsconfig.json
-- Database schema: !`ls -la prisma/schema.prisma 2>/dev/null || echo "No Prisma schema found"`
-- Existing docs: !`ls -la .claude/docs/*.md 2>/dev/null || echo "No docs yet"`
-
-## Goal
-
-Create comprehensive Tech Stack Documentation based on deep codebase analysis. Document all technologies, frameworks, libraries, development tools, deployment strategies, and implementation patterns with specific versions and configurations.
-
-## Process
-
-### 1. Automated Technical Discovery
-
-- Parse package.json for all dependencies
-- Analyze configuration files (tsconfig, vite.config, next.config, etc.)
-- Detect database setup (Prisma, Drizzle, TypeORM, etc.)
-- Identify testing frameworks and tools
-- Scan for CI/CD configurations
-- Check deployment configurations
-
-### 2. Deep Code Analysis
-
-Examine codebase for:
-
-- **Architecture Patterns:** Monorepo structure, module organization
-- **Framework Usage:** Next.js app router vs pages, API routes
-- **State Management:** Zustand, Redux, Context API patterns
-- **Styling Approach:** Tailwind, CSS modules, styled-components
-- **Type Safety:** TypeScript strictness, validation libraries
-- **API Design:** REST, GraphQL, tRPC implementation
-- **Authentication:** Auth libraries and session management
-- **Testing Strategy:** Unit, integration, E2E test patterns
-
-### 3. Interactive Technical Q&A
-
-Ask 4-6 deployment and infrastructure questions:
-
-- Use numbered/lettered options
-- Focus on non-discoverable information
-- Gather hosting, monitoring, and workflow details
-
-### 4. Generate Comprehensive Documentation
-
-Create detailed tech stack document with:
-
-- Specific version numbers
-- Configuration examples
-- Command references
-- Architecture diagrams (when applicable)
-
-### 5. Save and Organize
-
-- Create `.claude/docs/` if needed
-- Save as `tech-stack.md`
-- Update CLAUDE.md commands section
-
-## Technical Questions Template
-
-### 🚀 Deployment & Infrastructure
-
-**1. Where is your application currently deployed?**
-
-a) **Vercel** - Next.js optimized hosting  
- b) **AWS** - EC2, Lambda, or containerized  
- c) **Railway/Render** - Modern PaaS providers  
- d) **Self-hosted** - VPS or on-premise  
- e) **Other** - Please specify  
- f) **Not deployed yet** - Still in development
-
-**2. How is your database hosted?**
-
-a) **Managed service** (Supabase, PlanetScale, Neon, etc.)  
- b) **Cloud provider** (AWS RDS, Google Cloud SQL, etc.)  
- c) **Self-hosted** (Docker, VPS, etc.)  
- d) **Local only** - No production database yet
-
-### 📊 Monitoring & Operations
-
-**3. What observability tools do you use?**
-
-a) **Error tracking:** Sentry, Rollbar, Bugsnag  
- b) **Analytics:** Vercel Analytics, Google Analytics, Plausible  
- c) **Monitoring:** Datadog, New Relic, custom solution  
- d) **Logging:** CloudWatch, LogTail, custom logs  
- e) **None yet** - Planning to add later
-
-### 👥 Development Workflow
-
-**4. What's your Git workflow?**
-
-a) **Feature branches** with PR reviews  
- b) **Trunk-based** development  
- c) **GitFlow** with release branches  
- d) **Direct to main** (solo project)
-
-**5. How do you manage environments?**
-
-a) **Multiple deployments** (dev, staging, prod)  
- b) **Preview deployments** for PRs  
- c) **Single production** environment  
- d) **Local development** only
-
-### 🔐 Additional Services
-
-**6. Which external services do you integrate with?**
-
-- [ ] Payment processing (Stripe, PayPal)
-- [ ] Email service (SendGrid, Resend, AWS SES)
-- [ ] File storage (S3, Cloudinary, UploadThing)
-- [ ] Authentication (Auth0, Clerk, Supabase Auth)
-- [ ] Search (Algolia, Elasticsearch)
-- [ ] Other APIs (please specify)
-
-## Document Structure
-
-The generated document must follow this technical structure:
-
-### **Overview**
-
-- Brief description of the application's technical nature
-- Technology stack summary
-- Architecture approach (monolith, microservices, etc.)
-
-### **Programming Language & Runtime**
-
-- Primary programming language and version
-- Runtime environment and version
-- Type system and language features used
-
-### **Frontend**
-
-- UI Framework/Library and version
-- Styling approach and frameworks
-- Component libraries and design systems
-- State management solutions
-- Build tools and bundlers
-- Browser support and compatibility
-
-### **Backend**
-
-- Backend framework and architecture
-- API design (REST, GraphQL, tRPC, etc.)
-- Authentication and authorization
-- Middleware and security
-- File handling and uploads
-
-### **Database & Storage**
-
-- Database type and version
-- ORM/Query builder
-- Schema management and migrations
-- Caching solutions
-- File storage solutions
-- Data backup and recovery
-
-### **Development Tools & Workflow**
-
-- Package manager
-- Code formatting and linting
-- Type checking and compilation
-- Testing frameworks and strategies
-- Development server and hot reload
-- Version control workflow
-
-### **Deployment & Infrastructure**
-
-- Hosting platform and services
-- Build and deployment pipeline
-- Environment configuration
-- Domain and DNS management
-- SSL/TLS and security
-- Monitoring and logging
-
-### **External Integrations**
-
-- Third-party APIs and services
-- Payment processing
-- Email services
-- Analytics and tracking
-- Error monitoring
-- Performance monitoring
-
-### **Quality Assurance & Testing**
-
-- Testing strategy and frameworks
-- Code coverage tools
-- End-to-end testing
-- Performance testing
-- Security testing
-- Code review process
-
-### **Schemas & Data Models**
-
-- Database schema (if applicable)
-- API schemas and validation
-- Type definitions and interfaces
-- Data relationships and constraints
-
-## Target Audience
-
-The document should serve:
-
-- **Developers** joining the project who need technical onboarding
-- **DevOps engineers** setting up infrastructure and deployment
-- **Technical architects** evaluating or improving the tech stack
-- **Security teams** understanding the technical landscape
-- **Future maintainers** who need to understand technical decisions
-
-The language should be technical, precise, and include specific version numbers and configuration details.
-
-## Documentation Principles
-
-### DO Include:
-
-- **Exact Versions:** Lock file versions, not just ranges
-- **Configuration Examples:** Actual config snippets from the project
-- **Command Reference:** All npm scripts and their purposes
-- **Setup Instructions:** Step-by-step for new developers
-- **Architecture Decisions:** Why specific technologies were chosen
-- **Integration Details:** How services connect and communicate
-
-### DON'T Include:
-
-- **Generic Descriptions:** Avoid Wikipedia-style explanations
-- **Outdated Information:** Only document what's actually used
-- **Wishful Thinking:** Document current state, not future plans
-- **Sensitive Data:** No API keys, secrets, or credentials
-- **Redundant Info:** Link to official docs instead of copying
-
-## Output
-
-- **Format:** Markdown (`.md`)
-- **Location:** `.claude/docs/`
-- **Filename:** `tech-stack.md`
-
-## Execution Steps
-
-### 1. Automated Analysis Phase
-
-```bash
-# Extract key technical information
-- Read package.json and lock files
-- Scan for configuration files
-- Detect framework patterns
-- Identify database setup
-- Find test configurations
-```
-
-### 2. Manual Discovery Phase
-
-- Read key source files to understand architecture
-- Check for API route patterns
-- Analyze authentication implementation
-- Review deployment configurations
-
-### 3. Interactive Q&A
-
-- Present deployment and infrastructure questions
-- Use checkboxes for multi-select options
-- Wait for user responses
-
-### 4. Document Generation
-
-- Start with discovered information
-- Incorporate user responses
-- Add specific configuration examples
-- Include all npm scripts with descriptions
-
-### 5. Save and Update
-
-```bash
-# Create directory and save
-mkdir -p .claude/docs
-# Save to .claude/docs/tech-stack.md
-```
-
-### 6. Update CLAUDE.md
-
-Add discovered commands to the Commands section:
-
-```markdown
-### Development
-
-- `pnpm dev` - Start development server
-- `pnpm build` - Build for production
-- `pnpm typecheck` - Run TypeScript type checking
-
-# ... other discovered commands
-```
-
-### 7. Next Steps
-
-- Suggest: "Would you like me to update CLAUDE.md with the discovered commands?"
-- Recommend: "Should I create an app design document to complement this technical documentation?"
-
-## Example Usage
-
-```bash
-# Basic usage
-/project:create-tech-stack
-
-# With specific focus
-/project:create-tech-stack Focus on deployment and CI/CD setup
-```
-
-## Sample Output Structure
-
-```markdown
-# Tech Stack Documentation
-
-## Overview
-
-- **Framework:** Next.js 14.2.5 (App Router)
-- **Language:** TypeScript 5.5.3
-- **Database:** PostgreSQL with Prisma ORM
-- **Deployment:** Vercel with preview deployments
-
-## Commands Reference
-
-### Development
-
-- `pnpm dev` - Start Next.js dev server on port 3005
-- `pnpm build` - Build production bundle
-- `pnpm typecheck` - Run tsc --noEmit
-
-### Database
-
-- `pnpm db:generate` - Generate Prisma client
-- `pnpm db:push` - Push schema changes to database
-
-# ... continue with full documentation
-```

package/2/.claude/commands/update-app-design.md

@@ -1,298 +0,0 @@
----
-allowed-tools: Read, Glob, Grep, Write, MultiEdit, TodoWrite, Bash
-description: Update existing app design document based on codebase changes and project evolution
----
-
-# Sync Application Design Document
-
-**User Request:** $ARGUMENTS
-
-## Context
-
-- Project root: !`pwd`
-- Package.json: @package.json
-- Current design doc: @.claude/docs/app-design-document.md
-- Last modified: !`stat -f "%Sm" .claude/docs/app-design-document.md 2>/dev/null || echo "No existing document"`
-- Project status: @CLAUDE.md#project-status
-
-## Goal
-
-Update the existing Application Design Document to reflect current codebase state, new features, changed priorities, and project evolution. Maintain consistency with the original document while incorporating new information.
-
-## Process
-
-### 1. Document Analysis
-
-- Read and understand the existing app-design-document.md
-- Establish baseline understanding of documented features
-- Note the document's structure and tone
-- Identify areas that may need updates
-
-### 2. Codebase Change Detection
-
-**Think deeply about what has changed in the codebase since the document was last updated.**
-
-Analyze for:
-
-- **New Features:** Components, modules, or capabilities added
-- **Modified Flows:** Changes to user journeys or business logic
-- **Removed Features:** Deprecated or deleted functionality
-- **Architecture Evolution:** New patterns, services, or integrations
-- **Scale Changes:** Growth in complexity or user base
-- **Security Updates:** New authentication/authorization patterns
-
-_Extended thinking helps identify subtle changes, understand how new features integrate with existing ones, and recognize patterns that indicate architectural evolution._
-
-### 3. Interactive Update Session
-
-**CRITICAL:** Ask project stage question FIRST to assess if priorities have changed:
-
-- Use lettered/numbered options for easy response
-- Focus on what has changed and why
-- Gather context for accurate updates
-
-### 4. Update Project Configuration
-
-If project stage or priorities have changed:
-
-- Update `CLAUDE.md` "Project Status" section
-- Adjust DO/DON'T lists for new priorities
-- Document any stage transitions
-
-### 5. Sync Document
-
-Update the document incrementally:
-
-- Preserve accurate existing content
-- Add new sections only when necessary
-- Update outdated information
-- Maintain consistent tone and structure
-
-### 6. Save Updated Document
-
-- Backup suggestion if major changes
-- Overwrite existing app-design-document.md
-- Note what was updated
-
-## Required Questions Template
-
-### 🎯 CRITICAL: Project Evolution Assessment (Ask First!)
-
-**1. Has your project stage evolved since the last update?**
-
-a) **Same Stage** - Still in [current stage], just adding features  
-b) **Stage Evolution** - Moved from [current] to next stage  
-c) **Major Pivot** - Significant change in direction or purpose  
-d) **Help Me Assess** - Let's review current state together
-
-**2. Have your development priorities changed?**
-
-Based on your current stage, are these still your priorities?
-
-[Show current DO/DON'T lists from CLAUDE.md]
-
-a) **Same Priorities** - These still reflect our focus  
-b) **Adjusted Priorities** - Some changes needed (please specify)  
-c) **New Focus Areas** - Different priorities based on learnings  
-d) **Stage-Based Change** - Priorities changed due to stage evolution
-
-### 📊 Change Identification Questions
-
-**3. What major features have been added?**
-
-Please describe any significant new capabilities, modules, or user-facing features added since the last update.
-
-**4. Have any core user flows changed?**
-
-a) **Authentication/Authorization** - Login, permissions, security  
-b) **Main User Journey** - Primary application workflow  
-c) **Data Management** - How users create/edit/delete data  
-d) **Integration Points** - External service connections  
-e) **None/Minor Only** - No significant flow changes
-
-**5. What has been removed or deprecated?**
-
-List any features, integrations, or capabilities that have been removed or are being phased out.
-
-**6. Have you integrated new external services?**
-
-a) **Payment Processing** - Stripe, PayPal, etc.  
-b) **Communication** - Email, SMS, notifications  
-c) **Analytics/Monitoring** - Tracking, logging services  
-d) **AI/ML Services** - LLMs, image processing, etc.  
-e) **Other** - Please specify  
-f) **None** - No new integrations
-
-### 🚀 Future Direction Questions
-
-**7. How has user feedback influenced changes?**
-
-Describe any significant pivots or adjustments made based on user feedback or usage patterns.
-
-**8. What are your updated success metrics?**
-
-Have your KPIs or success measurements changed? Current focus:
-
-- User growth targets?
-- Revenue goals?
-- Engagement metrics?
-- Performance benchmarks?
-
-**9. What's the next major milestone?**
-
-a) **Feature Release** - Specific new capability  
-b) **Scale Milestone** - User/revenue target  
-c) **Technical Goal** - Performance, security, architecture  
-d) **Business Goal** - Partnerships, funding, market expansion
-
-## Update Strategy
-
-### Incremental Updates
-
-- **Preserve:** Keep accurate existing content
-- **Enhance:** Add new information to existing sections
-- **Replace:** Update outdated or incorrect information
-- **Remove:** Mark deprecated features appropriately
-
-### Change Documentation
-
-- **New Features:** Add to relevant feature categories
-- **Modified Flows:** Update user journey descriptions
-- **Architecture Changes:** Reflect in system architecture section
-- **Business Evolution:** Update goals and success metrics
-
-### Consistency Maintenance
-
-- Keep the same professional, accessible tone
-- Maintain technology-agnostic descriptions
-- Focus on WHAT not HOW
-- Preserve document structure
-
-## Document Update Areas
-
-### Always Review:
-
-1. **Introduction**
-   - Update if purpose or audience has shifted
-   - Reflect any pivot in value proposition
-
-2. **Core Features**
-   - Add new feature categories if needed
-   - Update existing features with enhancements
-   - Mark removed features as deprecated
-
-3. **User Experience**
-   - Update user journeys with new flows
-   - Add new user personas if applicable
-   - Reflect UI/UX improvements
-
-4. **System Architecture**
-   - Add new integrations
-   - Update data flow diagrams
-   - Reflect new security patterns
-
-5. **Business Logic**
-   - Update rules and workflows
-   - Reflect new validation requirements
-   - Document new business constraints
-
-6. **Future Considerations**
-   - Update roadmap based on progress
-   - Add new planned features
-   - Reflect lessons learned
-
-## Execution Steps
-
-### 1. Start with Analysis
-
-```bash
-# Check when document was last updated
-stat -f "%Sm" .claude/docs/app-design-document.md
-
-# Review recent commits for feature changes
-git log --oneline --since="30 days ago" | head -20
-```
-
-**Think deeply about:** "What has fundamentally changed in this application? How have new features altered the original vision? What patterns indicate architectural evolution?"
-
-### 2. Interactive Q&A
-
-- **MUST ASK PROJECT STAGE FIRST**
-- Present all questions clearly
-- Wait for complete responses
-
-### 3. Update Project Status (if needed)
-
-If stage or priorities changed, update both:
-
-```markdown
-# In CLAUDE.md
-
-## Project Status
-
-**Current Stage**: [New Stage]
-
-### DO Care About (Production-Ready Foundation)
-
-[Updated priorities]
-
-### DO NOT Care About (Skip for Velocity)
-
-[Updated items to skip]
-```
-
-### 4. Sync Document
-
-- Make targeted updates
-- Preserve document quality
-- Add version note if helpful:
-
-```markdown
-<!-- Last updated: [date] - Major changes: [summary] -->
-```
-
-### 5. Save and Backup
-
-```bash
-# Optional: Create backup
-cp .claude/docs/app-design-document.md .claude/docs/app-design-document.backup.md
-
-# Save updated document
-# Overwrite .claude/docs/app-design-document.md
-```
-
-## Key Principles
-
-### DO:
-
-- **Preserve Quality:** Maintain document's professional tone
-- **Incremental Updates:** Don't rewrite unnecessarily
-- **Clear Changes:** Make updates obvious and well-integrated
-- **User Focus:** Keep emphasis on user value
-- **Stage Awareness:** Align with current project maturity
-
-### DON'T:
-
-- **Complete Rewrite:** Unless fundamentally pivoted
-- **Technical Details:** Maintain high-level focus
-- **Break Structure:** Keep established organization
-- **Lose History:** Preserve context of major decisions
-- **Skip Analysis:** Always understand current state first
-
-## Output
-
-- **Format:** Markdown (`.md`)
-- **Location:** `.claude/docs/`
-- **Filename:** `app-design-document.md` (overwrites)
-- **Backup:** Suggest if major changes
-
-## Final Checklist
-
-1. ✅ Read existing document completely
-2. ✅ Analyze codebase changes thoroughly
-3. ✅ Ask project stage question FIRST
-4. ✅ Update CLAUDE.md if stage/priorities changed
-5. ✅ Make incremental, targeted updates
-6. ✅ Preserve document quality and tone
-7. ✅ Suggest backup for major changes
-8. ✅ Consider tech-stack.md updates if needed

package/2/.claude/commands/update-project-structure.md

@@ -1,14 +0,0 @@
----
-allowed-tools: Bash
-description: Update project structure documentation by running tree script
----
-
-# Update Project Structure
-
-Run the tree script to update project structure documentation:
-
-```bash
-bash .claude/scripts/tree.sh
-```
-
-Do not do anything else.