import Link from "next/link";
import { BlogFAQ } from "../BlogFAQ";
import { BlogInlineCTA } from "../BlogInlineCTA";
import type { TOCItem } from "../BlogTOC";

export const vibeDesigningFAQ = [
  {
    q: "What is vibe designing?",
    a: "Vibe designing is an AI-powered design workflow where you describe what you want in natural language, an AI generates a visual, and you iterate until the output matches your intent. The term comes from \"vibe coding,\" coined by Andrej Karpathy of OpenAI in February 2025.",
  },
  {
    q: "Is vibe designing the same as vibe coding?",
    a: "They share the same core idea but apply to different layers. Vibe coding produces working code. Vibe designing produces visual layouts, UI components, and design assets. In practice they often overlap.",
  },
  {
    q: "What tools are used for vibe designing?",
    a: "The most widely used in 2026: Figma's AI agent, Vercel v0, Lovable, Bolt.new, and Cursor. The right tool depends on where in your workflow you're applying it.",
  },
  {
    q: "Can vibe designing replace a professional designer?",
    a: "Not for product work that requires strategic judgment. It speeds up the visual execution layer. It doesn't replace user research, conversion thinking, or the ability to review AI output critically.",
  },
  {
    q: "How fast can a design team ship with vibe designing?",
    a: "For a landing page or marketing page, a skilled designer using AI tools can produce a quality first draft in hours rather than days. DesignShare delivers most requests in around 48 hours using these workflows with senior oversight.",
  },
  {
    q: "Should startups use vibe designing tools themselves?",
    a: "Yes, for prototyping, quick landing page tests, and internal tools where the stakes are low. For your core product, pricing page, and onboarding flow, having a senior designer involved in the strategic direction is still worth it.",
  },
];

export const vibeDesigningTOC: TOCItem[] = [
  { id: "origin", label: "Where it comes from" },
  { id: "looks-like", label: "What it looks like" },
  { id: "tools", label: "The tools in 2026" },
  { id: "good-for", label: "What it's good for" },
  { id: "limits", label: "Where it falls short" },
  { id: "need-designer", label: "Why you need a designer" },
  { id: "how-we-use", label: "How we use it" },
  { id: "faq", label: "FAQ" },
];

