vibefast-cli 0.6.2 → 0.7.1

package/2/.claude/commands/create-prd-interactive.md

@@ -1,113 +0,0 @@
----
-allowed-tools: Bash, Read, Write, Glob, Grep, Task, TodoWrite, mcp__taskmaster-ai__parse_prd
-description: Generate a PRD interactively with clarifying questions for complex features
----
-
-# Generate a Product Requirements Document (PRD)
-
-## Context
-
-- **User Request:** $ARGUMENTS
-- **Project Root:** !`pwd`
-- **Existing PRDs:** !`ls -la .claude/docs/prd-*.md 2>/dev/null || echo "No existing PRDs found"`
-- **Project Status:** @CLAUDE.md#project-status
-- **Tech Stack:** @.claude/docs/tech-stack.md
-- **Project Structure:** !`bash .claude/scripts/tree.sh`
-- **PRD Template:** @.taskmaster/templates/example_prd.md
-
-## Goal
-
-To create a detailed Product Requirements Document (PRD) in Markdown format. The PRD should be clear, actionable, and suitable for a junior developer to understand and implement.
-
-## Process
-
-1. **Analyze Feature Request:** Think deeply about the user's feature request and its implications for the codebase.
-
-2. **Codebase Analysis:**
-   - Search for relevant existing code patterns
-   - Review components that might be affected
-   - Identify potential integration points
-   - Consider architectural impacts
-
-3. **Ask Clarifying Questions:**
-   - Ask 4-6 targeted questions based on codebase analysis
-   - Provide lettered/numbered options for easy response
-   - Focus on understanding the "what" and "why", not the "how"
-
-4. **Generate PRD:**
-   - Follow the example PRD structure exactly
-   - Include all required sections from the template
-   - Ensure clarity for junior developers
-
-5. **Save and Next Steps:**
-   - Save as `prd-[feature-name].md` in `.claude/docs/`
-   - Suggest running Task Master parse command
-
-## Clarifying Questions Framework
-
-Adapt questions based on the specific feature request provided above. Consider these areas:
-
-- **Problem/Goal:** "What problem does this feature solve for the user?" or "What is the main goal we want to achieve with this feature?"
-- **Target User:** "Who is the primary user of this feature?"
-- **Core Functionality:** "Can you describe the key actions a user should be able to perform with this feature?"
-- **User Stories:** "Could you provide a few user stories? (e.g., As a [type of user], I want to [perform an action] so that [benefit].)"
-- **User Experience:** "Describe the user journey and key user flows for this feature"
-- **Scope/Boundaries:** "Are there any specific things this feature _should not_ do (non-goals)?"
-- **Technical Integration:** "What existing systems or components should this integrate with?"
-- **Data Requirements:** "What kind of data does this feature need to display or manipulate?"
-- **Design/UI:** "Are there any existing design patterns or UI guidelines to follow?" or "Can you describe the desired look and feel?"
-- **Development Phases:** "Should this be built in phases? What's the MVP vs future enhancements?"
-- **Dependencies:** "What needs to be built first? Are there logical dependencies?"
-- **Success Criteria:** "How will we know when this feature is successfully implemented?"
-- **Edge Cases:** "Are there any potential risks or technical challenges we should consider?"
-
-## PRD Structure Requirements
-
-The PRD must follow the exact structure from @.taskmaster/templates/example_prd.md:
-
-### `<context>` Section
-
-1. **Overview:** High-level overview of the product/feature, what problem it solves, who it's for, and why it's valuable
-2. **Project Context:** Include the standard project status information. CRITICIAL: DO NOT forget this section. Read the mentioned files if needed.
-3. **Core Features:** List and describe the main features, including what each does, why it's important, and how it works at a high level
-4. **User Experience:** Describe user personas, key user flows, and UI/UX considerations
-
-### `<PRD>` Section
-
-1. **Technical Architecture:** System components, data models, APIs and integrations, infrastructure requirements
-2. **Development Roadmap:** Break down into phases (MVP requirements, future enhancements) focusing on scope and detailing exactly what needs to be built
-3. **Logical Dependency Chain:** Define the logical order of development, which features need to be built first, getting quickly to something usable/visible, properly pacing and scoping each feature without time estimates
-4. **Risks and Mitigations:** Technical challenges, figuring out the MVP that can be built upon, resource constraints
-5. **Appendix:** Research findings, technical specifications, additional information
-
-## Target Audience
-
-Assume the primary reader of the PRD is a **junior developer**. Therefore, requirements should be explicit, unambiguous, and avoid jargon where possible. Provide enough detail for them to understand the feature's purpose and core logic.
-
-## Output
-
-- **Format:** Markdown (`.md`)
-- **Location:** `.claude/docs/`
-- **Filename:** `prd-[feature-name].md`
-
-## Final Instructions
-
-1. **Think deeply** about the feature request and its architectural implications
-2. **Do NOT start implementing** - only create the PRD document
-3. **Ask clarifying questions** with lettered/numbered options
-4. **Generate complete PRD** following the template structure exactly
-5. **Save the PRD** to `.claude/docs/prd-[feature-name].md`
-6. **Suggest next step:** "Use `/parse` or `task-master parse-prd .claude/docs/prd-[feature-name].md` to convert this PRD into Task Master tasks"
-
-## Example Usage
-
-```
-/project:prd user authentication system
-```
-
-This will:
-
-1. Analyze the codebase for existing auth patterns
-2. Ask questions about auth requirements
-3. Generate a comprehensive PRD
-4. Save it as `prd-user-authentication.md`

