Initial commit

.claude/commands/task/add-interactive.md

@@ -0,0 +1,59 @@
+---
+allowed-tools: mcp__taskmaster-ai__add_task, TodoWrite
+description: Add tasks interactively with clarifying questions
+---
+
+# Add Tasks Interactively
+
+## Context
+
+- **User Request:** $ARGUMENTS
+- **Current Tag:** !`jq -r '.currentTag // "master"' .taskmaster/state.json 2>/dev/null || echo "master"`
+
+## Goal
+
+Create well-defined tasks by asking clarifying questions about the feature requirements.
+
+## Process
+
+1. **Analyze Feature Request:** Think deeply about what tasks might be needed.
+
+2. **Ask Clarifying Questions:**
+
+   - Ask 4-6 targeted questions based on the feature
+   - Provide lettered/numbered options for easy response
+   - Focus on understanding scope and breakdown
+
+3. **Generate Tasks:**
+   - Create tasks based on answers
+   - Add to current tag context
+
+## Clarifying Questions Framework
+
+Adapt questions based on the specific feature request provided above. Consider these areas:
+
+- **Scope:** "How big is this feature?"
+- **Components:** "What are the main parts that need to be built?"
+- **Dependencies:** "Does this depend on any existing tasks or features?"
+- **Priority:** "How urgent is this feature?"
+- **Testing:** "What kind of testing will this need?"
+- **Phases:** "Should this be built all at once or in phases?"
+
+## Final Instructions
+
+1. **Think deeply** about the feature request
+2. **Ask clarifying questions** with lettered/numbered options
+3. **Generate tasks** based on the answers
+4. **Add tasks** to the current tag context
+
+## Example Usage
+
+```
+/add-interactive user notification system
+```
+
+This will:
+
+1. Ask about notification types and delivery methods
+2. Understand scope and dependencies
+3. Create appropriate tasks based on answers

.claude/commands/task/add.md

@@ -0,0 +1,65 @@
+---
+allowed-tools: mcp__taskmaster-ai__add_task, TodoWrite
+description: Add one or more tasks to the current tag
+---
+
+# Add Tasks
+
+- **User Request:** $ARGUMENTS
+
+## Goal
+
+Add new tasks to your current tag context. Can handle single tasks or multiple tasks at once.
+
+## What You Can Say
+
+### Single Task
+
+```
+/add implement user login with email and password
+/add create API endpoint for user profile
+```
+
+### Multiple Tasks
+
+```
+/add
+1. Setup database schema
+2. Create user authentication
+3. Add email verification
+4. Implement password reset
+```
+
+### With Details
+
+```
+/add high priority: implement payment processing with Stripe
+/add depends on 5: add payment confirmation emails
+```
+
+## How It Works
+
+Based on your input (User Request), I'll:
+
+1. **Parse your request** - Single task or numbered list
+2. **Create tasks** in the current tag context
+3. **Set dependencies** if you mention "depends on X"
+4. **Set priority** if you mention high/medium/low
+5. **Confirm** what was added
+
+## Examples
+
+### Quick Add
+
+- `/add fix the login bug` → Creates task "fix the login bug"
+
+### Batch Add
+
+- `/add 1. Setup 2. Test 3. Deploy` → Creates 3 tasks
+
+### With Context
+
+- `/add urgent: fix security vulnerability in auth` → High priority task
+- `/add after task 3: add unit tests` → Sets dependency
+
+The command is smart enough to understand your intent from natural language.

.claude/commands/task/done.md

@@ -0,0 +1,21 @@
+---
+allowed-tools: mcp__taskmaster-ai__set_task_status, mcp__taskmaster-ai__next_task, TodoWrite
+description: Mark task as complete and optionally get next task
+---
+
+# Task Done
+
+**User Request:** $ARGUMENTS
+
+## Goal
+
+Mark task(s) as complete. By default, also shows the next task.
+
+## What You Can Say
+
+```
+/done 3                    # Mark task 3 as done, show next
+/done 3 stop               # Mark done, don't show next
+/done 5,7,9               # Mark multiple tasks done
+/done                     # Mark current task done (if tracking)
+```

