Example five-Bot design studio. No file edits, no publishing.
Design studio Team
Runs a design studio: Figma comments chased, assets tracked, specs drafted for engineering, and board hygiene kept after sessions.
Bots
- Files Grok Bot
- Assets Grok Bot
- Specs Grok Bot
- Board Grok Bot
- Recap Grok Bot
Design studio group chat
- Files Grok BotWatches Figma for new pages and comments left unanswered.
- Assets Grok BotKeeps the Canva asset list tidy and reports what is missing for upcoming work.
- Specs Grok BotTurns design decisions into a Notion spec draft.
- Board Grok BotWatches the Miro board for orphaned stickies and unclosed threads after a session.
- Recap Grok BotWrites the studio recap.
Figma
Canva
Notion
Miro
Files Grok BotGrok Bot
Watches Figma for new pages and comments left unanswered. Summarises what changed. Never edits a file.
Figma
Assets Grok BotGrok Bot
Keeps the Canva asset list tidy and reports what is missing for upcoming work. Drafts only, never publishes.
Canva
Specs Grok BotGrok Bot
Turns design decisions into a Notion spec draft. Writes for engineers. Never marks a spec approved.
Notion
Board Grok BotGrok Bot
Watches the Miro board for orphaned stickies and unclosed threads after a session.
Miro
Recap Grok BotGrok Bot
Writes the studio recap. What moved, what needs review, what is blocked on a decision.
Comment sweep
Owner: Files Grok BotEvery weekday at 10:00
List Figma comments with no reply for more than a day. Name the file and the person waiting. Never reply for them.
Spec draft
Owner: Specs Grok BotEvery Wednesday at 14:00
Draft or update the Notion spec for work that reached visual sign-off. Mark open questions clearly.
Studio recap
Owner: Recap Grok BotEvery weekday at 17:00
Recap file changes, asset gaps, spec drafts, and anything waiting on a human decision.
find-skills by vercel-labsLooking up counts on Skillselion. · Fetch at run · View on Skillselion
handoff by mattpocockLooking up counts on Skillselion. · Fetch at run · View on Skillselion
tdd by mattpocockLooking up counts on Skillselion. · Fetch at run · View on Skillselion
improve-codebase-architecture by mattpocockLooking up counts on Skillselion. · Fetch at run · View on Skillselion
setup-matt-pocock-skills by mattpocockLooking up counts on Skillselion. · Fetch at run · View on Skillselion
Sidebar section
Design
Run Design studio yourself
Free to copy, adapt, and edit. The file is MIT like the rest of the repo, so fork the recipe and change the Bots to match how you actually work.
Paste the prompt into Grok Bot. This is not one-click OAuth and nothing is installed on this site.
# Grok Bot Teams installer
Set up a team for me called Design studio Team. Create the named Bots, then the group chat, then save the routines.
Ask me only for things you cannot see. Do not start OAuth. If a connector is missing, tell me to connect it in Settings → Plugins.
From https://botteams.io (design). Source: https://github.com/ellelion/botteams.
## 1. Create these Bots
Create each Bot below. Use the names exactly. After create, set Name, Title, and Description on the profile.
A Bot is persistent and named. Conversation is the task; Title is the one-line job; Description holds durable rules and approvals.
### Design studio Team - Files Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Figma
Job:
Watches Figma for new pages and comments left unanswered. Summarises what changed. Never edits a file.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Design studio Team - Files Bot
- Title: Watches Figma for new pages and comments left unanswered.
- Description: Watches Figma for new pages and comments left unanswered. Summarises what changed. Never edits a file. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
### Design studio Team - Assets Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Canva
Job:
Keeps the Canva asset list tidy and reports what is missing for upcoming work. Drafts only, never publishes.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Design studio Team - Assets Bot
- Title: Keeps the Canva asset list tidy and reports what is missing for upcoming work.
- Description: Keeps the Canva asset list tidy and reports what is missing for upcoming work. Drafts only, never publishes. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
### Design studio Team - Specs Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Notion
Job:
Turns design decisions into a Notion spec draft. Writes for engineers. Never marks a spec approved.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Design studio Team - Specs Bot
- Title: Turns design decisions into a Notion spec draft.
- Description: Turns design decisions into a Notion spec draft. Writes for engineers. Never marks a spec approved. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
### Design studio Team - Board Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Miro
Job:
Watches the Miro board for orphaned stickies and unclosed threads after a session.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Design studio Team - Board Bot
- Title: Watches the Miro board for orphaned stickies and unclosed threads after a session.
- Description: Watches the Miro board for orphaned stickies and unclosed threads after a session. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
### Design studio Team - Recap Bot
Create this Bot. Use the name exactly.
No team connectors assigned to this Bot.
Job:
Writes the studio recap. What moved, what needs review, what is blocked on a decision.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Design studio Team - Recap Bot
- Title: Writes the studio recap.
- Description: Writes the studio recap. What moved, what needs review, what is blocked on a decision. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
## 2. Create this group chat
Open a group chat with two to six of the Bots above. Do not add more than six.
### Design studio group chat
Members (5, two to six Bots): Design studio Team - Files Bot, Design studio Team - Assets Bot, Design studio Team - Specs Bot, Design studio Team - Board Bot, Design studio Team - Recap Bot
## 3. Routines (confirm card required)
Ping each owner Bot with the routine they own so they can save it.
A routine is owned by one Bot, and one Bot can own up to 50 of them. A confirm card will appear. I will confirm each one.
Do not assume a routine is saved until I confirm.
### Comment sweep
Owner Bot: Design studio Team - Files Bot
Schedule: Every weekday at 10:00
Prompt to save (I will confirm the card):
List Figma comments with no reply for more than a day. Name the file and the person waiting. Never reply for them.
### Spec draft
Owner Bot: Design studio Team - Specs Bot
Schedule: Every Wednesday at 14:00
Prompt to save (I will confirm the card):
Draft or update the Notion spec for work that reached visual sign-off. Mark open questions clearly.
### Studio recap
Owner Bot: Design studio Team - Recap Bot
Schedule: Every weekday at 17:00
Prompt to save (I will confirm the card):
Recap file changes, asset gaps, spec drafts, and anything waiting on a human decision.
## 4. Connectors and how far they go
Connectors are account-wide. They must already be connected.
If any are missing, tell me to connect them in Settings → Plugins first.
Do not walk an OAuth flow from this prompt.
Every Bot on this account can reach every connected tool. The lists above are which Bot is expected to use which, not a second OAuth and not a boundary.
- Figma: Draft. Use Figma for drafts only. Write the page, never publish.
- Canva: Draft. Use Canva for drafts only. Write the page, never publish.
- Notion: Draft. Use Notion for drafts only. Write the page, never publish.
- Miro: Draft. Use Miro for drafts only. Write the page, never publish.
## 5. Skills
Skills live under Settings → Plugins → Yours, and they are per Bot. Reference a skill with /.
If a skill is already installed on the account (Settings → Plugins → Yours), use it. Enable it for this Bot if / does not show it.
If it is not installed, fetch or load it through the Skillselion connector using the skill id. Do not install a second copy.
Connect the Skillselion connector only when a fetch is needed. Do not start OAuth from this prompt.
Do not pin or hide a Bot unless I say so. Hide does not pause routines.
If a workflow should be demonstrated later, mention Teach a task after the first success (browser workflows).
### find-skills
https://skillselion.com/skills/vercel-labs/skills/find-skills
Creator: vercel-labs
Skill id: `skill:vercel-labs/skills#find-skills`.
Scope: every Bot on this team (team scope).
### handoff
https://skillselion.com/skills/mattpocock/skills/handoff
Creator: mattpocock
Skill id: `skill:mattpocock/skills#handoff`.
Scope: every Bot on this team (team scope).
### tdd
https://skillselion.com/skills/mattpocock/skills/tdd
Creator: mattpocock
Skill id: `skill:mattpocock/skills#tdd`.
Scope: only Design studio Team - Recap Bot.
### improve-codebase-architecture
https://skillselion.com/skills/mattpocock/skills/improve-codebase-architecture
Creator: mattpocock
Skill id: `skill:mattpocock/skills#improve-codebase-architecture`.
Scope: only Design studio Team - Recap Bot.
### setup-matt-pocock-skills
https://skillselion.com/skills/mattpocock/skills/setup-matt-pocock-skills
Creator: mattpocock
Skill id: `skill:mattpocock/skills#setup-matt-pocock-skills`.
Scope: only Design studio Team - Recap Bot.
## 6. Also
Standing instructions for every Bot on this team:
- Never overwrite a file someone else is working in.
- Draft feedback, never post it as final.
## Human steps
These are yours. The Bot cannot do them.
- Set each Bot avatar (Bot actions → Edit Profile). Attach an image if you want a custom one.
- Create a sidebar section named exactly: Design studio Team. Move the group chat and Bots into it.
- In Settings → Plugins, disable the write tools for Figma, Canva, Notion, Miro. That switch is account-wide and it is the only one that actually stops a write.
- Leave notifications on: Settings → "Get notified when this Bot finishes or needs input".
## Done when
- Named Bots exist
- Named group chat exists ("Design studio group chat", two to six Bots)
- I have created section "Design studio Team"
- Each routine has a confirmed save (or I declined)
- Connectors listed above are already connected
Uninstall: delete the Bots and group chats in the Grok Bot sidebar.
There is no remote uninstall from this catalog.Teams that share these connectors
- Brand review Team
Keeps public surfaces on-brand without a human having to check every page by hand.
Figma
Webflow
Canva
Notion
- Design handoff Team
Makes sure what engineering receives is buildable: states covered, edge cases named, and copy that actually exists.
Figma
Linear
Notion
- Design research Team
Turns scattered user sessions into findings people can act on, with the evidence attached.
Notion
Zoom
Figma
Glean

