Experience

Pitching a developer

One portable sheet, readable top to bottom at phone width with zero interaction.

Asking for a job description

Intake is a conversation: the user writes a sentence and the system echoes back what it understood as chips.

Guided workflows

First runs get coachmarks anchored to what they explain, never a dimmed overlay or a spotlight.

Onboarding

First run is a short floating flow, not a form. Four steps, one line each, pineapples marking the way. Skip what does not apply, jump back to anything you finished, and the garden bursts when you are done.

Celebration

Celebration is the garden growing, where the evidence itself is the reward.

Decks and reports

Exported pages are editorial: one idea per page, a display headline of eight words or fewer, and no card soup.

A RevealCard in a PDF is the same component tree, POSTed to the render worker and captured server side.

POST /render
{
  "component": "RevealCard",
  "props": {
    "name": "Ada Lovelace",
    "handle": "ada",
    "verdict": "Ships compilers on weekends",
    "score": 96,
    "scoreLine": "96th percentile of systems engineers at this stage",
    "signals": [
      { "label": "Rust", "trust": "github" },
      { "label": "Top 3%", "trust": "score" }
    ],
    "repos": [
      { "name": "query-engine", "url": "https://github.com/ada/query-engine" }
    ],
    "weeks": [[{ "date": "2025-07-06", "count": 12 }]]
  }
}

Long-form intake

When the ask is bigger than one sentence, intake becomes a set of numbered steps with a clear commitment at the top and a single launch at the bottom.

Future