A Gem is useful for repeated tasks where the role, rules or output format stay relatively stable. Some creation features are web-only or account-dependent.
1. Start from a repeated task
Choose a task you already perform several times, such as editing, briefing, study review or a recurring analysis format.
2. Create a new Gem
Open Gems / Explore Gems and create a new Gem. Give it a name that describes the job rather than a personality.
3. Write durable instructions
Specify task, context, format, quality rules and what the Gem should do when information is missing.
4. Add knowledge only when it is truly reusable
Attach stable reference files when they should guide many future chats. Keep temporary case-specific material out of the permanent knowledge set.
5. Preview with edge cases, then save
Test a normal example, a missing-information example and a difficult example. Revise the Gem instructions before saving.
Gem instructions: Job: [repeat task]. Audience: [audience]. Always ask for [missing critical inputs] before starting. Use this output structure: [format]. Use knowledge files as references, but flag conflicts. Never invent missing numbers, dates or citations.
Turning every one-off prompt into a Gem; placing temporary client data in permanent knowledge; making instructions so long that priorities conflict; never testing failure cases.
Finish check
A good Gem should make a repeated task faster while remaining predictable when the input is incomplete or unusual.