@ompo-design/mcp-server 0.1.4 → 0.1.5

package/dist/apply-plan.js

@@ -169,23 +169,32 @@ function buildDomStructurePlan(operation) {
                     selector: operation.selector
                 }
             };
-        case 'dom.move':
+        case 'dom.move': {
+            const reordered = operation.fromParentSelector === operation.toParentSelector;
             return {
                 kind: 'dom.move',
-                summary: 'Move an existing element to a new parent',
+                summary: reordered
+                    ? `Reorder element within parent "${operation.toParentSelector}"`
+                    : `Move element to a new parent "${operation.toParentSelector}"`,
                 steps: [
-                    `Locate element "${operation.selector}" in source using selector and surrounding structure.`,
-                    `Move it from "${operation.fromParentSelector}" (index ${operation.fromIndex}) to "${operation.toParentSelector}" at index ${operation.index}.`,
-                    'Preserve the element’s content and non-Ompo styling.'
+                    `Locate element "${operation.selector}" in source using selector, tag, id, class, or nearby text.`,
+                    reordered
+                        ? `Reorder it inside "${operation.toParentSelector}" from child index ${operation.fromIndex} to index ${operation.index}.`
+                        : `Move it from "${operation.fromParentSelector}" (index ${operation.fromIndex}) to "${operation.toParentSelector}" at index ${operation.index}.`,
+                    'Update JSX/HTML/component structure in source — this is a markup change, not a CSS tweak.',
+                    'Preserve the element’s content and non-Ompo styling.',
+                    'If the project uses mapped lists or arrays, update item order in data when that drives rendering.'
                 ],
                 payload: {
                     selector: operation.selector,
                     fromParentSelector: operation.fromParentSelector,
                     fromIndex: operation.fromIndex,
                     toParentSelector: operation.toParentSelector,
-                    insertIndex: operation.index
+                    insertIndex: operation.index,
+                    reordered
                 }
             };
+        }
         case 'dom.delete':
             return {
                 kind: 'dom.delete',
@@ -278,6 +287,7 @@ export function buildApplyPlan(bundle) {
             'Read ompoGlossary.fill and ompoGlossary.gap before applying layout changes — Ompo terms are not literal CSS properties.',
             'When widthMode or heightMode is "fill", apply the grouped flex properties together (flexGrow, flexBasis, alignSelf, removed width/height) — do not set a fixed px width/height on the filled axis.',
             'Gap belongs on the flex/grid parent. Fill belongs on the child inside a flex parent.',
+            'DOM moves are in domStructurePlans and domChanges — reorder or reparent elements in source markup/components, not just CSS.',
             'For dom.flexWrap: create a new wrapper, move matched children, then apply wrapperStyles.',
             'Use child anchors (tag, id, class, textSnippet) to find elements in source when selectors are unstable.',
             'Prefer the smallest possible diff for each file.'

package/dist/index.js

@@ -8,7 +8,7 @@ import { editsStoreReady, listEdits, readEditBundle, recordEditApplied, recordEd
 import { getOmpoEditsStorePath } from './edits-path.js';
 const server = new McpServer({
     name: 'ompo-mcp-server',
-    version: '0.1.4'
+    version: '0.1.5'
 });
 function requireEditsStore() {
     const storePath = getOmpoEditsStorePath();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ompo-design/mcp-server",
-  "version": "0.1.4",
+  "version": "0.1.5",
   "description": "MCP server for applying Ompo visual edits to a codebase",
   "type": "module",
   "license": "MIT",