.claude/commands/task/expand.md

@@ -0,0 +1,21 @@
+---
+allowed-tools: mcp__taskmaster-ai__expand_task, mcp__taskmaster-ai__expand_all
+description: Break down tasks into subtasks
+---
+
+# Expand Tasks
+
+**User Request:** $ARGUMENTS
+
+## Goal
+
+Break complex tasks into manageable subtasks.
+
+## What You Can Say
+
+```
+/expand 5                        # Break down task 5
+/expand 5 security focus         # With specific context
+/expand all                      # Expand all pending tasks
+/expand 5 research               # Use research for better breakdown
+```

.claude/commands/task/generate.md

@@ -0,0 +1,124 @@
+Generate individual task files from tasks.json.
+
+## Task File Generation
+
+Creates separate markdown files for each task, perfect for AI agents or documentation.
+
+## Execution
+
+```bash
+task-master generate
+```
+
+## What It Creates
+
+For each task, generates a file like `task_001.txt`:
+
+```
+Task ID: 1
+Title: Implement user authentication
+Status: pending
+Priority: high
+Dependencies: []
+Created: 2024-01-15
+Complexity: 7
+
+## Description
+Create a secure user authentication system with login, logout, and session management.
+
+## Details
+- Use JWT tokens for session management
+- Implement secure password hashing
+- Add remember me functionality
+- Include password reset flow
+
+## Test Strategy
+- Unit tests for auth functions
+- Integration tests for login flow
+- Security testing for vulnerabilities
+- Performance tests for concurrent logins
+
+## Subtasks
+1.1 Setup authentication framework (pending)
+1.2 Create login endpoints (pending)
+1.3 Implement session management (pending)
+1.4 Add password reset (pending)
+```
+
+## File Organization
+
+Creates structure:
+
+```
+.taskmaster/
+└── tasks/
+    ├── task_001.txt
+    ├── task_002.txt
+    ├── task_003.txt
+    └── ...
+```
+
+## Smart Features
+
+1. **Consistent Formatting**
+
+   - Standardized structure
+   - Clear sections
+   - AI-readable format
+   - Markdown compatible
+1. **Contextual Information**
+
+   - Full task details
+   - Related task references
+   - Progress indicators
+   - Implementation notes
+1. **Incremental Updates**
+
+   - Only regenerate changed tasks
+   - Preserve custom additions
+   - Track generation timestamp
+   - Version control friendly
+
+## Use Cases
+
+- **AI Context**: Provide task context to AI assistants
+- **Documentation**: Standalone task documentation
+- **Archival**: Task history preservation
+- **Sharing**: Send specific tasks to team members
+- **Review**: Easier task review process
+
+## Generation Options
+
+Based on arguments:
+
+- Filter by status
+- Include/exclude completed
+- Custom templates
+- Different formats
+
+## Post-Generation
+
+```
+Task File Generation Complete
+━━━━━━━━━━━━━━━━━━━━━━━━━━
+Generated: 45 task files
+Location: .taskmaster/tasks/
+Total size: 156 KB
+
+New files: 5
+Updated files: 12
+Unchanged: 28
+
+Ready for:
+- AI agent consumption
+- Version control
+- Team distribution
+```
+
+## Integration Benefits
+
+- Git-trackable task history
+- Easy task sharing
+- AI tool compatibility
+- Offline task access
+- Backup redundancy

.claude/commands/task/list.md

@@ -0,0 +1,21 @@
+---
+allowed-tools: mcp__taskmaster-ai__get_tasks
+description: List all tasks in current tag
+---
+
+# List Tasks
+
+**User Request:** $ARGUMENTS
+
+## Goal
+
+Show all tasks with their status, priority, and progress.
+
+## What You Can Say
+
+```
+/list              # All tasks
+/list pending      # Only pending tasks
+/list done         # Completed tasks
+/list blocked      # Blocked tasks
+```

.claude/commands/task/move.md

