feat: Simplified MCP prompts, compact access patterns

Author: tebanieo

workshops/modernizr/prompts/01-mysql-analysis/tasks.md

@@ -6,12 +6,13 @@
 - **Mark tasks as completed** by changing `[ ]` to `[x]` as you finish each task
 - **Commit after each major task completion** with descriptive messages
 - **Update the tasks.md file** itself when marking tasks complete and commit those changes too
+- **Use single working log**: Use `artifacts/stage-01/01_working_log.md` throughout the entire stage (not individual logs per subtask)
 - **DO NOT MODIFY THE CONTENT OF THIS FILE**: Only add a [x] mark to complete the task, for tracking purposes.
 - [ ] 0. Set up Git source control for the project
   - Initialize GIT at the root of this workspace so you have a point to revert your changes if needed in the future
   - You must always use git -P to avoid getting stuck in git operations
   - The subfolders have compiled projects, make sure to create a gitignore so you track only what you will be modifying not the compiled version or the node_modules
-  - Use a temporary file called `artifacts/stage-00/00_0_working_log.md` so you can track what is your current work and important notes and use it as a reference
+  - Use a temporary file called `artifacts/stage-01/01_working_log.md` to track your current work and important notes throughout this entire stage
   - Update the file task.md once completed, please let the user know that you have completed this task and summarize what has been done
   - Commit the latest changes registered in the working log and other artifacts
   - _Requirements: 1.1, 1.2, 1.3, 1.4, 1.5_
@@ -20,34 +21,47 @@
   - Make sure you have a clean commit log
   - From the backend/ folder use the README.md to understand its API endpoints
   - Explore the backend/ folder to understand in detail the available access patterns
+  - **CRITICAL**: This analysis defines the PRIMARY access patterns that MUST be supported in DynamoDB design
+  - **CRITICAL**: These API patterns are the authoritative source for what the application needs to do
   - Generate a file where you store the results of your investigation in `artifacts/stage-01/` under the name `01_1_API_access_patterns.md`
-  - Use a temporary file called `artifacts/stage-01/01_1_working_log.md` so you can track what is your current work and important notes and use it as a reference
-  - The result of the API access patterns must include a detailed explanation on the relationship between the different entities
+  - Use the working log file `artifacts/stage-01/01_working_log.md` to track your current work and important notes
+  - The result of the API access patterns must include:
+    - Complete list of all API endpoints and their data access requirements
+    - Detailed explanation on the relationship between the different entities
+    - Enumerate the access patterns so it is easier to know how many the application will need to support
+    - **Clear statement**: "These patterns represent ALL access patterns that must be supported in the DynamoDB design"
   - Update the file task.md once completed, please let the user know that you have completed this task and summarize what has been done
   - _Requirements: 3.3, 4.2, 4.4_
 
-- [ ] 2. Analyze MySQL database logs for performance patterns
+- [ ] 2. Analyze MySQL database logs for performance data
   - Make sure you have a clean commit log
   - From the database/ folder use the mysql_log_parser.py script to capture mysql query statistics and performance data
-  - Generate `artifacts/stage-01/01_2_mysql_log_analysis.md` with comprehensive analysis of:
-    - Query frequency and patterns from log analysis
-    - Performance bottlenecks and slow queries
-    - Access pattern identification from actual usage
-    - RPS estimates based on log data
-  - Use a temporary file called `artifacts/stage-01/01_2_working_log.md` to track your current work and important notes
+  - **CRITICAL**: This analysis provides SUPPLEMENTAL performance metrics for the API patterns identified in task 1
+  - **IMPORTANT**: Logs may not contain data for all API endpoints - this is expected and acceptable
+  - **IMPORTANT**: The API patterns from task 1 are the complete requirements; logs provide performance context where available
+  - Generate `artifacts/stage-01/01_2_mysql_log_analysis.md` with analysis focused on:
+    - Query frequency and performance metrics for queries that appear in logs
+    - Performance bottlenecks and slow queries identified from actual usage
+    - RPS estimates based on log data WHERE AVAILABLE
+    - **Explicit statement**: "This log analysis provides performance data for observed queries only. Complete access pattern requirements come from API analysis in task 1."
+  - Use the working log file `artifacts/stage-01/01_working_log.md` to track your current work and important notes
   - Update the file task.md once completed, please let the user know that you have completed this task and summarize what has been done
+  - DO NOT SUGGEST A DYNAMODB TABLE STRUCTURE - focus only on current MySQL analysis
   - _Requirements: 2.1, 2.2, 2.3, 2.4, 2.5, 2.6_
 
