sonance-brand-mcp 1.2.2 → 1.2.3

package/dist/index.js

@@ -3053,14 +3053,62 @@ This gives you the complete ${brand.toUpperCase()} component library including:
 
 **DO NOT proceed without calling get_full_library first.**
 
-### Step 2: Analyze the Application
-After getting the library, analyze the current application:
-- Identify all files that need brand updates
-- Create a prioritized list:
-  1. Root layout / theme provider
-  2. Navigation / header
-  3. Main pages
-  4. Shared components
+### Step 2: Audit the Existing Application (MANDATORY)
+You **MUST** thoroughly scan the existing codebase to understand what needs changing.
+
+**2a. Scan for Components**
+Search for and list all UI components:
+- Buttons, Cards, Inputs, Forms, Modals, Tables
+- Navigation components (headers, sidebars, menus)
+- Custom components in /components directory
+- Note: Which can be replaced with ${brand.toUpperCase()} library equivalents?
+
+**2b. Find Hardcoded Colors**
+Search for and list all color values:
+- Hex codes (#fff, #000, #3b82f6, etc.)
+- RGB/RGBA values (rgb(59, 130, 246))
+- HSL values
+- Tailwind color classes (bg-blue-500, text-gray-900)
+- Note: These ALL need to be replaced with semantic variables
+
+**2c. Locate Logo Files**
+Find all logo/brand assets:
+- Search /public, /assets, /images directories
+- Check for SVG, PNG, JPG logo files
+- Find where logos are imported/used in code
+- Note: These need to be replaced with ${brand.toUpperCase()} logos
+
+**2d. Check Theme/CSS Setup**
+Examine existing styling infrastructure:
+- globals.css or global styles
+- tailwind.config.js/ts (custom colors, fonts)
+- Theme providers or context
+- CSS variables already in use
+- Note: This is where ${brand.toUpperCase()} theme will be integrated
+
+**2e. Font Configuration**
+Check current font setup:
+- Font imports (Google Fonts, local fonts)
+- Font family declarations
+- Note: Replace with Montserrat
+
+**2f. Additional Findings**
+Note any other brand-related items discovered:
+- Third-party UI libraries (shadcn, MUI, Chakra, etc.)
+- Animation libraries with hardcoded color values
+- Icon sets that may need updating
+- Environment-specific styles or themes
+- Any other brand-inconsistent patterns
+
+**After auditing, create a change manifest:**
+| Category | Files Found | Changes Needed |
+|----------|-------------|----------------|
+| Components | list files... | Replace with ${brand.toUpperCase()} equivalents |
+| Colors | list files... | Convert to CSS variables |
+| Logos | list files... | Replace with ${brand.toUpperCase()} logos |
+| Theme | list files... | Integrate ${brand.toUpperCase()} theme |
+| Fonts | list files... | Switch to Montserrat |
+| Other | list files... | Address findings |
 
 ### Step 3: Redesign Systematically
 Work through the app in this order:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sonance-brand-mcp",
-  "version": "1.2.2",
+  "version": "1.2.3",
   "description": "MCP Server for Sonance Brand Guidelines and Component Library - gives Claude instant access to brand colors, typography, and UI components.",
   "main": "dist/index.js",
   "type": "module",