export function ArticleVibeDesigning() {
  return (
    <div className="b-prose">
      <p className="b-lead">
        A year ago, &ldquo;vibe coding&rdquo; was a niche term most developers
        hadn&rsquo;t heard of. Now it&rsquo;s the default way a lot of founders
        build their first product. Vibe designing is the same idea applied to
        design, and it&rsquo;s moving fast.
      </p>
      <p>
        If you&rsquo;re a founder or product lead trying to understand what your
        design team means when they talk about it, or trying to figure out
        whether it changes how you should be working, this post covers what it
        actually is, how the workflow plays out, and where it genuinely helps
        versus where it still falls short.
      </p>

      <h2 id="origin">Where the term comes from</h2>
      <p>
        Vibe coding was coined by Andrej Karpathy, co-founder of OpenAI, in
        February 2025. The idea was simple: instead of writing code manually, you
        describe what you want to an AI, review what it gives you, give feedback,
        and keep iterating. You focus on the intent and the outcome, not the
        implementation details.
      </p>
      <p>
        Vibe designing borrows that same logic for design work. Instead of
        manually placing components in Figma or building layouts frame by frame,
        you describe your intent in natural language, an AI generates a version,
        and you iterate until the output matches what you had in mind.
      </p>
      <p>
        Think of it as moving from being the person who builds everything by hand
        to being the creative director who shapes the direction and makes the
        critical calls. The mechanical execution speeds up dramatically. The
        important decisions still belong to you.
      </p>

      <h2 id="looks-like">What vibe designing actually looks like</h2>
      <p>
        Here&rsquo;s a practical example. Say you&rsquo;re building a new landing
        page for a SaaS product. Six months ago, the workflow looked like this:
        write a brief, send it to your designer, wait a few days for a first
        draft, give feedback, wait for revisions, repeat.
      </p>
      <p>
        With vibe designing, you open a tool, describe what you want. &ldquo;A
        landing page for a B2B project management tool, clean and minimal,
        targeting small engineering teams, hero with a headline about saving two
        hours a day, CTA to start a free trial.&rdquo; The AI generates a version
        in seconds. You review it, note what&rsquo;s off, describe the changes. It
        iterates. You&rsquo;re not waiting days. You&rsquo;re cycling through
        versions in minutes.
      </p>
      <p>
        What changes isn&rsquo;t the final quality bar. A well-designed,
        high-converting landing page still needs strategic thinking, brand
        consistency, real user research, and professional execution. What changes
        is the speed of getting to something worth reacting to.
      </p>

      <h2 id="tools">The tools driving it in 2026</h2>
      <p>
        <strong>Figma&rsquo;s AI agent</strong> (launched in beta May 20, 2026)
        is now the native vibe designing tool for product teams already in Figma.
        You describe a change or a new component in natural language directly on
        the canvas, and it executes. Rolling out to Professional, Organization,
        and Enterprise users ahead of Config 2026. We covered what this means for
        founders in our breakdown of{" "}
        <Link href="/blog/figma-ai-agents-startup-design-2026">
          Figma&rsquo;s AI agents and startup design
        </Link>
        .
      </p>
      <p>
        <strong>Vercel v0</strong> is built specifically for UI-first
        prototyping. You describe what you want, it generates responsive React
        components. Strong for front-facing pages and component libraries.
      </p>
      <p>
        <strong>Lovable and Bolt.new</strong> are closer to full-stack vibe
        coding tools. Useful for non-technical founders who want to go from idea
        to something that actually runs, not just a mockup.
      </p>
      <p>
        <strong>Cursor</strong> is the AI-native code editor for developers who
        want fine-grained control. Useful when you&rsquo;re close to
        production-ready code, not exploratory design.
      </p>
      <p>
        The tool you use depends on where in your workflow you&rsquo;re applying
        it. For early UI exploration, Figma&rsquo;s agent and v0 are the current
        standards. For going from idea to working prototype quickly, Lovable or
        Bolt.new.
      </p>

      <h2 id="good-for">What it&rsquo;s actually good for</h2>
      <p>Vibe designing genuinely accelerates a specific set of tasks:</p>
      <ul>
        <li>
          Landing pages and marketing pages where you need a fast visual to react
          to
        </li>
        <li>
          Exploring layout variations when the brand is established but you want
          to try different structures
        </li>
        <li>
          Internal tools, dashboards, and admin screens where function matters
          more than nuance
        </li>
        <li>Rough wireframes quickly to anchor a team conversation</li>
        <li>Teams iterating on something with an existing design system</li>
      </ul>

      <h2 id="limits">Where it still falls short</h2>
      <p>This is the part that doesn&rsquo;t get said enough.</p>
      <p>
        Vibe designing doesn&rsquo;t know your users. It doesn&rsquo;t know that
        your SaaS has a 68% drop-off at step two of onboarding, or that your
        pricing page caused three demo calls to stall last month. It produces
        output that is visually plausible but strategically generic.
      </p>
      <p>
        It also doesn&rsquo;t know your brand beyond what you explicitly describe.
        And describing brand accurately in a prompt is genuinely hard.
      </p>
      <p>
        Quality control is real work. Fast iteration produces a lot of output.
        Someone with design experience still needs to review it, catch
        what&rsquo;s wrong, and make the calls on what actually ships. If you let
        AI output go straight to production without that oversight, the results
        show.
      </p>

      <h2 id="need-designer">Why you still need a designer</h2>
      <p>
        Vibe designing makes certain parts of a designer&rsquo;s job faster. It
        does not make the judgment, strategic direction, or conversion thinking
        obsolete.
      </p>
      <p>
        The designers who are struggling with these tools are the ones treating
        them as an autonomous creative. The ones getting real value are using
        them as a fast execution layer while they focus on the direction.
      </p>
      <p>
        A designer who can describe intent clearly, review AI output critically,
        and iterate with precision is doing more in the same time. That&rsquo;s a
        better designer, not a replaced one.
      </p>

      <h2 id="how-we-use">How senior design teams are using it</h2>
      <p>
        At DesignShare, we&rsquo;ve been building these workflows into how we work
        for over a year. It&rsquo;s one of the reasons most requests come back in
        around 48 hours.
      </p>
      <p>
        The pattern that works: the senior designer sets the strategic direction,
        establishes the structure, and defines what the output needs to achieve.
        AI tools handle the fast execution layer, the bulk iterations, the
        component variations, the first visual passes. The senior designer
        reviews everything and makes the calls on what actually moves forward.
      </p>
      <p>
        Without that oversight layer, you get speed without quality. With it, you
        get both.
      </p>

      <BlogInlineCTA
        heading="Want a team that uses these workflows"
        accent="every day?"
        text="DesignShare delivers senior product design in ~48 hours, flat $3,495/mo. Pause anytime."
        cta="See how it works"
        href="https://designshare.net/#how"
      />

      <h2 id="faq">Frequently asked questions</h2>
      <BlogFAQ items={vibeDesigningFAQ} />
    </div>
  );
}
