otro

CLAUDE.md

@@ -115,30 +115,6 @@ Do NOT modify web-base files — they are shared across all projects.
 10. `enlace` (link) fields already include slashes — **NEVER modify an existing enlace** unless explicitly asked
 11. **NEVER modify the `controlador` field** of existing records — it defines whether a page is Builder or Standard
 
-## Project Styles
-
-When creating new modules, you need to match the visual style of the existing project. To avoid re-exploring modules every time:
-
-1. **If `docs/project-styles.md` exists** → read it. It contains the project's color palette, typography, spacing, and design patterns. Use it directly.
-2. **If it does NOT exist and there are 3+ modules** → explore the existing modules to understand the style, then **generate `docs/project-styles.md`** with a summary for future use.
-3. **If it does NOT exist and there are few modules** → create the module based on the user's description without exploring. The style will be defined as modules are created.
-
-**When exploring modules for style reference:**
-- Only look at modules that have a `builder.json` file (these are builder modules)
-- Skip modules whose directory name starts with `custom-` (these are general sections, not visual modules)
-- Read `index-base.tpl` and `style.css` of 3-4 representative modules
-- Summarize: color palette, typography, spacing, Tailwind patterns, common CSS classes, design conventions
-
-**When generating `docs/project-styles.md`**, include:
-- 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.)
-
-**Update `docs/project-styles.md`** after creating a module if the project has grown significantly since the last update (e.g. 5+ new modules).
-
 ## MCP Tools
 
 This project has MCP tools for managing modules, records, media, and more. **Before starting any task, consult the tools reference for the correct workflow.**
@@ -146,9 +122,9 @@ This project has MCP tools for managing modules, records, media, and more. **Bef
 See [docs/mcp-tools-reference.md](docs/mcp-tools-reference.md) for the complete list of available tools and step-by-step workflows.
 
 Key workflows:
-- **Create module**: `create_module` → `add_module_to_record` → `set_module_config_vars` → images
+- **Create module**: Read [docs/module-creation-guide.md](docs/module-creation-guide.md) first → `create_module` → `add_module_to_record` (returns sectionId) → `set_module_config_vars` (returns uploadFields) → images via uploadFields
 - **Edit module**: read vars → edit `index-base.tpl` → `compile_module`
-- **Add images**: `get_module_config_vars` → `upload_record_image` (fieldName from builder.json relations)
+- **Add images**: use `uploadFields` from `set_module_config_vars` response → `upload_record_image`
 - **Generate images**: `generate_image` → `upload_record_image` with returned URL
 
 ## Documentation
@@ -163,4 +139,5 @@ Key workflows:
 - [docs/vue-builder-rules.md](docs/vue-builder-rules.md) — CMS-VUE rules (tabs, colorpicker, components)
 - [docs/vue-builder-examples.md](docs/vue-builder-examples.md) — Vue builder examples (Banner Slideshow, etc.)
 - [docs/pages-and-records.md](docs/pages-and-records.md) — Page types (Builder vs Standard), sections, visibility, critical rules
+- [docs/module-creation-guide.md](docs/module-creation-guide.md) — Module creation workflow, style reference, field types
 - [docs/mcp-tools-reference.md](docs/mcp-tools-reference.md) — MCP tools reference, available tools, workflows