@@ -0,0 +1,21 @@
+---
+allowed-tools: mcp__taskmaster-ai__move_task
+description: Reorganize task structure
+---
+
+# Move Tasks
+
+**User Request:** $ARGUMENTS
+
+## Goal
+
+Move tasks to different positions or parents.
+
+## What You Can Say
+
+```
+/move 5.2 to 7.3              # Move subtask to different parent
+/move 5 to 25                 # Move to new position
+/move 10,11,12 to 16,17,18    # Move multiple tasks
+/move 5.2 to 7                # Subtask becomes standalone
+```

.claude/commands/task/next.md

@@ -0,0 +1,18 @@
+---
+allowed-tools: mcp__taskmaster-ai__next_task, mcp__taskmaster-ai__get_task, TodoWrite, Read, Write, MultiEdit, Bash, Grep, Glob
+description: Get next task and start implementing it immediately
+---
+
+# Next Task & Implement
+
+**User Request:** $ARGUMENTS
+
+## Goal
+
+Find the next task and start implementing it right away (unless you say otherwise).
+
+## How It Works
+
+1. **Find next task** based on priorities and dependencies
+2. **Show task details** briefly
+3. **Start implementation** immediately

.claude/commands/task/research.md

@@ -0,0 +1,32 @@
+---
+allowed-tools: mcp__taskmaster-ai__research, mcp__taskmaster-ai__update_task, mcp__taskmaster-ai__update_subtask
+description: Research best practices and update tasks
+---
+
+# Research for Tasks
+
+- **User Request:** $ARGUMENTS
+
+## Goal
+
+Research current best practices, or solutions to help with task implementation.
+
+## What You Can Say
+
+```
+"Research JWT security best practices for task 5"
+"What's the best way to handle file uploads in Next.js?"
+"Research MongoDB vs PostgreSQL for our use case"
+"Find React Query v5 migration guide"
+```
+
+## How It Works
+
+I'll research what you asked about (User Request) and:
+
+1. **Get current information** beyond my knowledge cutoff
+2. **Include relevant context** from your project if needed
+3. **Show you the findings**
+4. **Update tasks** if you mentioned specific ones
+
+Just tell me what you need to know and optionally which task it's for.

.claude/commands/task/show.md

@@ -0,0 +1,20 @@
+---
+allowed-tools: mcp__taskmaster-ai__get_task
+description: Show specific task details
+---
+
+# Show Task
+
+**User Request:** $ARGUMENTS
+
+## Goal
+
+Display detailed information about specific task(s).
+
+## What You Can Say
+
+```
+/show 5           # Show task 5
+/show 5,7,9       # Show multiple tasks
+/show 5.2         # Show subtask
+```

.claude/commands/task/spec.md

@@ -0,0 +1,77 @@
+# End-to-End Feature Implementation Guide
+
+## Context
+
+- When implementing new end-to-end features
+- When planning feature development workflow
+- When ensuring consistent architecture
+
+## Requirements
+
+- Follow the implementation steps in order
+- Use the appropriate standards for each step
+- Ensure consistency across all implementation layers
+- Test each phase before moving to the next
+
+## Implementation Steps
+
+1. **Schema Definition** → Use rule @.cursor/rules/2101-schema-prisma.mdc
+
+   - Define Prisma schema with standard fields
+   - Add proper relations and indexes
+   - Use correct field types and constraints
+   - Follow naming conventions
+
+2. **Router Implementation** → Use rule @.cursor/rules/2102-router.mdc
+
+   - Create protected tRPC router
+   - Add input validation with Zod
+   - Implement cursor-based pagination
+   - Handle security and responses
+
+3. **React Query Integration** → Use rule @.cursor/rules/2103-trpc-react-query.mdc
+
+   - Set up queries with queryOptions
+   - Handle loading states
+   - Implement optimistic updates
+   - Manage cache invalidation
+
+4. **CRUD Implementation** → Use rule @.cursor/rules/2105-crud.mdc
+
+   - Follow phased implementation approach
+   - Start with Create & Read operations
+   - Add Update & Delete operations
+   - Implement advanced features last
+
+5. **Authentication** → Use rule @.cursor/rules/2106-auth.mdc
+   - Use protectedProcedure for routes
+   - Add session checks in components
+   - Implement auth guards
+   - Handle unauthorized states
+
+## Examples
+
+<example>
+```typescript
+// Implementation follows all steps in order
+// 1. Schema defined in prisma/schema.prisma
+// 2. Router implemented in src/server/api/routers/item.ts
+// 3. React Query integration in src/components/ItemList.tsx
+// 4. CRUD operations implemented in phases
+// 5. Authentication checks in all appropriate places
+```
+Complete feature implementation following all steps in order
+</example>
+
+<example type="invalid">
+```typescript
+// Implementation skips steps or does them out of order
+// Missing schema definition
+// Incomplete router implementation
+// Using old tRPC patterns instead of React Query
+// Missing error handling
+// Implementing all CRUD operations at once
+// Missing authentication checks
+```
+Incomplete or out-of-order implementation missing critical steps
+</example>

