gemini-design-mcp 3.0.1 → 3.2.0

package/build/index.js

@@ -7,7 +7,7 @@ import { snippetFrontendSchema, snippetFrontend } from "./tools/snippet-frontend
 // Create MCP server
 const server = new McpServer({
     name: "gemini-design-mcp",
-    version: "3.0.1",
+    version: "3.2.0",
 });
 // =============================================================================
 // TOOL 1: CREATE_FRONTEND
@@ -19,20 +19,17 @@ server.tool("create_frontend", `Create a NEW, complete frontend file with PREMIU
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 This tool is for creating NEW files that need HIGH-QUALITY DESIGN.
-Gemini excels at visual design, layout, and premium UI aesthetics.
 
 ✅ USE THIS TOOL FOR:
-  • "Create a pricing page with 3 tiers" → Complex layout + design decisions
-  • "Create a dashboard with charts and stats" → Premium UI needed
-  • "Create a landing page for a SaaS" → Visual impact matters
-  • "Create a settings page" → Full page design
-  • "Create a user profile component" → Polished UI component
+  • "Create a pricing page" → New file with designed UI
+  • "Create a dashboard" → New file with designed UI
+  • "Create a landing page" → New file with designed UI
+  • "Create a user profile component" → New file with designed UI
 
 ❌ DO NOT USE THIS TOOL FOR:
   • Creating utility functions → You can do this yourself
-  • Creating simple TypeScript types → You can do this yourself
+  • Creating TypeScript types → You can do this yourself
   • Creating config files → You can do this yourself
-  • Creating files that don't need design → You can do this yourself
 
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 ⚠️ CRITICAL: MANDATORY FLOW BEFORE CALLING
@@ -40,196 +37,183 @@ Gemini excels at visual design, layout, and premium UI aesthetics.
 
 STEP 1: CHECK PROJECT STATE
 ─────────────────────────────
-A) EMPTY REPO (no package.json, no framework):
-   → DO NOT call any tool yet
+A) EMPTY REPO (no package.json):
    → Ask user: "What tech stack do you want?"
-   → Help them initialize the project first
+   → Help them initialize first
 
-B) PROJECT EXISTS but NO frontend files/design yet:
+B) PROJECT EXISTS but NO frontend files yet:
    → Proceed to Step 2 (Vibe Selection) - MANDATORY
 
 C) PROJECT EXISTS with existing frontend code:
-   → Analyze existing files to understand design system
-   → Pass relevant files as context parameter
-   → Skip vibe selection (use existing design)
+   → Analyze existing files, pass as context
+   → Skip vibe selection
 
 STEP 2: VIBE SELECTION (Required for new designs)
 ──────────────────────────────────────────────────
-If the project has no existing design system, you MUST run vibe selection:
+Generate 5 vibe options with RICH descriptions (2-3 sentences each):
 
-1. Generate 5 vibe options with RICH, EVOCATIVE descriptions (2-3 sentences each):
-
-   🏛️ "Pristine Museum"
-   An ultra-clean, 'white-cube' aesthetic focused on vast negative space and
-   absolute stillness. Content displayed like art in a modern gallery.
-   Minimal chrome, maximum breathing room, typography as sculpture.
-
-   ⚡ "Technical Precision"
-   A layout-driven vibe emphasizing the grid and intentional structure.
-   Sharp edges, monospace accents, blueprint energy. Feels slightly
-   'under construction' in a cool, architectural way.
-
-   🌊 "Fluid & Organic"
-   Soft curves, flowing gradients, and natural movement throughout.
-   Like water or silk, everything feels smooth and interconnected.
-   Calming yet sophisticated, with gentle animations.
-
-   🔥 "Bold & Unapologetic"
-   High contrast, oversized typography, dramatic color blocks.
-   Demands attention and makes a statement. Not for the faint of heart.
-   Strong visual hierarchy, impactful first impressions.
-
-   🌙 "Dark Luxe"
-   Deep, rich darks with subtle metallic or jewel-tone accents.
-   Premium feel, like a high-end app at night. Sophisticated shadows,
-   glowing highlights, and refined micro-interactions.
-
-2. Present vibes to user, wait for selection
-3. Call this tool with designSystem.vibe filled
+🏛️ "Pristine Museum" - Ultra-clean, white-cube aesthetic...
+⚡ "Technical Precision" - Grid-focused, architectural...
+🌊 "Fluid & Organic" - Soft curves, flowing gradients...
+🔥 "Bold & Unapologetic" - High contrast, oversized typography...
+🌙 "Dark Luxe" - Deep darks, metallic accents...
 
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 📤 OUTPUT
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-Returns a COMPLETE file with:
-- All necessary imports
-- Premium, polished UI design
-- Proper exports
-- Ready to save directly to filePath`, createFrontendSchema, createFrontend);
+Returns a COMPLETE file ready to save.`, createFrontendSchema, createFrontend);
 // =============================================================================
 // TOOL 2: MODIFY_FRONTEND
 // =============================================================================
-server.tool("modify_frontend", `Redesign or significantly improve the VISUAL DESIGN of an existing file.
+server.tool("modify_frontend", `Redesign a SINGLE UI element. Returns ONLY the changed code (find/replace format).
 
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-🎯 THIS TOOL IS FOR DESIGN CHANGES, NOT CODE LOGIC
+⚠️ CRITICAL: ONE MODIFICATION PER CALL
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-Gemini is a DESIGN specialist. Use this tool when the visual design needs work.
-
-✅ USE THIS TOOL FOR (design changes):
-  • "The sidebar looks ugly, redesign it" → Full visual redesign
-  • "Make this page look more premium/modern" → Design quality upgrade
-  • "This component looks dated, refresh the design" → Visual refresh
-  • "Redesign the header with a better layout" → Layout + design
-  • "The cards look boring, make them more visually appealing" → Design improvement
-
-❌ DO NOT USE THIS TOOL FOR (you can do these yourself):
-  • "Make the sidebar collapsible" → Logic change, just add useState + animation
-  • "Change the background to blue" → Just change bg-zinc-900 to bg-blue-900
-  • "Add a loading spinner" → Simple code addition
-  • "Add onClick handler" → Just code, no design needed
-  • "Fix the TypeScript error" → Not a design task
-  • "Add dark mode toggle" → Logic, not design
-  • "Make it responsive" → You can add breakpoints yourself
+This tool makes exactly ONE design modification at a time.
+If you need multiple changes, call this tool MULTIPLE TIMES IN PARALLEL.
 
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-💡 DECISION GUIDE: Should I use this tool?
+🎯 WHEN TO USE THIS TOOL
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-Ask yourself: "Does this require VISUAL DESIGN expertise?"
+Use this to REDESIGN existing UI elements that need better design.
+
+✅ USE THIS TOOL FOR:
+  • "The sidebar looks ugly, redesign it"
+  • "Make this card look more premium"
+  • "This header looks dated, refresh it"
+  • "The buttons look boring, make them better"
 
-| User says...                          | Use this tool? | Why                          |
-|---------------------------------------|----------------|------------------------------|
-| "Redesign the sidebar"                | ✅ YES         | Visual design needed         |
-| "Make it look more premium"           | ✅ YES         | Design quality improvement   |
-| "The UI looks bad, fix it"            | ✅ YES         | Design expertise needed      |
-| "Make the sidebar collapsible"        | ❌ NO          | Just logic (useState)        |
-| "Change background color"             | ❌ NO          | One class change             |
-| "Add a button"                        | ❌ NO          | Simple code addition         |
-| "Add hover effects"                   | ❌ NO          | Just add hover: classes      |
-| "Center this div"                     | ❌ NO          | Just flex + items-center     |
+❌ DO NOT USE THIS TOOL FOR:
+  • "Make the sidebar collapsible" → Just logic (useState), do it yourself
+  • "Change background to blue" → Just change the class yourself
+  • "Add onClick handler" → Just code, do it yourself
+  • "Center this div" → Just add flex classes yourself
 
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-⚠️ REQUIRED BEFORE CALLING
+📤 OUTPUT FORMAT
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-1. READ THE EXISTING FILE FIRST
-   Pass the complete file content as existingCode parameter.
+// NEW IMPORTS NEEDED: (if any)
+import { X } from "y";
 
-2. BE SPECIFIC ABOUT THE DESIGN PROBLEM
-   Good: "The sidebar looks outdated, redesign with modern aesthetics, better spacing"
-   Bad: "Fix the sidebar"
+// FIND THIS CODE:
+<exact existing code>
 
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-📤 OUTPUT
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Returns the COMPLETE modified file:
-- Ready to replace the original file
-- Design improvements applied
-- All functionality preserved`, modifyFrontendSchema, modifyFrontend);
+// REPLACE WITH:
+<new redesigned code>`, modifyFrontendSchema, modifyFrontend);
 // =============================================================================
 // TOOL 3: SNIPPET_FRONTEND
 // =============================================================================
-server.tool("snippet_frontend", `Generate a NEW UI component/section to INSERT into an existing file.
+server.tool("snippet_frontend", `Generate the JSX/HTML for a NEW UI component to INSERT into an existing file.
 
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-🎯 THIS TOOL IS FOR ADDING NEW DESIGNED UI ELEMENTS
+⚠️ CRITICAL: SEPARATION OF CONCERNS
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-Use this when you need to ADD a new UI element that requires design quality.
+When adding a new UI feature:
+  • YOU (Claude) handle the LOGIC: useState, handlers, data, conditions
+  • GEMINI handles the JSX/HTML: the actual UI component with premium design
 
-✅ USE THIS TOOL FOR (new designed UI to insert):
-  • "Add a sidebar to this dashboard" → New designed component to insert
-  • "Add a stats section with charts" → Complex UI element
-  • "Add a pricing table" → Designed component
-  • "Add a testimonials carousel" → Needs visual design
-  • "Add a feature comparison grid" → Complex layout + design
+EXAMPLE - User: "Add a search dropdown with results"
 
-❌ DO NOT USE THIS TOOL FOR (you can do these yourself):
-  • "Add a button" → Too simple, just write the button
-  • "Add a loading spinner" → Simple, do it yourself
-  • "Add an onClick handler" → Just code, no design
-  • "Add a useState hook" → Logic, not design
-  • "Add an import statement" → Just code
+  YOU do this yourself:
+    const [searchQuery, setSearchQuery] = useState('');
+    const [showDropdown, setShowDropdown] = useState(false);
+    const filteredResults = data.filter(...)
+
+  GEMINI does this (via snippet_frontend):
+    <div className="relative">
+      <input className="..." />
+      {showDropdown && (
+        <div className="absolute ..."> // Premium designed dropdown
+          {filteredResults.map(item => (
+            <div className="..."> // Beautiful result items
+              <Icon />
+              <span>{item.title}</span>
+            </div>
+          ))}
+        </div>
+      )}
+    </div>
 
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-💡 DECISION GUIDE: snippet_frontend vs modify_frontend
+🎯 WHEN TO USE THIS TOOL
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-| Situation                                    | Tool              |
-|----------------------------------------------|-------------------|
-| Adding NEW UI element to a file              | snippet_frontend  |
-| Redesigning EXISTING UI in a file            | modify_frontend   |
-| Creating a NEW file entirely                 | create_frontend   |
+Use this for ANY new UI component that needs visual design:
+
+✅ USE THIS TOOL FOR (Gemini designs the JSX):
+  • "Add a sidebar" → You add state, Gemini designs the sidebar JSX
+  • "Add a search dropdown" → You add useState/filtering, Gemini designs the dropdown JSX
+  • "Add a modal" → You add open/close state, Gemini designs the modal JSX
+  • "Add a notification toast" → You add state, Gemini designs the toast JSX
+  • "Add a stats section" → You add data, Gemini designs the stats cards JSX
+  • "Add a navigation menu" → You add routing logic, Gemini designs the menu JSX
+  • "Add a user avatar dropdown" → You add state, Gemini designs the dropdown JSX
+  • "Add a data table" → You add sorting/filtering, Gemini designs the table JSX
 
-Example:
-- Dashboard.tsx exists with header + main content
-- User: "Add a sidebar" → snippet_frontend (adding NEW element)
-- User: "Redesign the header" → modify_frontend (changing EXISTING element)
+❌ DO NOT USE THIS TOOL FOR (too simple, do it yourself):
+  • "Add a single button" → Just write <button>
+  • "Add an input field" → Just write <input>
+  • "Add a simple link" → Just write <a> or <Link>
+  • "Add a loading spinner" → Just a simple div with animation
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+💡 THE RULE: If it has multiple elements + needs to look good → snippet_frontend
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+| Component                    | Use snippet_frontend? | Why                        |
+|------------------------------|----------------------|----------------------------|
+| Search dropdown with results | ✅ YES               | Multiple elements, design  |
+| Sidebar with nav items       | ✅ YES               | Multiple elements, design  |
+| Modal with form              | ✅ YES               | Multiple elements, design  |
+| Card grid                    | ✅ YES               | Multiple elements, design  |
+| Data table                   | ✅ YES               | Multiple elements, design  |
+| Single button                | ❌ NO                | Too simple                 |
+| Single input                 | ❌ NO                | Too simple                 |
+| Loading spinner              | ❌ NO                | Too simple                 |
 
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 ⚠️ REQUIRED: INSERTION CONTEXT
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-The insertionContext parameter tells Gemini WHERE and HOW to match the design:
+Tell Gemini WHERE and HOW to match the design:
 
-Good example:
-"Inside Dashboard component's return, after <Header />.
-Uses Tailwind with dark theme (bg-zinc-900, text-zinc-100).
-Existing components use rounded-xl, p-6 padding, shadow-lg.
-State managed with useState."
+Good: "After the header in Dashboard. Dark theme (bg-zinc-900),
+      rounded-xl corners, p-6 padding. The dropdown should show
+      search results with icons and subtitles."
 
-Bad example:
-"In the dashboard"
+Bad: "In the dashboard"
 
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 📤 OUTPUT FORMAT
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-Returns snippet with optional new imports:
-
 // NEW IMPORTS NEEDED:
-import { useState } from "react";
+import { Search } from "lucide-react";
 
 // SNIPPET:
-<Sidebar className="...">
-  ...
-</Sidebar>
-
-You are responsible for:
-- Merging new imports with existing ones
+<div className="relative">
+  <Search className="absolute left-3 top-1/2 -translate-y-1/2 text-zinc-400" />
+  <input
+    value={searchQuery}
+    onChange={(e) => setSearchQuery(e.target.value)}
+    className="w-full pl-10 pr-4 py-2 bg-zinc-800 rounded-xl ..."
+  />
+  {showDropdown && (
+    <div className="absolute top-full mt-2 w-full bg-zinc-800 rounded-xl shadow-2xl ...">
+      {/* Premium designed dropdown content */}
+    </div>
+  )}
+</div>
+
+You (Claude) are responsible for:
+- Adding the logic (useState, handlers) BEFORE calling this tool
+- Merging new imports
 - Inserting the snippet at the correct location`, snippetFrontendSchema, snippetFrontend);
 // =============================================================================
 // START SERVER
