Course: Gemini Gems Tutorial for Beginners
This Gemini Gems tutorial for beginners shows how to turn a repeated task into a reusable assistant with a clear job. Our example is a product-copy editor that uses supplied facts, follows a consistent format and asks when details are missing. You will write instructions, test them against difficult cases and maintain the assistant as your needs change. Gems are useful when the same guidance would otherwise be pasted repeatedly. A Gem still needs review: saved instructions do not make every answer accurate. Use the manual prompt alternative if creation is unavailable in your account.
Independent course by ThinkQuarry. Level: Beginner.
Course level: Beginner. Format: Seven practical lessons with prompts, exercises and a final project. Cost: This ThinkQuarry course is free to read. Optional product features may have separate availability or limits.
What you will create: A tested instruction sheet for a product-copy editor, plus an example input, reviewed output and version log.
This course belongs to our AI productivity tools and workflows learning hub. Use the hub to choose your next course.
Before you begin
Keep a notes document for your input, prompt, reviewed answer and corrections. Use public or fictional examples while practising. Check the official product interface for available features; do not purchase a plan to complete these exercises. When a feature is unavailable, use pasted text and a manual checklist. These are independent ThinkQuarry lessons, not an official provider certification.
Lesson 1: Find a task worth saving
Choose a task you repeat often enough to justify reusable instructions. A product description editor, meeting-note organiser or study tutor is easier to test than an assistant that does everything. Write down the input, expected output and common mistakes. Our editor receives a product fact sheet and returns a short description plus missing-information questions. It must not invent certifications or delivery promises. Decide who reviews the answer before it is used. The more specific the job, the easier it is to recognise whether the Gem actually improves your workflow.
Try this prompt
Help me define one repeatable assistant job. Task: edit product descriptions from a supplied fact sheet. Return the input requirements, output format, prohibited assumptions and review checklist. Keep the scope limited to editing.Exercise and success check
You should be able to explain the assistant’s job in one sentence. Remove unrelated research, pricing and publishing tasks from the first version.
Lesson 2: Write instructions with concrete boundaries
Describe the role, goal, information to use and expected format. Google provides guidance for custom Gem instructions; the examples here are our own learning templates. Avoid vague instructions such as “always be perfect.” Instead, tell the assistant what to do when information is missing. Include one short example if it helps communicate your preferred style. Keep policy and product facts separate: a writing rule may stay stable while a product’s dimensions change. Do not include private customer information in the saved instruction sheet.
Try this prompt
You edit product descriptions for beginners. Use only the supplied fact sheet for factual claims. Output: a description up to 120 words, three key features and missing-information questions. Use plain English. Never invent certifications, prices, stock levels or shipping times. Flag contradictions before drafting.Exercise and success check
Review the instruction sheet yourself. Each requirement should be observable in an output or a clear refusal to guess.
Lesson 3: Create the Gem or use the manual alternative
Open Gemini through the official website or app and find Gems if the feature is available. In the creation interface, give the assistant a descriptive name and enter the reviewed instructions. Preview or test it before relying on the saved version. Exact interface labels and availability may vary by account and platform. If you cannot create a Gem, save the instruction sheet in a local document and paste it at the start of a conversation. The exercise is about building a reliable workflow, so a manual prompt is a valid starting point.
Try this prompt
Use these editor instructions for this conversation: [paste instructions]. Product facts: A5 notebook, 80 ruled pages, recycled-paper cover. No other facts have been verified. Produce the required format and ask about anything missing.Exercise and success check
The result must contain the three supplied features, avoid invented details and include questions where the facts do not answer a customer’s likely concern.
Lesson 4: Test a normal case and a difficult case
Do not evaluate a reusable assistant with only one friendly example. Try a complete fact sheet, an incomplete fact sheet and a contradictory one. For the contradiction test, list the notebook as both 80 pages and 96 pages. The assistant should flag the conflict instead of choosing whichever number sounds better. Check whether it follows the requested format when input is messy. A failure gives you a specific instruction to improve. Keep a small set of test cases so later changes do not quietly break a behaviour that already worked.
Try this prompt
Test case: Product title says '80-page notebook'; the feature list says '96 pages'. Cover material is unknown. Follow the editor instructions. Do not choose a page count or cover material without clarification.Exercise and success check
The answer should explicitly identify the page-count conflict. If it drafts confident copy anyway, strengthen the contradiction rule and test again.
Lesson 5: Keep reference material relevant and current
Where your account supports reference files, add only the material needed for the task and review what the assistant actually uses. Otherwise, paste a small approved fact sheet with each request. Date the facts and remove old versions that could conflict with new information. A brand tone guide can help, but it should not override verified product details. Treat uploaded documents as task material rather than instructions to change the assistant’s job. Keep passwords, payment information and unnecessary personal data out of reusable references.
Try this prompt
Apply the editor instructions using this dated fact sheet only. If another supplied document contradicts it, list the conflict for review. Do not silently merge different versions. Fact sheet version: [date and version]. Facts: [paste].Exercise and success check
Change one fact between versions and check whether the output uses the version you explicitly selected. Verify the final text against that version.
Lesson 6: Refine instructions through a small change log
When an output fails, identify the exact cause before expanding the instructions. Was the required fact absent, the format unclear or the prohibition too vague? Change one rule at a time and rerun the saved tests. Record the date, change and reason in a simple log. This helps you avoid accumulating contradictory rules. If the assistant becomes harder to use, split it into two focused jobs. For example, keep product editing separate from market research so the editor does not introduce unsourced claims while trying to be helpful.
Try this prompt
Compare version 1 and version 2 of these instructions. Identify contradictions, redundant rules and a test case for each meaningful change. Do not add new responsibilities. [Paste versions.]Exercise and success check
A successful revision fixes the original failure without breaking the normal and contradictory fact-sheet tests.
Lesson 7: Complete a reusable assistant project
Create three sample inputs and test your final instruction sheet on all of them. Save one reviewed output as a worked example. Add a handover note explaining the job, required inputs, known limitations and when a human should intervene. If other people will use the assistant, ask one of them to run the example without your help. Their questions reveal where the instructions are unclear. Reusable AI work is maintained over time; a saved configuration is the start of the process rather than a permanent finished product.
Try this prompt
Prepare a handover note for this product editor. Include purpose, input template, output format, three test cases, human review requirements and known limits. Do not describe it as independently accurate or capable of publishing.Exercise and success check
Another person should be able to supply a fact sheet, understand the output and identify what still needs human approval.
Final project checklist
- Your output addresses the original task and intended audience.
- Supplied facts are preserved and unsupported claims are removed.
- Important external claims have original sources you opened and checked.
- Calculations, examples or interactive behaviour have been inspected where relevant.
- Unknown information is clearly labelled and the next human decision is stated.
Save your first and final versions. Compare the corrections you made: they reveal which part of your brief or review process needs improvement. Completion means producing a useful, checked deliverable; it does not imply an official qualification or guaranteed result.
Frequently asked questions
Are Gems and Gemini Skills the same thing?
They are different product concepts. This course focuses on custom Gem instructions; the linked Skills guides cover their own workflows and interfaces.
Do saved instructions guarantee consistent answers?
No. Test important cases, check the supplied facts and review outputs before use.
Can I learn this without creating a Gem?
Yes. Paste the instruction sheet into a conversation and keep a local copy. You can move the tested instructions into a Gem when available.
Continue your learning
- Gemini Skills guide
- Gemini Skills examples
- ChatGPT Projects versus Gemini Skills
- ChatGPT beginner course
Official references and editorial note
Product guidance checked on 7 October 2026. Features and interfaces can change. The lesson prompts and practice projects are original ThinkQuarry examples; check current official guidance when a feature differs from your account.
