npm - vibefast-cli - Versions diffs - 0.6.2 → 0.7.1 - Mend

vibefast-cli 0.6.2 → 0.7.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (857) hide show

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

@@ -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 DELETED Viewed

@@ -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.

package/2/.claude/commands/update-tech-stack.md DELETED Viewed

@@ -1,325 +0,0 @@
----
-allowed-tools: Read, Glob, Grep, Write, MultiEdit, TodoWrite, Bash
-description: Update tech stack documentation based on dependency changes and technical evolution
----
-# Update Tech Stack Documentation
-**User Request:** $ARGUMENTS
-## Context
-- Project root: !`pwd`
-- Package.json: @package.json
-- Current tech doc: @.claude/docs/tech-stack.md
-- **Project Structure:** !`bash .claude/scripts/tree.sh`
-- Last modified: !`stat -f "%Sm" .claude/docs/tech-stack.md 2>/dev/null || echo "No existing document"`
-- Recent package changes: !`git diff HEAD~10 HEAD -- package.json 2>/dev/null | grep -E "^[+-]" | head -20 || echo "No recent changes"`
-## Goal
-Update the existing Tech Stack Documentation to reflect current technical state, dependency changes, new tools adoption, and infrastructure evolution. Maintain technical accuracy while documenting all changes.
-## Process
-### 1. Document Analysis
-- Read existing tech-stack.md thoroughly
-- Note documented versions and configurations
-- Understand current technical baseline
-- Identify sections that may need updates
-### 2. Technical Change Detection
-**Think deeply about technical evolution in the codebase.**
-Analyze for:
-- **Dependency Changes:** New packages, version updates, removals
-- **Framework Evolution:** Major version upgrades, breaking changes
-- **Tool Adoption:** New dev tools, linters, formatters, testing frameworks
-- **Infrastructure Shifts:** Deployment, hosting, monitoring changes
-- **Database Evolution:** Schema changes, new ORMs, migrations
-- **Integration Updates:** New APIs, services, authentication providers
-_Extended thinking helps identify cascading dependency updates, understand version compatibility issues, and recognize architectural implications of technical changes._
-### 3. Automated Comparison
-```bash
-# Compare current vs documented dependencies
-# Check for version mismatches
-# Identify new configuration files
-# Detect new tool configurations
-```
-### 4. Interactive Technical Q&A
-Ask targeted questions about:
-- Non-discoverable infrastructure changes
-- Deployment and hosting updates
-- New external service integrations
-- Workflow and process changes
-### 5. Update Documentation
-Update incrementally:
-- Preserve accurate technical information
-- Update version numbers precisely
-- Add new sections for major additions
-- Mark deprecated technologies
-### 6. Save and Verify
-- Suggest backup for major changes
-- Update CLAUDE.md commands if needed
-- Verify all versions are accurate
-## Technical Questions Template
-### 🔄 Version Updates & Dependencies
-**1. Which major dependencies have been updated?**
-Review your recent dependency changes:
-a) **Framework upgrades** (Next.js, React, etc.) with breaking changes
-b) **Tool updates** (TypeScript, ESLint, etc.) requiring config changes
-c) **New dependencies** added for features or development
-d) **Removed packages** that are no longer needed
-e) **All of the above** - Major technical overhaul
-**2. Have you changed your package manager or Node version?**
-a) **Same setup** - No changes to tooling
-b) **Node upgrade** - Updated Node.js version
-c) **Package manager switch** - Changed from npm/yarn/pnpm
-d) **Monorepo adoption** - Moved to workspace setup
-### 🏗️ Infrastructure Evolution
-**3. Have your deployment or hosting arrangements changed?**
-Current deployment is documented as: [show from existing doc]
-a) **Same platform** - Just configuration updates
-b) **Platform migration** - Moved to different provider
-c) **Architecture change** - Serverless, containers, etc.
-d) **Multi-region** - Expanded geographic deployment
-**4. Database or storage changes?**
-a) **Version upgrade** - Same DB, newer version
-b) **Migration** - Switched database systems
-c) **New caching** - Added Redis, Memcached, etc.
-d) **Storage addition** - New file storage, CDN
-e) **No changes** - Same setup as before
-### 🛠️ Development Workflow Updates
-**5. New development tools or practices?**
-Select all that apply:
-- [ ] New testing framework or strategy
-- [ ] Added code quality tools (linters, formatters)
-- [ ] CI/CD pipeline changes
-- [ ] Docker/containerization adoption
-- [ ] New build tools or bundlers
-- [ ] Performance monitoring tools
-**6. External service integrations?**
-Have you added or changed:
-a) **Payment processing** - New or updated provider
-b) **Authentication** - Different auth service
-c) **Email/SMS** - Communication service changes
-d) **Monitoring** - New error tracking or analytics
-e) **APIs** - Additional third-party integrations
-f) **None** - Same external services
-### 🔐 Security & Compliance
-**7. Security tool adoption?**
-- [ ] Vulnerability scanning (Snyk, etc.)
-- [ ] Secret management changes
-- [ ] New authentication methods
-- [ ] Compliance tools (GDPR, etc.)
-- [ ] Security headers/policies
-- [ ] None of the above
-## Update Strategy
-### Version Precision
-```typescript
-// ❌ Outdated
-"next": "^13.0.0"
-// ✅ Current and precise
-"next": "14.2.5"
-```
-### Configuration Updates
-- Update all config examples to match current files
-- Include new configuration options
-- Remove deprecated settings
-- Add migration notes for breaking changes
-### New Technology Sections
-When adding major new tools:
-```markdown
-### [New Tool Category]
-**Tool:** [Name] [Version]
-**Purpose:** [Why it was adopted]
-**Configuration:** [Key settings]
-**Integration:** [How it connects with other tools]
-```
-## Document Update Areas
-### Always Check:
-1. **package.json changes**
-   ```bash
-   # Compare all dependencies
-   # Note version changes
-   # Identify new packages
-   ```
-2. **Configuration files**
-   - tsconfig.json updates
-   - New .config files
-   - Build tool configurations
-   - Linting rule changes
-3. **Development scripts**
-   - New npm/pnpm scripts
-   - Changed command purposes
-   - Removed scripts
-4. **Infrastructure files**
-   - Dockerfile changes
-   - CI/CD workflows
-   - Deployment configs
-   - Environment examples
-### Conditional Updates:
-- **Architecture:** Only if fundamental changes
-- **Conventions:** Only if standards changed
-## Execution Steps
-### 1. Start with Analysis
-```bash
-# Check current dependencies vs documented
-diff <(jq -r '.dependencies | keys[]' package.json | sort) \
-     <(grep -E '^\*\*.*:' .claude/docs/tech-stack.md | cut -d: -f1 | sed 's/\*//g' | sort)
-# Review recent dependency commits
-git log --oneline --grep="dep" --since="30 days ago"
-# Check for new config files
-find . -name "*.config.*" -newer .claude/docs/tech-stack.md 2>/dev/null
-```
-**Think deeply about:** "What technical decisions drove these changes? How do version updates affect the overall architecture? What new capabilities do these tools enable?"
-### 2. Interactive Q&A
-- Present technical questions clearly
-- Include current state from documentation
-- Wait for detailed responses
-### 3. Update Documentation
-Follow incremental approach:
-```markdown
-<!-- Version update example -->
-**Before:** React 18.2.0
-**After:** React 18.3.1 - Includes new compiler optimizations
-<!-- New tool example -->
-### Code Quality Tools
-**New Addition:**
-- **Biome:** 1.8.3 - Replaced ESLint and Prettier
-  - Faster performance (10x)
-  - Single configuration file
-  - Built-in formatting
-```
-### 4. Commands Update
-Update CLAUDE.md if new scripts discovered:
-```markdown
-### Development
-- `pnpm dev` - Start development server
-- `pnpm check` - NEW: Run Biome linting and formatting
-- `pnpm test:e2e` - NEW: Run Playwright tests
-```
-### 5. Save and Backup
-```bash
-# Optional backup
-cp .claude/docs/tech-stack.md .claude/docs/tech-stack.backup.md
-# Save updated document
-# Overwrite .claude/docs/tech-stack.md
-```
-## Key Principles
-### DO:
-- **Exact Versions:** Use precise version numbers from lock files
-- **Config Accuracy:** Match actual configuration files
-- **Change Rationale:** Explain why tools were adopted/changed
-- **Migration Notes:** Document breaking changes and updates
-- **Performance Impact:** Note improvements or concerns
-### DON'T:
-- **Generic Updates:** Avoid vague version ranges
-- **Assumption:** Verify every technical detail
-- **Old Information:** Remove outdated configurations
-- **Wishful Documentation:** Only document what exists
-- **Sensitive Data:** Never include secrets or keys
-## Output
-- **Format:** Markdown (`.md`)
-- **Location:** `.claude/docs/`
-- **Filename:** `tech-stack.md` (overwrites)
-- **Backup:** Suggest for major changes
-## Final Checklist
-1. ✅ Read existing tech-stack.md completely
-2. ✅ Analyze all dependency changes
-3. ✅ Check configuration file updates
-4. ✅ Review infrastructure changes
-5. ✅ Ask targeted technical questions
-6. ✅ Update with exact versions
-7. ✅ Include configuration examples
-8. ✅ Update CLAUDE.md commands
-9. ✅ Suggest backup if major changes
-10. ✅ Verify technical accuracy