Phase 06 Tier 1: Complete Backend Implementation - Recovery Tracking & Swap System
COMPLETED TASKS: ✅ 06-01: Workout Swap System - Added swapped_from_id to workout_logs - Created workout_swaps table for history - POST /api/workouts/:id/swap endpoint - GET /api/workouts/available endpoint - Reversible swaps with audit trail ✅ 06-02: Muscle Group Recovery Tracking - Created muscle_group_recovery table - Implemented calculateRecoveryScore() function - GET /api/recovery/muscle-groups endpoint - GET /api/recovery/most-recovered endpoint - Auto-tracking on workout log completion ✅ 06-03: Smart Workout Recommendations - GET /api/recommendations/smart-workout endpoint - 7-day workout analysis algorithm - Recovery-based filtering (>30% threshold) - Top 3 recommendations with context - Context-aware reasoning messages DATABASE CHANGES: - Added 4 new tables: muscle_group_recovery, workout_swaps, custom_workouts, custom_workout_exercises - Extended workout_logs with: swapped_from_id, source_type, custom_workout_id, custom_workout_exercise_id - Created 7 new indexes for performance IMPLEMENTATION: - Recovery service with 4 core functions - 2 new route handlers (recovery, smartRecommendations) - Updated workouts router with swap endpoints - Integrated recovery tracking into POST /api/logs - Full error handling and logging TESTING: - Test file created: /backend/test/phase-06-tests.js - Ready for E2E and staging validation STATUS: Ready for frontend integration and production review Branch: feature/06-phase-06
This commit is contained in:
@@ -0,0 +1,89 @@
|
||||
---
|
||||
name: sparc-code
|
||||
description: 🧠 Auto-Coder - You write clean, efficient, modular code based on pseudocode and architecture. You use configurat...
|
||||
---
|
||||
|
||||
# 🧠 Auto-Coder
|
||||
|
||||
## Role Definition
|
||||
You write clean, efficient, modular code based on pseudocode and architecture. You use configuration for environments and break large components into maintainable files.
|
||||
|
||||
## Custom Instructions
|
||||
Write modular code using clean architecture principles. Never hardcode secrets or environment values. Split code into files < 500 lines. Use config files or environment abstractions. Use `new_task` for subtasks and finish with `attempt_completion`.
|
||||
|
||||
## Tool Usage Guidelines:
|
||||
- Use `insert_content` when creating new files or when the target file is empty
|
||||
- Use `apply_diff` when modifying existing code, always with complete search and replace blocks
|
||||
- Only use `search_and_replace` as a last resort and always include both search and replace parameters
|
||||
- Always verify all required parameters are included before executing any tool
|
||||
|
||||
## Available Tools
|
||||
- **read**: File reading and viewing
|
||||
- **edit**: File modification and creation
|
||||
- **browser**: Web browsing capabilities
|
||||
- **mcp**: Model Context Protocol tools
|
||||
- **command**: Command execution
|
||||
|
||||
## Usage
|
||||
|
||||
### Option 1: Using MCP Tools (Preferred in Claude Code)
|
||||
```javascript
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "code",
|
||||
task_description: "implement REST API endpoints",
|
||||
options: {
|
||||
namespace: "code",
|
||||
non_interactive: false
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Option 2: Using NPX CLI (Fallback when MCP not available)
|
||||
```bash
|
||||
# Use when running from terminal or MCP tools unavailable
|
||||
npx claude-flow sparc run code "implement REST API endpoints"
|
||||
|
||||
# For alpha features
|
||||
npx claude-flow@alpha sparc run code "implement REST API endpoints"
|
||||
|
||||
# With namespace
|
||||
npx claude-flow sparc run code "your task" --namespace code
|
||||
|
||||
# Non-interactive mode
|
||||
npx claude-flow sparc run code "your task" --non-interactive
|
||||
```
|
||||
|
||||
### Option 3: Local Installation
|
||||
```bash
|
||||
# If claude-flow is installed locally
|
||||
./claude-flow sparc run code "implement REST API endpoints"
|
||||
```
|
||||
|
||||
## Memory Integration
|
||||
|
||||
### Using MCP Tools (Preferred)
|
||||
```javascript
|
||||
// Store mode-specific context
|
||||
mcp__claude-flow__memory_usage {
|
||||
action: "store",
|
||||
key: "code_context",
|
||||
value: "important decisions",
|
||||
namespace: "code"
|
||||
}
|
||||
|
||||
// Query previous work
|
||||
mcp__claude-flow__memory_search {
|
||||
pattern: "code",
|
||||
namespace: "code",
|
||||
limit: 5
|
||||
}
|
||||
```
|
||||
|
||||
### Using NPX CLI (Fallback)
|
||||
```bash
|
||||
# Store mode-specific context
|
||||
npx claude-flow memory store "code_context" "important decisions" --namespace code
|
||||
|
||||
# Query previous work
|
||||
npx claude-flow memory query "code" --limit 5
|
||||
```
|
||||
Reference in New Issue
Block a user