@skyramp/mcp 0.0.25 → 0.0.27

package/build/prompts/modularization-prompts.js

@@ -13,12 +13,35 @@ Only if NO existing function can be reused:
 4. Parameterize the test function(s) with meaningful parameters to make it more flexible. Preserve the original order of code lines within each function.
 5. Only extract reusable logical sections into helper functions. Use inline parameter types instead of creating interfaces or type definitions.
 
+**IMPORT CLEANUP AFTER MODULARIZATION:**
+After applying modularization principles:
+1. **Analyze Remaining Imports**: Review all import statements at the top of the file
+2. **Identify Unused Imports**: Check which imported modules, functions, or classes are no longer referenced in the modularized code
+3. **Remove Unused Imports**: Delete any import statements that are not used in the final modularized code
+4. **Preserve Required Imports**: Keep all imports that are actually used by the modularized functions
+5. **Maintain Import Order**: Preserve the original ordering of remaining imports for consistency
+
+**IMPORT REMOVAL RULES:**
+- Only remove imports that are completely unused after modularization
+- Keep imports used by any function, even if usage decreased
+- Preserve imports for types used in function parameters (inline types)
+- Do not remove imports for testing frameworks or utilities
+- Maintain proper import syntax and formatting
+
+**LANGUAGE-SPECIFIC IMPORT HANDLING:**
+- **Python**: Remove unused import and from...import statements
+- **JavaScript/TypeScript**: Remove unused import and require() statements
+- **Java**: Remove unused import statements
+- **All Languages**: Preserve framework-specific imports (testing libraries, etc.)
+
 **CRITICAL CONSTRAINTS:**
 - NO interfaces, classes, types, or data structures
 - NO new test cases or logic
 - NO additional files
 - ONLY helper functions with inline types
 - PRESERVE original functionality exactly
