Designing a High-Converting Landing Page with cm-ux-master

The “Template Trap” is the silent killer of the modern Vibe Coder. You’ve mastered the art of intent-driven development; you can spin up a functional CRUD application or an AI-integrated dashboard in a single afternoon using Gemini CLI. But then comes the moment of truth: you share the link, and the bounce rate is astronomical. Users arrive, squint at a wall of generic components, and leave before they even reach your call-to-action.

The problem isn’t your code. It’s your High Craft—or lack thereof. In a world where anyone can generate a functional layout, conversion is won through psychological leverage, visual hierarchy, and the ruthless application of design truth. This is where cm-ux-master becomes the most powerful weapon in your Vibe Coding arsenal. It is not just a component generator; it is a design intelligence engine that bridges the gap between “it works” and “it sells.”

The Architecture of Conversion: How it Works

cm-ux-master is built on a foundation of four critical pillars that transform subjective “vibes” into objective design excellence:

The 48 UX Laws & 37 Design Tests: This is the analytical brain. Instead of guessing if a button is big enough, the skill applies Fitts’s Law. Instead of hoping your pricing table is clear, it runs a Hick’s Law complexity audit. The 37 Design Tests are a series of automated and agentic checks—like the “Squint Test” (checking visual hierarchy) and the “5-Second Test” (ensuring the value proposition is immediate).
Harvester v4 (Semantic Extraction): This is the skill’s ability to “look” at top-tier, high-performing websites and extract their “soul.” It doesn’t copy the CSS; it identifies the spacing ratios, font pairings, and emotional triggers that make a Stripe or an Apple landing page feel premium.
UX Heuristics (Nielsen + Krug): By adhering to established industry standards like Nielsen’s 10 Usability Heuristics and Steve Krug’s “Don’t Make Me Think” principles, the tool ensures your landing page is inherently intuitive.
Component Realism: Unlike generic AI generators that output “Div Soup,” cm-ux-master utilizes its BM25 search across 16 domains to generate components that are accessible, responsive, and performance-optimized from the first line of code.

The Vibe-to-Conversion Workflow: A Practical Example

Let’s walk through the implementation of a landing page for a fictional product: VibeTrace, an observability tool for AI agents. We want to move from a vague idea to a validated, high-converting design system.

Phase 1: The Psychological Foundation (`cm-jtbd`)

Before touching a single pixel, we must understand the “Job” the user is hiring our landing page to do. We invoke the cm-jtbd (Jobs-To-Be-Done) framework within our planning phase.

Intent: Identify why a user would “hire” VibeTrace. Outcome: A “Job Statement” that informs our Hero section: “When I’m deploying autonomous agents in production, I want to see exactly where the logic loop broke, so that I can fix the agent before it drains my API credits.”

Phase 2: Design Extraction with Harvester v4

We don’t want a generic landing page. We want it to feel like a high-end developer tool. We instruct cm-ux-master to analyze a reference.

# Example instruction to the agent
gemini activate_skill cm-ux-master
"Analyze the landing page at linear.app/method. Extract the spacing system, the use of dark-mode gradients, and the 'Feature Bento' layout logic. Save this as a design-token-manifest in .pen format."

The Harvester v4 engine scans the reference and generates a DESIGN.md file that codifies these attributes. It identifies that the “Linear look” relies on 8px grid increments, 0.02em letter spacing on headings, and a specific “glassmorphism” overlay for code blocks.

Phase 3: The Component Generation Loop

Now we use the Component Generator to build our Hero section. Instead of a simple header, we demand a conversion-optimized structure.

"Generate a Hero component for VibeTrace using the Linear design tokens. 
Include:
1. An 'Over-the-Fold' Value Prop (Hook).
2. A 'Grand Slam Offer' CTA button.
3. A 'Social Proof' strip for logos.
4. An interactive terminal mockup showing an agent log."

cm-ux-master won’t just give you HTML. It will generate a React component that uses Vanilla CSS (per project standards) with CSS variables linked to our design tokens.

Phase 4: Ruthless Validation (The 37 Tests)

This is the most critical step. Once the prototype is in the .pen editor, we run the design tests. One of the most effective is the Squint Test.

The Squint Test Logic:

Goal: Ensure the most important elements (Headline and CTA) are the first things seen.
Process: The agent simulates a blurred view of the UI. If the “Sign Up” button and the “Headline” aren’t the most prominent blurred shapes, the layout fails.

If the test fails, cm-ux-master suggests a Correction Operation:

“Heuristic Violation detected: CTA button has low contrast ratio (3:1) against background. Suggesting Update to Primary Color #38BDF8 (12:1 ratio) to satisfy WCAG 2.2 and Fitts’s Law prominence.”

Phase 5: Closing the Loop with Stitch

Finally, we use the pencil MCP tools to sync this validated design into our project. Because cm-ux-master is integrated with Google Stitch, it can generate a production-ready UI preview. You can visually inspect the interaction of the terminal mockup before committing to the full frontend build.

Best Practices for High-Craft Vibe Coding

To maximize the impact of cm-ux-master, you must adopt a “Security and Quality First” mindset. Design is not just how it looks; it’s how it handles failure.

1. Master the “Objection/Counter-Objection” Framework

A high-converting page isn’t just about features; it’s about answering the user’s internal doubts. Use the cro-methodology within your design prompts.

Objection: “Is it hard to integrate?”
Design Solution: A “Three Lines of Code” section with a “Copy” button.
Objection: “Will it slow down my agents?”
Design Solution: A “Performance Benchmark” chart generated with d3-viz.

2. Enforce the 8px Grid

Consistency is the difference between amateur and professional. cm-ux-master defaults to an 8px grid system. Never use “random” padding like 13px. Stick to 8, 16, 24, 32, 48, 64. This creates a mathematical rhythm that the human eye perceives as “stable” and “trustworthy.”

3. Semantic Color Tokens

Don’t use hardcoded hex codes in your components. Use tokens:

--color-surface-primary
--color-text-vibrant
--color-action-cta This allows you to switch from a “Dark Mode” developer aesthetic to a “Light Mode” enterprise aesthetic in seconds by updating the variables via the set_variables tool in the Pencil editor.

4. Accessibility as a Conversion Metric

Accessibility is not just a legal requirement; it’s a conversion optimizer. A user with poor lighting on their mobile device has the same “visual impairment” as someone with permanent low vision. By enforcing WCAG 2.2 via the cm-ux-master audit gates, you ensure your page is readable for everyone, in every condition.

The Squint Test: A Practical Drill

Try this right now on your current project. Open your landing page. Stand back 5 feet and squint your eyes until the text is unreadable.

Can you see exactly where you are supposed to click?
Does the “shape” of the page lead your eye in a “Z” or “F” pattern?
Is there a massive blob of grey (text) that feels like “work” to read?

If you can’t answer “Yes” to the first two and “No” to the last, you are leaving money on the table. Invoke cm-ux-master and ask it to “Perform a Squint Test and restructure for Z-pattern eye-flow.”

Conclusion: From Vibe to Value

Vibe Coding gives us the speed of thought, but cm-ux-master gives us the discipline of a world-class design agency. By integrating this skill into your workflow, you stop building “AI demos” and start building “Digital Products.”

The goal of a landing page is a Handshake. It is the moment where you prove to the user that you understand their problem (cm-jtbd), that you have a professional solution (cm-ux-master), and that you can be trusted to deliver it. Don’t let your “vibe” get lost in a sea of generic templates. Elevate your craft, validate your assumptions, and convert your traffic into a community.

Your code is ready. Is your design? Activate cm-ux-master and find out.