.claude/commands/task/update-task-interactive.md

@@ -0,0 +1,59 @@
+---
+allowed-tools: mcp__taskmaster-ai__update, mcp__taskmaster-ai__update_task, mcp__taskmaster-ai__update_subtask, mcp__taskmaster-ai__get_tasks
+description: Update tasks interactively with clarifying questions
+---
+
+# Update Tasks Interactively
+
+## Context
+
+- **User Request:** $ARGUMENTS
+- **Current Tag:** !`jq -r '.currentTag // "master"' .taskmaster/state.json 2>/dev/null || echo "master"`
+
+## Goal
+
+Update tasks based on implementation changes by asking clarifying questions to ensure accurate updates.
+
+## Process
+
+1. **Analyze Change:** Think deeply about the implications of the change.
+
+2. **Ask Clarifying Questions:**
+
+   - Ask 4-6 targeted questions about the change
+   - Provide lettered/numbered options for easy response
+   - Focus on understanding impact and scope
+
+3. **Update Tasks:**
+   - Update affected tasks based on answers
+   - Show what was changed
+
+## Clarifying Questions Framework
+
+Adapt questions based on the change described above. Consider these areas:
+
+- **Scope:** "Which tasks are affected by this change?"
+- **Reason:** "Why was this change made?"
+- **Impact:** "How does this affect the implementation approach?"
+- **Dependencies:** "Does this change affect task dependencies?"
+- **Testing:** "How should test strategies be updated?"
+- **Documentation:** "What additional context should be added?"
+
+## Final Instructions
+
+1. **Think deeply** about the change and its implications
+2. **Ask clarifying questions** with lettered/numbered options
+3. **Update tasks** based on the answers
+4. **Confirm** what was updated
+
+## Example Usage
+
+```
+/project:task:update-interactive switching to microservices architecture
+```
+
+This will:
+
+1. Ask about which components are affected
+2. Understand the migration approach
+3. Update relevant tasks with new architecture details

.claude/commands/task/update-task.md

@@ -0,0 +1,30 @@
+---
+allowed-tools: mcp__taskmaster-ai__update, mcp__taskmaster-ai__update_task, mcp__taskmaster-ai__update_subtask, mcp__taskmaster-ai__get_tasks
+description: Update tasks based on implementation changes
+---
+
+# Update Tasks
+
+**User Request:** $ARGUMENTS
+
+## Goal
+
+Update tasks when implementation changes from the original plan. Just tell me what changed and I'll update the relevant tasks.
+
+## What You Can Say
+
+```
+"We're using MongoDB instead of PostgreSQL"
+"Update task 5 to use OAuth instead of JWT"
+"All tasks from 10 onwards should use the new API structure"
+"Task 7.2 needs a note about the Redis caching we added"
+```
+
+## How It Works
+
+Based on what you tell me (User Request), I'll:
+
+1. **Understand the change** from your description
+2. **Find affected tasks** automatically or use the ones you specify
+3. **Update them** with the new approach
+4. **Confirm** what was updated