Why do you keep re-typing the same context into Gemini every day?
If you paste the same background, tone rules, and instructions into Gemini for every similar task, you are paying an invisible tax. A Gemini Gem removes it by saving that setup once into a reusable assistant you open and use instantly. Same quality, zero re-typing.
Most intermediate users discover Gems exist, try one of Google's pre-made ones, and never build their own. That is the gap this guide closes.
The payoff is concrete. A task that took three minutes of setup plus a minute of writing drops to one click and the actual request.
By the end of this article you will have built a working Gem for one of your real recurring tasks, in under ten minutes.
This is not a feature reserved for advanced users. If you can write a clear paragraph describing what you want, you can build a Gem that produces it on demand.
What is a Gemini Gem?
A Gemini Gem is a saved version of Gemini pre-loaded with a name, a description, custom instructions, an optional default tool, and optional knowledge files. It is a specialist you design once for a specific job, then reuse without re-explaining context every session.
Think of it as a custom GPT inside Gemini, or a colleague you have already briefed.
Gems differ from Gemini's global custom instructions in one important way. Custom instructions apply to every conversation you have. A Gem applies only when you open that specific Gem.
That separation matters. You can keep a formal "Client Email" Gem and a punchy "Social Caption" Gem side by side, each with its own tone, without them interfering.
It also means you can experiment safely. A new Gem never touches your default Gemini behaviour, so you can build, test, and discard ideas without disrupting your everyday chats.
According to Google's own Gemini Apps Help, Gems are available on the free plan as well as every paid tier, and you can create as many as you need.
How do you create a custom Gemini Gem step by step?
Open gemini.google.com, expand the menu, and click Gems to reach the Gem manager. Click New Gem, give it a name, write its instructions, optionally set a default tool and upload knowledge files, then preview and save. The whole process takes under ten minutes.
Here is the exact sequence.
1. Open the Gem manager. In the Gemini sidebar, click Gems. You will see Google's pre-made Gems, any Gems you have built, and a New Gem button.
2. Name and describe it. Give the Gem a clear name like "HK Client Email Drafter" so you can find it later.
3. Write the instructions. This is the heart of the Gem. Google recommends 500 to 2,000 characters for best performance. Cover the role, tone, focus, format, and constraints.
4. Pick a default tool. Options include no default, Create image, Canvas, Deep Research, Create music, and Guided Learning. If your Gem always researches, set Deep Research as the default.
5. Add knowledge files. Under Knowledge, upload reference documents from your device or Google Drive. These persist with the Gem, so you never re-upload them.
6. Preview and save. Use the preview panel on the right to test a prompt. When the output looks right, click Save.
One detail people miss: the preview panel is your test bench. Run two or three realistic prompts before saving, and tweak the instructions until the output is consistent. Five minutes of testing here saves hours of disappointing results later.
Your saved Gem then appears in the sidebar, ready to open like any chat. You can edit, duplicate, or share it with colleagues at any time.
What makes a Gem's instructions actually work?
Strong Gem instructions follow a five-part structure: role definition, communication style, knowledge focus, response format, and constraints. This structure tells the model who it is, how to sound, what to prioritise, how to shape output, and what to avoid, removing the guesswork that causes inconsistent results.
Vague instructions like "be helpful and write good emails" produce vague Gems. Specific structure produces a reliable specialist.
Here is a copy-paste instruction template you can drop straight into the instruction field and adapt.
Try this Gem instruction template:
ROLE: You are a [specific role] who helps me [specific job] for [my company type] in Hong Kong.
STYLE: Write in [tone]. Use [language]. Keep sentences short and direct.
FOCUS: Prioritise [the thing that matters most]. Always include [required element].
FORMAT: Return every response as [exact structure, for example: subject line, then 3 short paragraphs].
CONSTRAINTS: Never [list what to avoid]. If you lack information, ask me one question rather than guessing.
Notice the last line. Telling a Gem to ask rather than guess is the single most effective way to cut confidently wrong output.
Google also offers a "Use Gemini to re-write instructions" button, which expands a rough draft into a fuller instruction set you can then edit.
Treat that button as a starting point, not the final word. It is excellent for fleshing out structure quickly, but you should always read the result and cut anything that does not match how you actually work.
One more tip: write your instructions in the same language you want the Gem to respond in. A Gem instructed in Traditional Chinese tends to hold that voice more consistently than one instructed in English but asked to reply in Chinese.
What does a real Gem workflow look like for a Hong Kong professional?
A practical example: a "Client Email Drafter" Gem loaded with your company tone guide and three approved past emails as knowledge files. Each time, you paste the client's message and a one-line goal, and the Gem returns a ready-to-send draft in your house style within seconds.
Walk through how an account manager would build it.
The role line names the job: drafting replies to client emails for a Hong Kong professional services firm. The style line locks the tone to polite, concise business English or Traditional Chinese.
The knowledge files do the heavy lifting. Upload the firm's tone guide and three strong past replies, and the Gem mirrors that voice automatically, with no description needed.
The daily use is fast. Paste the incoming email, add "goal: reschedule the meeting politely and propose two new times," and the draft arrives in your voice.
The same pattern works for a recruiter screening CVs, a marketer writing product descriptions, or an operations lead summarising weekly reports. Build the Gem once, reuse it for months.
The hidden benefit is consistency across a team. If three colleagues use the same shared Gem, every client email leaves the company in the same voice, regardless of who drafted it. That is hard to achieve with one-off prompts where everyone phrases things differently.
What are the most common Gemini Gem mistakes?
The three most common mistakes are writing instructions that are too short, skipping knowledge files, and never updating the Gem. Thin instructions leave too much to chance, missing knowledge forces generic output, and a stale Gem quietly produces outdated answers based on old reference files.
Each one is easy to avoid.
Instructions too short. A single sentence wastes the Gem's potential. Use Google's 500 to 2,000 character guidance and cover all five structural parts.
No knowledge files. Without your real documents, the Gem only knows generic patterns. The uploaded files are what make output sound like you, not like every other Gemini user.
Never updating. A Gem built six months ago may reference outdated pricing, products, or policy. Review and refresh the knowledge files when anything material changes.
Building one giant Gem. A single Gem that tries to do emails, captions, and reports does all three poorly. Build narrow, specialised Gems instead.
A simple rule keeps you on track: one Gem, one job. If you cannot describe what a Gem does in a single short sentence, it is trying to do too much and should be split into two.
Try it now: build your first Gem in 10 minutes
Choose one task you do at least weekly. Open Gemini, click Gems, then New Gem. Paste the instruction template above, fill in every bracket with your real details, and upload one or two reference documents as knowledge files. Preview a test prompt, adjust, and save.
Run it on a real task tomorrow and compare it to your usual from-scratch prompt.
The difference is not a smarter model. It is a model that already knows your job, waiting in your sidebar.
Once you have one working Gem, building the next takes half the time. Most power users end up with a small shelf of them, one per recurring task, each saving a few minutes that quietly add up across a week.
That is the real promise of tools like this, and it is why we have spent 28 years helping Hong Kong teams turn new technology into something that actually saves time. We understand AI. We understand you better. With UD by your side, AI doesn't feel cold.
Turn One Gem Into a Whole AI Workforce
One Gem saves you minutes. A team of purpose-built AI assistants saves you whole workflows. We'll walk you through every step, from designing your first Gem to building a library of AI employees that handle your most repetitive work reliably.
