Luxury Watch Trader

A luxury watch trading application powered by Claude Task Master AI.

Task Master Integration

This project is configured with Claude Task Master, an AI-powered task management system designed for AI-driven development workflows.

Getting Started with Task Master

1. Configure API Keys

Copy the example environment file and add your API keys:

cp .env.example .env

Edit .env and add at least one API key (Anthropic is required for the main model):

• ANTHROPIC_API_KEY (Required) - Your Claude API key from https://console.anthropic.com/
• PERPLEXITY_API_KEY (Optional) - For research features
• OPENAI_API_KEY (Optional) - For OpenAI models
• GOOGLE_API_KEY (Optional) - For Gemini models

2. Upload Your App Requirements

To start building your luxury watch trading application, you need to create a Product Requirements Document (PRD). Here's how:

Option 1: Create PRD from Template (Simple Projects)

1. Copy the simple template:

   cp .taskmaster/templates/example_prd.txt .taskmaster/docs/prd.txt
   

2. Edit .taskmaster/docs/prd.txt with your app requirements:

   • Overview: What problem does your luxury watch trading app solve?
   • Core Features: List trading features (marketplace, authentication, payment processing, etc.)
   • User Experience: Buyer/seller personas, user flows
   • Technical Architecture: Tech stack, APIs, database design
   • Development Roadmap: MVP features and future enhancements
   • Logical Dependency Chain: What needs to be built first

Option 2: Create PRD for Complex Projects

For more complex systems with dependencies:

1. Copy the advanced template:

   cp .taskmaster/templates/example_prd_rpg.txt .taskmaster/docs/prd.txt
   

2. This template provides more structure for dependency-aware task graphs

Option 3: Create PRD with AI

Simply discuss your idea with your AI assistant and ask it to generate a PRD for you, then save it to .taskmaster/docs/prd.txt.

3. Generate Tasks from PRD

Once your PRD is ready, you can:

Using MCP Tools (in your editor): Ask your AI assistant: "Parse the PRD at .taskmaster/docs/prd.txt and generate tasks"

Using CLI:

npx task-master parse-prd .taskmaster/docs/prd.txt

Or use the alias:

tm parse-prd .taskmaster/docs/prd.txt

4. Analyze Project Complexity

Ask your AI assistant to analyze the complexity:

• MCP Tool: analyze_project_complexity
• CLI: npx task-master analyze-complexity

5. Expand Tasks

Ask your AI assistant to expand all tasks using the complexity analysis. This breaks down high-level tasks into manageable subtasks.

6. Start Development

Ask your AI assistant to "begin working on the next task" and it will pull from your task queue and start implementing.

Available Commands

Task Master provides both CLI and MCP tool interfaces:

# View all tasks
npx task-master list

# Add a new task
npx task-master add-task "Task description"

# Get next task to work on
npx task-master next

# Show specific task details
npx task-master show <task-id>

# Update task status
npx task-master update-status <task-id> <status>

# Research a topic
npx task-master research "topic to research"

# Configure models
npx task-master models --setup

You can use the alias tm instead of npx task-master:

tm list
tm next
tm add-task "New feature"

MCP Configuration

Task Master has been configured for multiple editors:

• Cursor: .cursor/mcp.json
• VS Code: .vscode/mcp.json
• Windsurf: .windsurf/mcp.json
• Claude Desktop: .mcp.json
• Gemini: .gemini/settings.json
• Zed: .zed/settings.json

Your AI assistant can now use Task Master tools directly through the MCP protocol.

Project Structure

.taskmaster/
├── docs/          # Your PRDs and documentation
├── tasks/         # Generated task files
├── reports/       # Project complexity reports
├── templates/     # PRD templates
├── config.json    # Task Master configuration
└── state.json     # Current project state

Workflow

1. Define: Create your PRD in .taskmaster/docs/prd.txt
2. Parse: Generate tasks from the PRD
3. Analyze: Let AI analyze complexity
4. Expand: Break tasks into subtasks
5. Execute: Ask AI to work on next task
6. Iterate: Update tasks as you learn and pivot

Tips

• Start with a clear, detailed PRD
• Use the dependency chain to ensure foundational work is done first
• Update task status as you complete work
• Add new tasks as requirements emerge
• Use research tools to gather fresh information when needed

Development

To activate the shell aliases in your current terminal:

source ~/.bashrc

Now you can use tm instead of typing out the full command!