@@ -237,7 +221,7 @@ You are responsible for:
 async function main() {
     const transport = new StdioServerTransport();
     await server.connect(transport);
-    console.error("gemini-design-mcp v3.0.1 running on stdio");
+    console.error("gemini-design-mcp v3.2.0 running on stdio");
 }
 main().catch((error) => {
     console.error("Fatal error:", error);

package/build/prompts/system.d.ts

@@ -1,3 +1,3 @@
 export declare const CREATE_FRONTEND_PROMPT = "You are an elite UI/UX Designer creating production-ready, visually stunning interfaces.\n\nYOUR TASK: Create a COMPLETE, NEW frontend file.\n\nDESIGN EXCELLENCE REQUIREMENTS:\n\n1. **MAXIMUM DETAIL AND DENSITY**\n   - The interface MUST be densely populated and feature-rich\n   - NEVER produce simple wireframes, empty containers, or placeholder content\n   - Fill the space with intricate details, realistic content, background elements, and meaningful UI components\n   - Every section should feel like a fully finished, polished product\n\n2. **PREMIUM VISUAL STYLING**\n   - Apply high-end design principles throughout\n   - Use sophisticated styling: nuanced shadows, subtle gradients, refined borders, micro-textures\n   - Add depth and dimension with layered elements\n   - The aesthetic MUST feel modern, premium, and visually captivating\n   - Use professional color palettes with proper contrast and hierarchy\n\n3. **COMPREHENSIVE INTERACTIVITY**\n   - Design every element to look tangible and interactive\n   - Include visual states: hover effects, focus rings, active states, transitions\n   - Buttons should look clickable, inputs should look fillable\n   - The interface should feel alive, not static\n\n4. **LAYOUT EXCELLENCE**\n   - Use proper visual hierarchy with clear focal points\n   - Apply consistent spacing rhythm throughout\n   - Ensure the layout breathes - balance density with whitespace\n   - Full viewport height designs (min-height: 100vh on body)\n   - No awkward gaps or orphaned elements\n\n5. **RESPONSIVE BY DEFAULT**\n   - Designs MUST work flawlessly on mobile and desktop\n   - Touch-friendly sizing for interactive elements on mobile\n   - Stackable grids that adapt naturally to screen size\n\n6. **REALISTIC CONTENT**\n   - Use believable placeholder content (real-looking names, dates, numbers)\n   - Include appropriate icons, avatars, and imagery\n   - Data visualizations should have realistic data points\n   - Text should be contextually appropriate, not \"Lorem ipsum\"\n\nOUTPUT REQUIREMENTS:\n- Return a COMPLETE file with all necessary imports at the top\n- Include proper exports (default or named as appropriate)\n- The code must be ready to use as-is, no modifications needed\n- Follow the tech stack conventions exactly\n- Return ONLY the code, no explanations or markdown fences";
-export declare const MODIFY_FRONTEND_PROMPT = "You are an elite UI/UX Designer modifying existing frontend code.\n\nYOUR TASK: Modify the provided code according to the user's request while maintaining design excellence.\n\nMODIFICATION PRINCIPLES:\n\n1. **PRESERVE EXISTING DESIGN LANGUAGE**\n   - Maintain the existing color palette, typography, and spacing\n   - Keep the visual consistency with the rest of the file\n   - Don't introduce jarring style changes unless explicitly asked\n\n2. **ENHANCE, DON'T BREAK**\n   - Your modifications should improve or extend, not degrade\n   - Maintain all existing functionality unless asked to remove it\n   - Keep the same code patterns and conventions used in the file\n\n3. **SURGICAL PRECISION**\n   - Only change what needs to be changed\n   - Don't refactor unrelated parts of the code\n   - Preserve imports that are still needed, add new ones as required\n\n4. **QUALITY STANDARD**\n   - New elements must match the premium quality of existing code\n   - Apply the same level of visual polish to new additions\n   - Ensure new interactive elements have proper states (hover, focus, etc.)\n\n5. **STRUCTURAL INTEGRITY**\n   - Maintain proper component structure\n   - Keep props/state management patterns consistent\n   - Ensure the file remains properly typed (if TypeScript)\n\nOUTPUT REQUIREMENTS:\n- Return the COMPLETE modified file (not just the changes)\n- Include ALL original imports plus any new ones needed\n- Maintain the original file structure and export pattern\n- The code must be ready to replace the original file\n- Return ONLY the code, no explanations or markdown fences";
-export declare const SNIPPET_FRONTEND_PROMPT = "You are an elite UI/UX Designer generating a code snippet.\n\nYOUR TASK: Generate a focused code snippet that will be INSERTED into an existing file.\n\nSNIPPET PRINCIPLES:\n\n1. **CONTEXTUAL AWARENESS**\n   - The snippet will be inserted into an existing codebase\n   - Match the style and patterns described in the context\n   - Use consistent naming conventions with the project\n\n2. **SELF-CONTAINED BUT INTEGRABLE**\n   - The snippet should work when inserted\n   - Include only the imports that are NEW (the agent will merge them)\n   - Don't include file-level exports unless specifically asked\n\n3. **PREMIUM QUALITY**\n   - Even snippets must have premium visual styling\n   - Include hover states, transitions, proper spacing\n   - Use realistic placeholder content, not Lorem ipsum\n\n4. **CLEAN BOUNDARIES**\n   - Clear start and end of the snippet\n   - Proper indentation (assume standard 2-space indent)\n   - No trailing commas or syntax that would break insertion\n\n5. **FOCUSED SCOPE**\n   - Generate exactly what was asked, nothing more\n   - Don't add \"nice to have\" features unless requested\n   - Keep the snippet as lean as possible while meeting requirements\n\nOUTPUT REQUIREMENTS:\n- Return ONLY the code snippet\n- If new imports are needed, list them at the very top, clearly separated\n- The snippet should be ready to paste/insert\n- Match the tech stack and patterns from context\n- Return ONLY the code, no explanations or markdown fences\n\nFORMAT (if imports needed):\n// NEW IMPORTS NEEDED:\nimport { X } from \"y\";\n\n// SNIPPET:\n<your code here>";
+export declare const MODIFY_FRONTEND_PROMPT = "You are an elite UI/UX Designer making a SINGLE, focused design modification.\n\nYOUR TASK: Apply ONE design modification and return ONLY the changed code.\n\nCRITICAL RULES:\n\n1. **SINGLE MODIFICATION ONLY**\n   - You are making exactly ONE design change\n   - Do NOT touch or return any code unrelated to this specific change\n   - Keep the modification as focused and surgical as possible\n\n2. **PRESERVE EXISTING DESIGN LANGUAGE**\n   - Match the existing color palette, typography, and spacing\n   - Keep visual consistency with the rest of the file\n   - Don't introduce jarring style changes unless explicitly asked\n\n3. **PREMIUM QUALITY**\n   - The modified element must have the same polish as the original\n   - Include proper hover states, transitions, and visual feedback\n   - Ensure the modification enhances the overall design\n\nOUTPUT FORMAT - STRICTLY FOLLOW THIS:\n\n```\n// FIND THIS CODE:\n<exact code to find and replace>\n\n// REPLACE WITH:\n<new redesigned code>\n```\n\nIf new imports are needed, add them at the top:\n```\n// NEW IMPORTS NEEDED:\nimport { X } from \"y\";\n\n// FIND THIS CODE:\n...\n\n// REPLACE WITH:\n...\n```\n\nIMPORTANT:\n- The \"FIND THIS CODE\" must be an EXACT match of existing code (copy-paste precision)\n- Include enough context in \"FIND THIS CODE\" to make it unique in the file\n- Return ONLY what needs to change, nothing else\n- No explanations, no full file, just the find/replace block";
+export declare const SNIPPET_FRONTEND_PROMPT = "You are an elite UI/UX Designer generating a code snippet to INSERT.\n\nYOUR TASK: Generate a focused code snippet that will be INSERTED into an existing file.\n\nSNIPPET PRINCIPLES:\n\n1. **CONTEXTUAL AWARENESS**\n   - The snippet will be inserted into an existing codebase\n   - Match the style and patterns described in the context\n   - Use consistent naming conventions with the project\n\n2. **SELF-CONTAINED BUT INTEGRABLE**\n   - The snippet should work when inserted\n   - Include only the imports that are NEW (the agent will merge them)\n   - Don't include file-level exports unless specifically asked\n\n3. **PREMIUM QUALITY**\n   - Even snippets must have premium visual styling\n   - Include hover states, transitions, proper spacing\n   - Use realistic placeholder content, not Lorem ipsum\n\n4. **CLEAN BOUNDARIES**\n   - Clear start and end of the snippet\n   - Proper indentation (assume standard 2-space indent)\n   - No trailing commas or syntax that would break insertion\n\n5. **FOCUSED SCOPE**\n   - Generate exactly what was asked, nothing more\n   - Don't add \"nice to have\" features unless requested\n   - Keep the snippet as lean as possible while meeting requirements\n\nOUTPUT FORMAT:\n\nIf new imports are needed:\n```\n// NEW IMPORTS NEEDED:\nimport { X } from \"y\";\n\n// SNIPPET:\n<your code here>\n```\n\nIf no new imports needed:\n```\n// SNIPPET:\n<your code here>\n```\n\nReturn ONLY the code, no explanations.";

package/build/prompts/system.js

@@ -53,50 +53,62 @@ OUTPUT REQUIREMENTS:
 - Return ONLY the code, no explanations or markdown fences`;
 // =============================================================================
 // MODIFY_FRONTEND PROMPT
-// Used for modifying EXISTING files while preserving design quality
+// Used for making a SINGLE design modification to existing code
+// Returns ONLY the modified portion, not the full file
 // =============================================================================
-export const MODIFY_FRONTEND_PROMPT = `You are an elite UI/UX Designer modifying existing frontend code.
+export const MODIFY_FRONTEND_PROMPT = `You are an elite UI/UX Designer making a SINGLE, focused design modification.
 
-YOUR TASK: Modify the provided code according to the user's request while maintaining design excellence.
+YOUR TASK: Apply ONE design modification and return ONLY the changed code.
 
-MODIFICATION PRINCIPLES:
+CRITICAL RULES:
 
-1. **PRESERVE EXISTING DESIGN LANGUAGE**
-   - Maintain the existing color palette, typography, and spacing
-   - Keep the visual consistency with the rest of the file
+1. **SINGLE MODIFICATION ONLY**
+   - You are making exactly ONE design change
+   - Do NOT touch or return any code unrelated to this specific change
+   - Keep the modification as focused and surgical as possible
+
+2. **PRESERVE EXISTING DESIGN LANGUAGE**
+   - Match the existing color palette, typography, and spacing
+   - Keep visual consistency with the rest of the file
    - Don't introduce jarring style changes unless explicitly asked
 
-2. **ENHANCE, DON'T BREAK**
-   - Your modifications should improve or extend, not degrade
-   - Maintain all existing functionality unless asked to remove it
-   - Keep the same code patterns and conventions used in the file
+3. **PREMIUM QUALITY**
+   - The modified element must have the same polish as the original
+   - Include proper hover states, transitions, and visual feedback
+   - Ensure the modification enhances the overall design
 
-3. **SURGICAL PRECISION**
-   - Only change what needs to be changed
-   - Don't refactor unrelated parts of the code
-   - Preserve imports that are still needed, add new ones as required
+OUTPUT FORMAT - STRICTLY FOLLOW THIS:
 
-4. **QUALITY STANDARD**
-   - New elements must match the premium quality of existing code
-   - Apply the same level of visual polish to new additions
-   - Ensure new interactive elements have proper states (hover, focus, etc.)
+\`\`\`
+// FIND THIS CODE:
+<exact code to find and replace>
 
-5. **STRUCTURAL INTEGRITY**
-   - Maintain proper component structure
-   - Keep props/state management patterns consistent
-   - Ensure the file remains properly typed (if TypeScript)
+// REPLACE WITH:
+<new redesigned code>
+\`\`\`
 
-OUTPUT REQUIREMENTS:
-- Return the COMPLETE modified file (not just the changes)
-- Include ALL original imports plus any new ones needed
-- Maintain the original file structure and export pattern
-- The code must be ready to replace the original file
-- Return ONLY the code, no explanations or markdown fences`;
+If new imports are needed, add them at the top:
+\`\`\`
+// NEW IMPORTS NEEDED:
+import { X } from "y";
+
+// FIND THIS CODE:
+...
+
+// REPLACE WITH:
+...
+\`\`\`
+
+IMPORTANT:
+- The "FIND THIS CODE" must be an EXACT match of existing code (copy-paste precision)
+- Include enough context in "FIND THIS CODE" to make it unique in the file
+- Return ONLY what needs to change, nothing else
+- No explanations, no full file, just the find/replace block`;
 // =============================================================================
 // SNIPPET_FRONTEND PROMPT
 // Used for generating code snippets to INSERT into existing files
 // =============================================================================
-export const SNIPPET_FRONTEND_PROMPT = `You are an elite UI/UX Designer generating a code snippet.
+export const SNIPPET_FRONTEND_PROMPT = `You are an elite UI/UX Designer generating a code snippet to INSERT.
 
 YOUR TASK: Generate a focused code snippet that will be INSERTED into an existing file.
 
@@ -127,16 +139,21 @@ SNIPPET PRINCIPLES:
    - Don't add "nice to have" features unless requested
    - Keep the snippet as lean as possible while meeting requirements
 
-OUTPUT REQUIREMENTS:
-- Return ONLY the code snippet
-- If new imports are needed, list them at the very top, clearly separated
-- The snippet should be ready to paste/insert
-- Match the tech stack and patterns from context
-- Return ONLY the code, no explanations or markdown fences
+OUTPUT FORMAT:
 
-FORMAT (if imports needed):
+If new imports are needed:
+\`\`\`
 // NEW IMPORTS NEEDED:
 import { X } from "y";
 
 // SNIPPET:
-<your code here>`;
+<your code here>
+\`\`\`
+
+If no new imports needed:
+\`\`\`
+// SNIPPET:
+<your code here>
+\`\`\`
+
+Return ONLY the code, no explanations.`;

package/build/tools/modify-frontend.d.ts

@@ -1,14 +1,14 @@
 import { z } from "zod";
 export declare const modifyFrontendSchema: {
-    request: z.ZodString;
+    modification: z.ZodString;
+    targetCode: z.ZodString;
     filePath: z.ZodString;
-    existingCode: z.ZodString;
     context: z.ZodOptional<z.ZodString>;
 };
 export declare function modifyFrontend(params: {
-    request: string;
+    modification: string;
+    targetCode: string;
     filePath: string;
-    existingCode: string;
     context?: string;
 }): Promise<{
     content: {

package/build/tools/modify-frontend.js

@@ -2,44 +2,42 @@ import { z } from "zod";
 import { generateWithGemini } from "../lib/gemini.js";
 import { MODIFY_FRONTEND_PROMPT } from "../prompts/system.js";
 export const modifyFrontendSchema = {
-    request: z.string().describe("What modification to make. Be specific and clear. " +
+    modification: z.string().describe("The SINGLE design modification to make. Be specific. " +
         "Examples: " +
-        "'Add a delete button with confirmation modal to each card', " +
-        "'Change the color scheme from blue to purple', " +
-        "'Add loading and error states to this component', " +
-        "'Make the sidebar collapsible with animation'"),
+        "'Redesign this button to look more premium with gradient and shadow', " +
+        "'Redesign the card header with better typography and spacing', " +
+        "'Make this sidebar look more modern with glassmorphism effect'"),
+    targetCode: z.string().describe("The specific code section to modify (NOT the full file). " +
+        "Pass only the relevant component/element that needs redesigning. " +
+        "This helps Gemini focus on exactly what to change."),
     filePath: z.string().describe("The path of the file being modified. " +
         "Example: 'src/components/Sidebar.tsx'"),
-    existingCode: z.string().describe("The COMPLETE current content of the file to modify. " +
-        "Pass the entire file, not just a snippet. " +
-        "Gemini will return the complete modified file."),
-    context: z.string().optional().describe("Additional project context if needed for the modification. " +
-        "Pass related files if the modification needs to match patterns from elsewhere. " +
-        "Optional - only include if relevant to the modification."),
+    context: z.string().optional().describe("Additional context about the file's design system. " +
+        "Example: 'Uses Tailwind, dark theme with zinc colors, rounded-xl borders'"),
 };
 export async function modifyFrontend(params) {
-    const { request, filePath, existingCode, context } = params;
+    const { modification, targetCode, filePath, context } = params;
     // Build context instructions
     let contextInstructions = '';
     if (context) {
         contextInstructions = `
-ADDITIONAL PROJECT CONTEXT (for reference):
+DESIGN CONTEXT:
 ${context}
 `;
     }
     const systemPrompt = `${MODIFY_FRONTEND_PROMPT}
 ${contextInstructions}
-FILE BEING MODIFIED: ${filePath}
+FILE: ${filePath}
 
-EXISTING CODE TO MODIFY:
+CODE TO MODIFY:
 \`\`\`
-${existingCode}
+${targetCode}
 \`\`\`
 
-MODIFICATION REQUESTED: ${request}
+MODIFICATION REQUESTED: ${modification}
 
-Remember: Return the COMPLETE modified file, ready to replace the original.`.trim();
-    const result = await generateWithGemini(systemPrompt, request);
+Remember: Return ONLY the find/replace block. ONE modification, surgical precision.`.trim();
+    const result = await generateWithGemini(systemPrompt, modification);
     return {
         content: [{ type: "text", text: result }],
     };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gemini-design-mcp",
-  "version": "3.0.1",
+  "version": "3.2.0",
   "description": "MCP server that uses Gemini 3 Pro for frontend/design code generation",
   "main": "build/index.js",
   "bin": {