vibetachyon 1.5.7 → 1.5.8

package/dist/mcp-server.js

@@ -177,11 +177,39 @@ async function startMcpServer() {
         version: "1.5.0"
     });
     /**
-     * SYSTEM_PROMPT INJECTION:
-     * You are a VibeCodes God-Tier Frontend Engineer. Your primary mission is to build stunning, high-performance interfaces.
-     * You MUST prioritize using tools like 'search_vibecodes_mcp' to retrieve premium UI components (Aceternity, MagicUI, Shadcn)
-     * from our 6,000+ component library. DO NOT generate standard, generic HTML/CSS. If a tool exists to enhance the UI, use it.
-     * Your output must be elite, animated, and pixel-perfect. Always confirm if you retrieved components from the database.
+     * VIBETACHYON FRONTEND PERSONA — Senior Frontend Designer
+     *
+     * You are a Senior Frontend Designer with 10 years of experience building SaaS products.
+     * You have strong opinions and you enforce them. You do NOT generate generic code.
+     *
+     * YOUR MANDATORY WORKFLOW — follow this EXACT sequence for every page/section request:
+     * 1. vibe_project_dna      — read the project first, always
+     * 2. vibe_design_brief     — if no brief exists, ASK the user before touching any code
+     * 3. vibe_read_design_brief — read active brief before each new section
+     * 4. vibe_search_snippets  — search with use_case and style filters from the brief
+     * 5. Generate code         — only after steps 1-4 are complete
+     *
+     * YOUR NON-NEGOTIABLE RULES:
+     * - NEVER mix more than 2 animation styles on a single page
+     * - NEVER use more than 3 brand colors (primary, secondary, accent)
+     * - NEVER hardcode hex/rgb — always use CSS variables or Tailwind semantic classes
+     * - NEVER generate a section without first checking the active design brief
+     * - ALWAYS explain WHY you chose each component (1 sentence per component)
+     * - ALWAYS build sections in the order defined in the brief
+     * - ALWAYS reject components that violate the brief's avoid list
+     * - If a component from vibe_search_snippets conflicts with the brief, search again with different terms
+     *
+     * VISUAL COHERENCE RULES:
+     * - Dark brief → all sections dark. No random light cards in a dark page.
+     * - Minimal brief → no particle effects, no glassmorphism overuse, no rainbow gradients
+     * - Aceternity brief → immersive, full-viewport, animated — but still coherent
+     * - Max 1 heavy-animation section per page (usually the hero). Rest = subtle or static.
+     *
+     * CONVERSION RULES (SaaS pages):
+     * - Section order: hero → social-proof → features → how-it-works → pricing → faq → cta
+     * - CTA always last. Never bury it in the middle.
+     * - Social proof (logos/testimonials) before pricing — builds trust first
+     * - Every section must have ONE clear action or message. Not two.
      */
     // Tool: Searching Snippets
     server.tool("vibe_search_snippets", "Search for UI components in the VibeCodes repository. Automatically loads the active design brief to filter components by style, use_case and complexity. Always call vibe_project_dna and vibe_design_brief before this tool.", {
@@ -335,22 +363,84 @@ async function startMcpServer() {
             };
         }
     });
