fdsfds

docs/mcp-tools-reference.md

@@ -28,6 +28,8 @@
 | `delete_record_upload` | Media | Borrar upload |
 | `reorder_record_uploads` | Media | Reordenar imágenes de un campo |
 | `refresh_acai_token` | Auth | Renovar token JWT expirado |
+| `navigate_browser` | Navegación | Navegar el browser del frontend a una URL |
+| `save_project_styles` | Proyecto | Guardar resumen de estilos en docs/project-styles.md |
 | `orchestrate_task` | Orquestador | Guía paso a paso para tareas complejas |
 | `rollback_git` | Git | Recuperar cambios de git remoto |
 

docs/module-creation-guide.md

@@ -15,16 +15,16 @@ When creating new modules, you MUST match the visual style of the existing proje
 
 ### Step 3: Explore and GENERATE the style guide (MANDATORY)
 - Read `index-base.tpl` and `style.css` of 3-4 representative modules (only those with `builder.json`, skip `custom-*`)
-- **You MUST then create the file `docs/project-styles.md`** with:
+- **You MUST then call `save_project_styles`** with a markdown summary including:
   - Primary/secondary/accent colors (hex values)
   - Font families and sizes used
   - Spacing scale (padding/margin patterns)
   - Common Tailwind classes and custom CSS patterns
   - Button styles, card styles, section layouts
   - Any recurring design patterns (gradients, shadows, borders, etc.)
-- This file will be used by future module creation tasks to avoid re-exploring every time.
+- This saves `docs/project-styles.md` which will be read by future module creation tasks — no re-exploration needed.
 
-**After creating a module:** if `docs/project-styles.md` does not exist yet and there are now 3+ modules, generate it.
+**After creating a module:** if `docs/project-styles.md` does not exist yet and there are now 3+ modules, call `save_project_styles`.
 
 ## Module Structure