---
name: matie-create
description: Create a Matie or reconnect its owner through one-time onboarding. Use only for guided setup, account verification, choosing a Playground and handing off the initial Taste.
---

# Set up Matie

For the first turn on a Node-capable host, fetch the small [form generator](onboarding-form.mjs) and run `node onboarding-form.mjs --identity https://matestable.com <private-fragment.html> en` (or `zh`). Present that locally generated fragment with the host’s native renderer immediately. Use the tested control layout as supplied. When the startup message contains a chosen preset, append its collection/slug after the language to preselect it.

For a new Matie, use the [first choices](references/quick-start.md#collect-setup-choices-and-first-taste)
to collect the starting city, Matie name and Avatar in one turn. For every round
that needs input, ask the current Agent host to create a private interactive
[onboarding form](references/forms.md). If that is unavailable, use the host's
structured question controls, then numbered text in chat. State the current
conversation's display limitation when switching to the fallback. Wait for the
owner's answers before advancing. Use the host's verified sign-in and attachment flows.

Use one Send to Agent action for each form. Send the selected answers as a
readable chat reply. Check for an existing owner connection after identity. A Mate account has one Taste Memory with public and private views. Adding or switching pets reuses it. For an owner without Taste, [delegate First Taste to Matie Taste](references/quick-start.md#delegate-first-taste).
Use its result when continuing onboarding.

In Codex, use the installed `visualize:visualize` skill when available. Include
its presentation reference to the generated form in the same turn's final reply.

The [progress page](https://matestable.com/matie/onboard/) shows setup progress. Before registration the owner can change their draft look under the pendant on the private setup page. Shared progress links are read-only. Keep
onboarding questions and answers in the Agent conversation.
Follow the owner’s chosen sign-in method. Collect an email address in chat only for the email-code option. For X, pass `{"method":"x"}` and share the complete first-party `authorizationUrl`, including its fragment. The owner verifies email on the website if prompted. Poll `account-status` and resume this preparation when verified. Only the email-code method asks for a code in chat. For that method, send just “Open <name>’s setup” using the private browser link. It also shows progress. Keep the shareable link for a separate sharing request. Resume an existing preparation using
the host's persistent private workspace.

Use `quick-setup` and `complete-hosted` for the official Playground and hosted
Taste. Follow [Agent onboarding](references/onboarding.md) for existing accounts,
connected Playgrounds and independent Taste. Keep credentials and private Taste
out of progress links.

For account and pet choices, use the account and roster forms in [first choices](references/quick-start.md). Keep instructions to one next action per message. Use the owner’s language.

After the handoff, install [Matie Taste](../matie-taste/SKILL.md)
in the user's Agent host and register the existing connection for future chats.

Invoke its first meal step and display two or three choices grounded in the owner’s preferences, city and local time, plus a free reply. If they have already asked for a meal, answer that request directly.

## Install Matie Taste

[Download Matie Taste](../matie-taste.tar.gz) and install the extracted `matie-taste` folder in your Agent. Follow the [connection guide](../matie-taste/references/connection.md) to use it in future conversations.
