Bring in expert teams
It can work on its own, but you can also bring in "reinforcements": ready-made capability packs, full expert teams, and MCP servers that call external tools. This chapter explains what the three kinds are and when they're worth using.
Three kinds of reinforcements, first
| Kind | What it is | Where to find it | When to use it |
|---|---|---|---|
| Skill | A pack of expertise the AI references automatically on relevant tasks | "Add" on the left of the input box → "My skills" | When you want it to follow a certain professional approach |
| Expert team | A group of role-divided members that enters with multiple capabilities at once | Same place — cards with the "Team" badge | When the task is complex and needs systematic execution |
| MCP | Connect an external tool service so it can call tools | "Add" → "MCP", or "More" → "Development" → "MCP" | When it needs to look up external systems or connect internal tools |
Skills: pick one, click "Use"
Click "Add" on the left of the input box → "My skills", and the dialog shows a few kinds of cards:
Official skills (with the "Official" badge)
| Skill | What it produces |
|---|---|
| Professional resume | Turns your resume into a polished single-page website, with layout and copy optimized for job hunting |
| Company website | An external website for a company or product: hero section, value proposition, social proof, pricing, FAQ, call-to-action |
Click "Use" on a card and it fills a kickoff request into the input box — just add your own details and you're off.
Expert teams (with the "Team" badge)
| Expert team | What it does for you |
|---|---|
| Product Strategy expert team | Turns a vague idea into a validated strategy: user research, competitive analysis, positioning, roadmap |
| Hi-Fi UI Design expert team | Produces production-grade high-fidelity interfaces directly — no wireframes |
| Software Development expert team | Frontend, backend, architecture, product, and QA together: planning, building, debugging, delivery |
The usage is the same: click "Use", and the input box gets a sentence starting with "Use the XXX expert team lead to…" — append your requirements after that sentence and send.
Cost note: expert teams load several large methodology skills into the context, so they consume noticeably more credits than a normal conversation — the Hi-Fi UI Design team especially. Consider them when the task is worth doing carefully and you've confirmed you want to proceed.
Custom skills: codify your rules
If you have a fixed way of working (e.g. "our copy must include concrete numbers, never use empty buzzwords"), you can turn it into a skill:
- Click your avatar in the top right → "Settings"
- Select "Skills" on the left
- Click "New skill", write a name and content
- Save
Skills are account-level and apply to all your apps automatically. A skill is just a piece of instruction text that states "how to do it, and what not to do".
Set project rules: Instructions
"Skills" govern your habits across all projects; "Instructions" govern the rules of one specific project.
Where: in the workspace click "More" on the right → "Development" → "Instructions".
Good things to put in:
- Technical conventions for the project (e.g. "all endpoints start with /api")
- Things not to touch (e.g. "don't modify login-related code")
- Fixed phrasing (e.g. "always show amounts with two decimal places")
Once written, every conversation in that project follows it.
MCP: let it use external tools
MCP is the way to give the AI external capabilities. Once connected, it can call the tools that service provides.
- Click "Add" on the left of the input box → "MCP" (or find it under "More" → "Development" → "MCP")
- Click "Add server"
- Fill in the name and address (must start with https, Streamable HTTP protocol)
- Fill in the auth headers if needed, and save
After saving, it applies to all your apps — the AI will automatically use these tools when it encounters relevant tasks.
Not sure what MCP is? Don't worry: most apps never need it. Come back to this section when you hit a need like "can it look up data in one of my systems?"
Should you use an expert team? One rule of thumb
| Situation | Suggestion |
|---|---|
| A small tool that fits in one sentence | Skip the teams — build it directly, faster and cheaper |
| A complete product design with a lot of interface polishing | The design team is worth it |
| A real project that must be shipped and maintained | The software development team is worth it |
| Just validating an idea | Build a prototype in a normal conversation first, then decide whether to call in a team |