> ## 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 Cursor

> Turn meeting decisions into Cursor-ready specs and code prompts

## From conversation to code

Earmark turns the conversation into Cursor-ready specs and code prompts. Instead of manually translating meeting decisions into engineering work, copy the artifact directly into Cursor and start building.

## How it works

<Frame caption="Engineering output formatted for Cursor">
  <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/7bmTb55b6UAEQSbk/images/artifact-integrations-cursor-linear-v0-codex.png?fit=max&auto=format&n=7bmTb55b6UAEQSbk&q=85&s=59556f7620e0e3aba890c19518f53997" alt="Engineering Specs style artifact with requirements and acceptance criteria ready to use in Cursor." style={{ width: '100%', display: 'block' }} width="1107" height="819" data-path="images/artifact-integrations-cursor-linear-v0-codex.png" />
    </div>
  </div>
</Frame>

1. Run a meeting with Earmark recording
2. Use the **Engineering Specs** template or write a custom prompt like "Generate a Cursor-ready spec for the API changes we discussed"
3. Earmark produces a structured artifact with requirements, acceptance criteria, and implementation guidance
4. Copy the output and drop it into Cursor as your starting prompt

## Best templates for Cursor workflows

* **Engineering Specs**: extracts actionable engineering items with motivation, requirements, and acceptance criteria
* **Technical Architecture**: captures architecture decisions, trade-offs, and component design
* **Ticket Generator**: produces structured tickets ready for implementation

<Tip>
  Be specific in your prompt about the technical context. "Generate a Cursor prompt for the auth refactor, focusing on the session token migration" produces better output than "Summarize the engineering discussion."
</Tip>