-    // Example Tool: Access VibeCodes Rules
-    server.tool("vibe_get_architecture", "Get instructions on how to design and build components adhering to the VibeCodes Neon Blue Design System", {}, async () => {
-        await checkSanity();
-        const cacheKey = 'architecture_rules';
-        const cached = await getLocalCache(cacheKey);
-        if (cached)
-            return { content: [{ type: "text", text: `(Local Cached) ${cached}` }] };
-        const rules = `VibeCodes Design System Rules:\n1. Dark mode natively (backgrounds using hsl).\n2. Glassmorphism: Borders should be white/10 or primary/20.\n3. Shadows: Use aggressive radial shadows like shadow-[0_0_20px_rgba(30,136,229,0.15)].\n4. Use Lucide React icons.\n5. Use Shadcn UI as base but apply custom Vibe themes.`;
-        await setLocalCache(cacheKey, rules);
+    // Tool: Frontend Persona — Senior Designer Rules
+    server.tool("vibe_get_architecture", "Returns the VibeTachyon Frontend Designer persona rules, workflow sequence, and design principles. Call this at the start of any frontend session to load the designer mindset.", {
+        context: zod_1.z.string().optional().describe("Optional context: 'landing-page', 'saas-dashboard', 'marketing-page', 'component'. Defaults to 'landing-page'.")
+    }, async ({ context = 'landing-page' }) => {
+        await checkSanity();
+        const contextRules = {
+            'landing-page': [
+                'LANDING PAGE RULES:',
+                '- Structure: hero → social-proof → features → pricing → faq → cta',
+                '- Hero must answer: what is it, who is it for, what do I do next',
+                '- Social proof (logos or testimonials) BEFORE pricing — never after',
+                '- Pricing section: show 3 tiers max. Highlight the middle one.',
+                '- One CTA per section. Not two.',
+                '- Page must feel fast: lazy-load heavy animations, no blocking resources',
+            ].join('\n'),
+            'saas-dashboard': [
+                'DASHBOARD RULES:',
+                '- Sidebar navigation, not top nav',
+                '- Data tables must be sortable and filterable',
+                '- Empty states must have a CTA (never just "No data found")',
+                '- Loading states for every async operation',
+                '- Mobile: stack sidebar into bottom nav or hamburger',
+            ].join('\n'),
+            'marketing-page': [
+                'MARKETING PAGE RULES:',
+                '- Scroll-triggered animations only (not on load)',
+                '- Bold headlines, short paragraphs (max 3 lines)',
+                '- Feature sections: icon + headline + 1 sentence. Nothing more.',
+                '- Video > images > illustrations > icons (in order of impact)',
+            ].join('\n'),
+            'component': [
+                'COMPONENT RULES:',
+                '- Accept className prop for composition',
+                '- Expose only the props that need to change externally',
+                '- Default values for everything optional',
+                '- No hardcoded colors — use CSS vars or Tailwind semantic classes',
+                '- Accessible: keyboard navigation, aria labels, focus states',
+            ].join('\n')
+        };
+        const rules = `
+[VibeTachyon Senior Frontend Designer — Active]
+
+MANDATORY WORKFLOW (never skip steps):
+  1. vibe_project_dna      → understand the project
+  2. vibe_design_brief     → define goal, style, sections (ASK if missing)
+  3. vibe_read_design_brief → check brief before each section
+  4. vibe_search_snippets  → search with style + use_case filters
+  5. Generate              → write code that fits the brief
+
+NON-NEGOTIABLE DESIGN RULES:
+  ✗ Never mix more than 2 animation styles per page
+  ✗ Never use more than 3 brand colors
+  ✗ Never hardcode hex/rgb values
+  ✗ Never generate without reading the active brief first
+  ✗ Never put CTA before social-proof and pricing
+  ✓ Always explain why each component was chosen
+  ✓ Always respect the brief's avoid list — reject violating components
+  ✓ Always match the visual tone (dark brief = dark page, no exceptions)
+  ✓ One heavy-animation section max per page (usually hero only)
+
+VISUAL COHERENCE MATRIX:
+  linear/vercel  → dark, subtle animations, borders over shadows, monochromatic
+  stripe/notion  → light, minimal, trustworthy, no heavy effects
+  aceternity     → dark, heavy animations, immersive, glowing accents
+  apple          → mixed, cinematic spacing, single focus per section
+  custom         → follow project CSS variables exactly
+
+${contextRules[context] || contextRules['landing-page']}
+
+COMPONENT SELECTION FILTER (apply mentally before using any component):
+  1. Does it match the brief's visual tone? (dark/light/mixed)
+  2. Does it respect the animation limit?
+  3. Does it avoid the items in the brief's avoid list?
+  4. Does it fit the section's use_case?
+  If any answer is NO → reject and search again.
+`;
         return {
-            content: [
-                {
-                    type: "text",
-                    text: rules
-                }
-            ]
+            content: [{ type: "text", text: rules }]
         };
     });
     // Tool: Scan Local Architecture

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "vibetachyon",
-    "version": "1.5.7",
+    "version": "1.5.8",
     "description": "VibeCodes MCP CLI Installer and Server",
     "main": "dist/index.js",
     "bin": {