HubToolify

View saved version →

---
name: festival-and-greeting-kit
description: Put together HubToolify stickers, illustrations and icons for a festival, holiday or occasion, such as Diwali, Eid, Christmas, a birthday, a wedding or a thank-you. Use when the user wants visuals to greet someone, decorate a post or message, or plan festive designs.
---

# Festival and greeting kit

Explicit instructions from the user always come first. If they ask for only stickers, or only one item, do just that.

## Workflow

1. **Name the occasion** and, if the user said so, where the visuals will be used (a chat message, a social post, a card, a website banner).
2. **Stickers first.** Call `search_stickers` with the occasion as `query` (for example "happy diwali"). If the user wants motion for a chat or story, set `animated` to true.
3. **Then illustrations** for larger designs (posts, banners, cards): call `search_illustrations` with the occasion as `query`. If nothing matches, try a broader word (for example "celebration", "gift" or "family").
4. **Optionally icons** for small decorations or a website: `search_icons` with the occasion or its symbols (for example "diya", "lantern", "gift").
5. **Summarise** what was found in a few lines: the best 3–5 stickers and the best illustrations by name, and which one suits which use.
6. **Downloads when asked:** `get_sticker`, `get_illustration` or `get_icon` with the exact names from the searches.

## Rules

- Use only names the search tools returned. If an occasion has no match, say so and offer the closest general results; never invent a sticker or scene.
- Some downloads depend on what the connected HubToolify account includes. When a result says something is not included, say so plainly and keep showing the previews. Do not mention prices.
- Be respectful with religious festivals: describe the visuals neutrally and do not add religious claims of your own.

View saved version →

---
name: find-the-right-tool
description: Find the HubToolify online tool, or the short chain of tools, for a file or text job, such as compressing or resizing an image, converting between formats, merging or splitting a PDF, editing a video, writing or checking text, SEO or developer tasks. Use when the user describes a task and wants a tool to do it.
---

# Find the right tool

Explicit instructions from the user always come first.

## Workflow

1. **Restate the job** in a few words: what the user starts with and what they want at the end (for example "a 6 MB photo → under 1 MB for email").
2. **Search** with `search_tools`, using the job as `query` (for example "compress image" or "merge pdf"). Add `category` only if the job is clearly in one.
3. **Multi-step jobs:** if the job needs more than one step (for example "turn these photos into one small PDF"), search each step and give them in order: step → tool.
4. **Answer briefly:** the best tool, one line on what it does for this job, and its link. Mention a second tool only if it is a real alternative.

## Rules

- Recommend only tools that `search_tools` returned, with the link it gave. Never invent a tool or a link.
- The tools run on hubtoolify.com; this app does not change the user's files inside ChatGPT. Say so if the user expects the file to be processed here.
- Some tools depend on what the connected HubToolify account includes; the results say so. Report it plainly. Do not mention prices.
- If no tool fits, say that clearly instead of stretching an unrelated tool to fit.

View saved version →

---
name: icon-set-for-a-project
description: Build a matching set of HubToolify icons for an app, website, slide deck or document. Use when the user wants several icons that belong together (a navigation bar, a feature list, a dashboard, a menu), or asks for icons for their project.
---

# Icon set for a project

Explicit instructions from the user always come first. If they name icons, a style, a size or a colour, follow that.

## Workflow

1. **List the concepts.** Turn the request into a short list of things the icons must show, one word or phrase each (for example: home, search, profile, settings, cart). If the user gave only a project type ("a food delivery app"), propose 6–10 concepts and go ahead with them; the user can change the list later.
2. **Pick one style for the whole set.** Use the style the user asked for, otherwise `line`. Every icon in the set uses the same style so they look like one family. Styles: line, solid, duotone, sharp-line, sharp-solid, sharp-duotone, imprint, pixel, slab, mellow, jass, 3d, draw, lineal, duo, flat.
3. **Search each concept** with `search_icons` (`query` = the concept, `style` = the chosen style, a small `limit` such as 6). Take the best match for each concept from the returned names.
4. **Report the set** as a short table: concept → icon name. Mention any concept with no good match and suggest the closest alternative instead of inventing one.
5. **Deliver files when asked.** Call `get_icon` for each icon the user wants, with the same `style`, plus `size` and `color` if the user gave them. The widget shows the SVG and its download link.

## Rules

- Use only icon names that `search_icons` returned. Never make up an icon name.
- Keep one style across the set unless the user asks to mix styles.
- If a result says a style is not included in the connected account, say so plainly and offer the same set in `line`, `solid` or `duotone`. Do not mention prices.
- HubToolify has no third-party brand logos. If the user asks for a brand's logo, say it is not available rather than presenting a generic icon as that logo.

View saved version →

---
name: product-screen-illustrations
description: Choose HubToolify illustration scenes for the screens of an app or website, such as onboarding, empty states, errors, success messages, sign-up or help pages. Use when the user is designing a product and needs pictures that fit specific screens with one consistent look.
---

# Illustrations for product screens

Explicit instructions from the user always come first.

## Workflow

1. **List the screens** the user needs pictures for. If they only described the product ("a budgeting app"), propose the usual set: welcome or onboarding, empty state, success, error or offline, and help.
2. **Search per screen** with `search_illustrations`, using the screen's purpose plus the product's subject as `query` (for example "empty inbox", "welcome", "success", "no results", "team"). Use a small `limit` such as 6.
3. **Keep one look.** Each result has a `pack`. Prefer scenes from the same pack so the screens look like one product. Once a good pack shows up, search again with `pack` set to it for the remaining screens.
4. **Animated scenes** suit onboarding and success screens. Set `animated` to true when the user wants motion.
5. **Report** a short table: screen → scene name (pack). Point out any screen with no good match and offer the nearest scene instead of inventing one.
6. **Downloads when asked:** `get_illustration` with the scene name. Still scenes come as SVG; animated ones also as MP4, GIF and Lottie JSON.

## Rules

- Use only scene names that `search_illustrations` returned.
- When a result says illustration downloads are not included in the connected account, say so plainly; the previews stay available. Do not mention prices.