Most teams don’t fail at AI because they lack tips.
They fail because there is no default.
Everyone has a private ChatGPT habit. The “good version” of a prompt lives in one person’s history. New hires start at zero. Managers call that “AI adoption.” It’s actually a standards gap.
You don’t fix a standards gap with a 40-role roadmap.
You fix it by shipping one team AI standard this week.
What a “standard” is (and isn’t)
A standard is not a longer Notion page of prompts.
It’s a named expert role people can actually use:
- A job (what it’s for)
- Guardrails (what it must not invent)
- A path into tools the team already opens
- A path into the org so it’s company property—not a DM
chamelAIn is built as your team’s shared AI playbook: roles live in the org; *you* can open a role in ChatGPT, Claude, or Gemini via a share link; teammates get access by joining the org and using roles published to the org catalog—not by receiving a forwarded link.
The five-step week
1. Pick one painful job
Choose one recurring task where quality swings by who “ran the AI”:
- Specs and acceptance criteria
- Change risk / rollout language
- Security review notes
- Narrative / positioning drafts
- Speed-to-ship engineering judgment
If everything is priority one, pick the task that creates the most rework.
2. Activate one official starter
New chamelAIn accounts already receive five official starters on My Personas.
Open My Personas, choose the starter that matches the job, and click Activate.
You are not collecting more prompts. You are choosing a default.
See Getting started.
3. Use it on real work once
A role that never touches real work is still a hobby.
Run the activated starter on one live task this week. Note what broke: missing context, wrong tone, weak constraints. Fix the role before you scale it.
4. Open it in *your* chat when you need to
When *you* want the same role in ChatGPT, Claude, or Gemini, create a share link from the persona (dashboard → persona → Share).
That link opens the role in your chat tools. No install required.
Important: a share link is not how you hand a role to a teammate. It does not transfer conversation history or create org access.
Optional later: builders can connect Cursor via MCP. That path is optional—not the whole story. See Connect MCP.
5. Invite the team and Publish to org
For the team standard:
- Invite people under Settings → Members
- Publish to org so the role lands in the org catalog
- Teammates activate the same role from the playbook
Publish to the public marketplace is a separate, plan-gated action. Don’t conflate “our org catalog” with “public listing.”
See Persona builder and Profile & settings.
Why this beats a prompt pile
| Prompt pile | Team standard |
|---|---|
| Strings in a doc | Named role with a job |
| No owner | Owned, versionable asset |
| DM the “good one” | Invite + publish for the org |
| New hires ask Sarah | New hires activate the default |
A folder full of prompts is an AI scrapbook.
A shared role playbook is how the org works.
What success looks like by Friday
- One starter activated
- One real task completed with it
- At least one teammate invited (or invite drafted)
- Role published to the org catalog (or ready to publish)
When that loop is boring, add the second role.
Start free
Get started free — official starters on day one.
Prefer a printable pack first? Team AI Playbook Starter Pack.