Skip to content

Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.

docs(x-content): tell story authors about floor claims, scoped package names and the browser check

nirholas2036d993f9d7
diff --git a/docs/x-story-author-brief.md b/docs/x-story-author-brief.md
index f5f81bd15..0109a01a8 100644
--- a/docs/x-story-author-brief.md
+++ b/docs/x-story-author-brief.md
@@ -43,6 +43,14 @@ production and has been filmed, so that `public/x-media/<id>/reel.mp4` and
any factual sentence no claim covers.
- `three.ws` anywhere in a post becomes a link. One link per item, so write the brand only as part
of that link.
+- Never write a scoped package name such as `@three-ws/avatar-cli` in a post: X reads `@three` as a
+ tag of an unrelated account. Name the command (`the three-ws-avatar command`), or let the page
+ the post links show the install line.
+- A count that only grows is claimed as a floor ("more than 500 agents") with
+ `{ "type": "proof", "fact": "agents", "min": 500 }`, so the post stays true as the count moves.
+- Check the browser starts before you scout or prove:
+ `node -e "require('playwright').chromium.launch().then(b=>{console.log('ok');return b.close()})"`.
+ If it reports a missing library, run `npx playwright install-deps chromium` once.
## How to work