package/2/.claude/commands/create-prd.md

@@ -1,111 +0,0 @@
----
-allowed-tools: Bash, Read, Write, Glob, Grep, Task, TodoWrite, mcp__taskmaster-ai__parse_prd
-description: Generate a PRD directly without questions for simple, well-defined features
----
-
-# Generate a Quick Product Requirements Document (PRD)
-
-## Context
-
-- **User Request:** $ARGUMENTS
-- **Project Root:** !`pwd`
-- **Existing PRDs:** !`ls -la .claude/docs/prd-*.md 2>/dev/null || echo "No existing PRDs found"`
-- **Project Status:** @CLAUDE.md#project-status
-- **Project Structure:** !`bash .claude/scripts/tree.sh`
-- **Tech Stack:** @.claude/docs/tech-stack.md
-- **PRD Template:** @.taskmaster/templates/example_prd.md
-
-## Goal
-
-To quickly create a Product Requirements Document (PRD) without asking clarifying questions. Best suited for simple, well-defined features where requirements are clear.
-
-## Process
-
-1. **Analyze Feature Request:**
-   - Think deeply about the user's feature request
-   - Make reasonable assumptions based on common patterns
-   - Review existing codebase for context
-
-2. **Codebase Analysis:**
-   - Search for relevant existing code patterns
-   - Review components that might be affected
-   - Identify potential integration points
-   - Consider architectural impacts
-
-3. **Generate PRD Immediately:**
-   - Follow the example PRD structure exactly
-   - Include all required sections from the template
-   - Make reasonable assumptions for unclear requirements
-   - Document assumptions clearly in the PRD
-
-4. **Save and Next Steps:**
-   - Save as `prd-[feature-name].md` in `.claude/docs/`
-   - Suggest running Task Master parse command
-
-## PRD Structure Requirements
-
-The PRD must follow the exact structure from @.taskmaster/templates/example_prd.md:
-
-### `<context>` Section
-
-1. **Overview:** High-level overview of the product/feature, what problem it solves, who it's for, and why it's valuable
-2. **Project Context:** Include the standard project status information. CRITICAL: DO NOT forget this section. Read the mentioned files if needed.
-3. **Core Features:** List and describe the main features, including what each does, why it's important, and how it works at a high level
-4. **User Experience:** Describe user personas, key user flows, and UI/UX considerations
-
-### `<PRD>` Section
-
-1. **Technical Architecture:** System components, data models, APIs and integrations, infrastructure requirements
-2. **Development Roadmap:** Break down into phases (MVP requirements, future enhancements) focusing on scope and detailing exactly what needs to be built
-3. **Logical Dependency Chain:** Define the logical order of development, which features need to be built first, getting quickly to something usable/visible, properly pacing and scoping each feature without time estimates
-4. **Risks and Mitigations:** Technical challenges, figuring out the MVP that can be built upon, resource constraints
-5. **Appendix:** Research findings, technical specifications, additional information
-
-## Assumptions Section
-
-When using quick mode, include an "Assumptions" section at the beginning of the PRD documenting:
-
-- Key assumptions made about requirements
-- Default choices for ambiguous features
-- Suggested areas that may need refinement
-
-## Final Instructions
-
-1. **Think deeply** about the feature request and make intelligent assumptions
-2. **Do NOT ask questions** - proceed directly to PRD generation
-3. **Document assumptions** clearly in the PRD
-4. **Generate complete PRD** following the template structure exactly
-5. **Save the PRD** to `.claude/docs/prd-[feature-name].md`
-6. **Suggest next step:** "Use `/parse` or `task-master parse-prd .claude/docs/prd-[feature-name].md` to convert this PRD into Task Master tasks"
-
-## Example Usage
-
-```
-/project:prd-quick user profile page with avatar upload
-```
-
-This will:
-
-1. Analyze the codebase for existing user/profile patterns
-2. Make assumptions about profile fields and avatar requirements
-3. Generate a comprehensive PRD immediately
-4. Save it as `prd-user-profile-page.md`
-5. Document all assumptions made
-
-## When to Use Quick Mode
-
-✅ **Good for:**
-
-- Simple CRUD features
-- Standard UI components
-- Well-defined integrations
-- Features with clear precedent in codebase
-
-❌ **Avoid for:**
-
-- Complex architectural changes
-- Features with many unknowns
-- Security-critical features
-- Features affecting multiple systems
-
-For complex features, use `/project:prd` for the full interactive process.

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
-```