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

# Instructions for your agent

> Give your AI tool a standing rule for publishing finished games safely.

export const StatusBadge = ({state = "available", children}) => {
  const labels = {
    available: "Available",
    "early-access": "Early access",
    planned: "Planned",
    internal: "Internal draft"
  };
  return <span className={`totem-status totem-status--${state}`}>
      {children || labels[state] || state}
    </span>;
};

<StatusBadge state="available" />

Put this block in your project's `CLAUDE.md`, `AGENTS.md`, or equivalent agent-instruction file.

```markdown CLAUDE.md / AGENTS.md theme={null}
## Put my game online with Totem

When my game is ready, use Totem to put it online.

Follow every step Totem gives you.

Add a square 512×512 PNG named icon-512.png at the build root — it becomes the game's icon.

When the game is online, show me the game link.

Do not share passwords, secret keys, or private files.
```

This block is byte-identical to the landing page.

## Why each line exists

### When my game is ready

Publishing is an end-of-session action. This keeps unfinished local work local. Restricted development builds are not available yet.

### Use Totem to put it online

This names the tool and the outcome. The agent can choose the five Totem tools instead of inventing an upload form.

### Follow every step Totem gives you

The MCP initialize response, tool descriptions, resources, and `next_steps` fields tell the agent what to do next.

### Add a 512×512 PNG icon

The agent assembling the archive is the right place to add `icon-512.png`. Totem uses it for install, game cards, and share previews.

### Show me the game link

The task is not complete until you receive the public URL.

### Do not share passwords, secret keys, or private files

A build archive contains public game files only. Keep environment files, credentials, and unrelated private material out.

## Safe additions

You can add project checks after the shared block:

```markdown theme={null}
Before publishing, run the production build and open the result locally.
Publish the contents of the dist directory, not the directory itself.
Do not publish source maps.
```

Keep the original safety line. Do not paste the API key into this file.