> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tryearmark.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Build in v0

> Convert meeting discussions into v0-ready UI prompts and component direction

## From conversation to UI

Skip the blank canvas. Earmark converts what you discussed into v0-ready UI prompts, components, and direction. Design discussions become actionable specs instead of vague notes.

## How it works

<Frame caption="v0-ready UI prompt from meeting context">
  <div
    style={{
  backgroundImage: 'url(https://mintcdn.com/earmark/vNkCE4NL0UOVgfZk/images/background-blue.png?fit=max&auto=format&n=vNkCE4NL0UOVgfZk&q=85&s=8d57271bb6e72c3715e83d97907c438b)',
  backgroundSize: 'cover',
  backgroundPosition: 'center',
  borderRadius: '1rem',
  padding: '4%',
}}
  >
    <div
      style={{
    borderRadius: '0.875rem',
    overflow: 'hidden',
    boxShadow: '0 24px 60px rgba(15, 23, 42, 0.28)',
  }}
    >
      <img src="https://mintcdn.com/earmark/OrYeOCJ-gjwRHqhp/images/v0-prompt.png?fit=max&auto=format&n=OrYeOCJ-gjwRHqhp&q=85&s=ae3adc048c62e08ebb5ba51c4b6a34c4" alt="Artifact with a v0-ready UI prompt including component descriptions and layout requirements." style={{ width: '100%', display: 'block' }} width="2752" height="1686" data-path="images/v0-prompt.png" />
    </div>
  </div>
</Frame>

1. Run a meeting where UI or design decisions are discussed
2. Use a custom prompt like "Generate a v0 prompt for the dashboard layout we discussed, including the data tables and filter sidebar"
3. Earmark produces a structured prompt grounded in what was actually said, with specific component descriptions, layout requirements, and interaction details
4. Paste the output into v0 and iterate from a real starting point

## Best templates for v0 workflows

* **Engineering Specs**: captures requirements including UI specifications
* **Topic Outcome Tracker**: records design decisions and open questions
* **Custom prompts**: "Write a v0 prompt for \[specific UI]" works well with Earmark's full transcript context

<Tip>
  Reference specific UI elements during the meeting. "The filter sidebar should have date range, status, and assignee dropdowns" gives Earmark the detail v0 needs to generate useful components.
</Tip>