-- [ ] 3. Extract table structure using MySQL MCP server
+- [ ] 3. Extract complete table structure using MySQL MCP server
   - Make sure you have a clean commit log
   - Use the MySQL MCP server's execute_sql tool to run SQL queries and collect the actual schema information deployed in the database
   - Write and execute SQL queries to extract table structures, relationships, indexes, and constraints for the online shopping store database
+  - **CRITICAL**: This analysis provides the COMPLETE data model that supports the API patterns from task 1
+  - **CRITICAL**: This contains ALL entities, relationships, and data structures - even those not visible in logs
   - Generate `artifacts/stage-01/01_3_table_structure_analysis.md` with comprehensive documentation of:
-    - Complete table definitions with columns, data types, and constraints
-    - Primary keys, foreign keys, and indexes
-    - Entity relationships and cardinalities
-    - Current database schema structure
-  - Use a temporary file called `artifacts/stage-01/01_3_working_log.md` to track your current work and important notes
+    - Complete table definitions with columns, data types, and constraints for ALL tables
+    - Primary keys, foreign keys, and indexes for the complete schema
+    - Entity relationships and cardinalities for all entities
+    - Current database schema structure showing the complete data model
+    - **Clear statement**: "This represents the complete source data model that must be migrated to DynamoDB"
+  - Use the working log file `artifacts/stage-01/01_working_log.md` to track your current work and important notes
   - DO NOT SUGGEST A DYNAMODB TABLE STRUCTURE - focus only on current MySQL analysis
   - Update the file task.md once completed, please let the user know that you have completed this task and summarize what has been done
   - _Requirements: 3.1, 3.2, 3.4, 3.5, 4.1, 4.3, 4.5_
@@ -56,16 +70,17 @@
 
 Before marking this stage complete, verify:
 - [ ] Git repository initialized with proper .gitignore
-- [ ] Working log files created in artifacts/stage-00/ and artifacts/stage-01/ directories
+- [ ] Single working log file created: `artifacts/stage-01/01_working_log.md`
 - [ ] **Three essential artifacts created**:
   - [ ] `artifacts/stage-01/01_1_API_access_patterns.md` - Backend API endpoints and access patterns from API specifications
   - [ ] `artifacts/stage-01/01_2_mysql_log_analysis.md` - Performance patterns and query statistics from mysql_log_parser.py
   - [ ] `artifacts/stage-01/01_3_table_structure_analysis.md` - Complete table structures and relationships from MySQL MCP server
-- [ ] API analysis includes detailed endpoint documentation and entity relationships
-- [ ] MySQL log analysis provides query frequency, performance bottlenecks, and RPS estimates
-- [ ] Table structure analysis includes complete schema with relationships, indexes, and constraints
-- [ ] All MySQL tables, relationships, and constraints are documented
-- [ ] Performance data from log analysis is comprehensive
+- [ ] **API analysis defines PRIMARY access patterns**: Complete list of all API endpoints that must be supported in DynamoDB
+- [ ] **MySQL log analysis provides SUPPLEMENTAL performance data**: RPS estimates and performance metrics where available in logs
+- [ ] **Table structure analysis provides COMPLETE data model**: All entities, relationships, and constraints from the source database
+- [ ] API patterns clearly marked as authoritative requirements for DynamoDB design
+- [ ] Log analysis explicitly notes it may not cover all API patterns
+- [ ] Table structure includes complete schema documentation for migration
 - [ ] Documentation focuses on current state analysis without DynamoDB suggestions
 - [ ] All changes are committed to Git with meaningful messages
 

workshops/modernizr/prompts/02-a-dynamodb-data-modeling/design.md

@@ -74,11 +74,8 @@ graph TD
 - RPS estimates based on actual usage
 
 ## Design Constraints and Preferences
-- Multi-table first approach (not single-table)
-- Natural keys preferred (user_id, order_id vs PK, SK)
-- Access pattern driven design
-- Cost optimization important
-- Hot partition avoidance critical
+- Let MCP server determine optimal approach based on access patterns and data model
+- No predetermined design preferences to avoid biasing the analysis
 ```
 
 ### 2. MCP Server Integration System
@@ -96,9 +93,8 @@ interface MCPDynamoDBDesignRequest {
         mysql_schema: MySQLSchema;
     };
     design_preferences: {
-        approach: "multi-table" | "single-table";
-        key_style: "natural" | "generic";
-        optimization_priority: "cost" | "performance" | "simplicity";
+        // Let MCP server determine optimal approach
+        // No predetermined preferences to avoid bias
     };
     constraints: {
         rps_requirements: Record<string, number>;