+- REMOVE unused imports after modularization
+- DO NOT CREATE/UPDATE package.json or requirements.txt or pom.xml or build.gradle file
 
 **CRITICAL: If you skip any step, the modularization is incomplete. You MUST complete all steps before proceeding.FIX ERRORS IN MODULARIZED CODE USING skyramp_fix_errors TOOL**
 `;
@@ -30,11 +53,20 @@ export function getFixErrorsPrompt() {
 1. **Parameter Passing:** Identify functions using variables from outside scope (like 'page' object). Pass these as parameters.
 2. **Validate Correctness:** Ensure code is free of reference errors, undefined variables, runtime issues.
 3. **Import Paths:** Ensure import paths are correct and there are no circular imports.
-4. **UI State Management:** Check for UI state conflicts, modal interference, or element interaction issues.
-5. **Sequential Operations:** Ensure UI operations don't interfere with each other when called in sequence.
+4. **Import Validation:** Ensure all remaining imports are necessary and no missing imports cause reference errors.
+5. **Unused Import Cleanup:** Verify that unused imports were properly removed without breaking functionality.
+6. **UI State Management:** Check for UI state conflicts, modal interference, or element interaction issues.
+7. **Sequential Operations:** Ensure UI operations don't interfere with each other when called in sequence.
+
+**IMPORT ERROR DEBUGGING:**
+- Check for missing imports that cause undefined reference errors
+- Verify that import removal didn't break existing functionality
+- Ensure all imported modules are actually available in the project
+- Confirm that import syntax is correct for the target language
 
 **KEY: Variables not defined within function scope MUST be passed as parameters.**
 **UI KEY: Helper functions that perform UI operations must be self-contained and not leave modals/dialogs open.**
+**IMPORT KEY: All imports must be either used in the code or properly removed.**
 `;
 }
 export function getModularizationPromptForUI(filePath, language) {
@@ -93,8 +125,38 @@ STEPS:
 - Array processing with null handling or special indexing
 - Button clicks with complex selector chains that are unique to specific contexts
 
+**IMPORT CLEANUP AFTER MODULARIZATION:**
+After applying modularization principles:
+1. **Analyze Remaining Imports**: Review all import statements at the top of the file
+2. **Identify Unused Imports**: Check which imported modules, functions, or classes are no longer referenced in the modularized code
+3. **Remove Unused Imports**: Delete any import statements that are not used in the final modularized code
+4. **Preserve Required Imports**: Keep all imports that are actually used by the modularized functions
+5. **Maintain Import Order**: Preserve the original ordering of remaining imports for consistency
+
+**UI-SPECIFIC IMPORT CONSIDERATIONS:**
+- Preserve all Playwright/testing framework imports (page, expect, test, etc.)
+- Keep UI-specific utility imports even if usage appears reduced
+- Maintain browser-specific imports that may be needed for UI operations
+- Do not remove imports for UI components or page object models
+- Preserve imports for locators, selectors, and UI interaction utilities
+
+**IMPORT REMOVAL RULES FOR UI TESTS:**
+- Only remove imports that are completely unused after modularization
+- Keep imports used by any function, even if usage decreased
+- Preserve imports for types used in function parameters (inline types)
+- Do not remove imports for testing frameworks or utilities
+- Maintain proper import syntax and formatting
+- Be extra cautious with UI framework imports - they may be used in ways not immediately obvious
+
+**LANGUAGE-SPECIFIC UI IMPORT HANDLING:**
+- **Python**: Remove unused import and from...import statements, but keep pytest, playwright imports
+- **JavaScript/TypeScript**: Remove unused import and require() statements, but preserve @playwright/test imports
+- **Java**: Remove unused import statements, but keep testing framework imports
+- **All Languages**: Always preserve UI testing framework and browser automation imports
+
 **CRITICAL CONSTRAINTS:**
 - NO interfaces, classes, types, or data structures
+- DO NOT CREATE/UPDATE package.json or requirements.txt or pom.xml or build.gradle file
 - NO changes to the core UI interaction sequence
 - NO extraction of partial workflows that depend on external state
 - NO generalization of complex logic patterns into loops or helper functions
@@ -108,6 +170,7 @@ STEPS:
 - NAVIGATION STEPS MUST REMAIN IN THE MAIN TEST FUNCTION TO MAINTAIN PROPER PAGE STATE
 - COMPLEX LOGIC PATTERNS MUST REMAIN IN THE MAIN TEST FUNCTION TO MAINTAIN EXACT BEHAVIOR
 - SPECIFIC SELECTORS MUST BE PRESERVED TO ENSURE CORRECT ELEMENT TARGETING
+- REMOVE unused imports after modularization (following UI-specific import rules)
 
 **BEFORE SUBMITTING: Double-check that every navigation step, complex operation, and specific selector from the original test appears in the same position with the same logic in the main test function.**
 
@@ -153,8 +216,11 @@ export function getFixErrorsPromptForUI() {
 8. **Unique Workflow Preservation**: If the original test has unique steps for similar operations, ensure these are preserved and not generalized incorrectly.
 9. **Complete Workflow Validation**: Ensure that extracted helper functions contain COMPLETE workflows, not partial steps that depend on external state.
 10. **Page State Management**: Verify that helper functions don't assume specific page states - the main test should handle navigation between different pages/states.
-11. **Validate Correctness**: Ensure code is free of reference errors, undefined variables, runtime issues.
-12. **Import Paths**: Ensure import paths are correct and there are no circular imports.
+11. **Import Validation**: Ensure all remaining imports are necessary and no missing imports cause reference errors.
+12. **Unused Import Cleanup**: Verify that unused imports were properly removed without breaking UI test functionality.
+13. **UI Framework Import Preservation**: Ensure that critical UI testing imports (Playwright, testing frameworks) were not accidentally removed.
+14. **Validate Correctness**: Ensure code is free of reference errors, undefined variables, runtime issues.
+15. **Import Paths**: Ensure import paths are correct and there are no circular imports.
 
 **TIMEOUT DEBUGGING CHECKLIST:**
 - Are all navigation steps (navbar clicks, page.goto) in the main test function?
@@ -175,6 +241,13 @@ export function getFixErrorsPromptForUI() {
 - Do button clicks use the same selector specificity as the original?
 - Are there any ambiguous selectors that could match multiple elements?
 
+**IMPORT ERROR DEBUGGING CHECKLIST:**
+- Are there any undefined reference errors due to missing imports?
+- Were any critical UI framework imports (page, expect, test) accidentally removed?
+- Do all remaining imports correspond to actually used functionality?
+- Are import paths correct and accessible in the project structure?
+- Were any imports removed that are used in non-obvious ways (like in string templates)?
+
 **SPECIFIC FIX FOR COMMON ERRORS:**
 If you see timeout on button clicks or element interactions:
 - Check if navigation steps were moved into helper functions and move them back to main test
@@ -186,10 +259,17 @@ If you see incorrect calculations or missing operations:
 - Verify all operations from original test are present in modularized version
 - Look for null value handling differences
 
+If you see import or reference errors:
+- Check if critical UI framework imports were accidentally removed
+- Verify all remaining imports are necessary and properly used
+- Restore any imports needed for UI interactions, even if usage seems minimal
+- Confirm import paths match the project structure
+
 **KEY: Every UI interaction from the original test must be present in the modularized version.**
 **CRITICAL: Helper functions should only contain COMPLETE, self-contained workflows.**
 **NAVIGATION KEY: Navigation steps between operations must remain in the main test flow to maintain proper page state.**
 **CALCULATION KEY: Unique logic patterns should not be generalized if they produce different results.**
 **SELECTOR KEY: Specific selectors must be preserved to ensure correct element targeting.**
+**IMPORT KEY: All necessary imports must be preserved, especially UI framework imports.**
 `;
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@skyramp/mcp",
-  "version": "0.0.25",
+  "version": "0.0.27",
   "main": "build/index.js",
   "type": "module",
   "bin": {
@@ -42,7 +42,7 @@
   },
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.11.4",
-    "@skyramp/skyramp": "^1.2.18",
+    "@skyramp/skyramp": "^1.2.20",
     "dockerode": "^4.0.6",
     "zod": "^3.25.3"
   },