Designkit

View saved version →

---
name: brand-visual-design
description: Develop logo directions, brand-guideline visuals, packaging concepts,
  and branded application mockups with Designkit. Use for new identity concepts or
  applications of brand assets; not manufacturing files or trademark clearance.
---

# Brand Design

Use the [bundled preset catalog](references/presets.json) to match the user's requested outcome, including natural-language phrases or an alias they explicitly use. Present a short menu only when asked to browse or when the goal is genuinely ambiguous. The local catalog supplies creative workflow guidance; it is not a live server catalog.

For the selected entry, load only its linked guide and [the MCP workflow](references/mcp-workflow.md). Reuse the user's supplied brief and materials. Ask only for missing inputs that affect the requested result. A complete creation or revision request should proceed without an extra planning ceremony.

Preserve the requested count, language, references, product facts and unchanged elements. Translate the chosen preset into a coherent task message using the existing MCP schemas. Do not add an invented `preset_id` argument, claim a native slash command was registered, or call a nonexistent preset-resolver tool.

Distinguish browsing, creative advice, generation, revision, status and preview. Browsing or critique alone must not submit a paid task. Return actual artifacts and the existing room's state; a chosen preset is not evidence of a completed design.

## Preset-specific guides

- [Brand Design](references/brand-design.md)

Referenced files: 4 — file references are metadata, not package contents.

View saved version →

---
name: design-revision
description: 'Modify an existing Designkit design or an uploaded design reference:
  change copy or colors, make a reference-guided redesign, or adapt the layout to
  new sizes. Use the existing room for revisions; not a new unrelated creative project.'
---

# Design Revision

Use the [bundled preset catalog](references/presets.json) to match the user's requested outcome, including natural-language phrases or an alias they explicitly use. Present a short menu only when asked to browse or when the goal is genuinely ambiguous. The local catalog supplies creative workflow guidance; it is not a live server catalog.

For the selected entry, load only its linked guide and [the MCP workflow](references/mcp-workflow.md). Reuse the user's supplied brief and materials. Ask only for missing inputs that affect the requested result. A complete creation or revision request should proceed without an extra planning ceremony.

Preserve the requested count, language, references, product facts and unchanged elements. Translate the chosen preset into a coherent task message using the existing MCP schemas. Do not add an invented `preset_id` argument, claim a native slash command was registered, or call a nonexistent preset-resolver tool.

Distinguish browsing, creative advice, generation, revision, status and preview. Browsing or critique alone must not submit a paid task. Return actual artifacts and the existing room's state; a chosen preset is not evidence of a completed design.

## Preset-specific guides

- [Revision Guide](references/revision-guide.md)

Referenced files: 4 — file references are metadata, not package contents.

View saved version →

---
name: ecommerce-design
description: Create ecommerce product visuals with Designkit, including listing image
  sets, A+ or detail-page modules, white-background images, lifestyle scenes, and
  product variants. Use for new ecommerce assets; use design-revision for changes
  to an existing design.
---

# E-commerce Design

Use the [bundled preset catalog](references/presets.json) to match the user's requested outcome, including natural-language phrases or an alias they explicitly use. Present a short menu only when asked to browse or when the goal is genuinely ambiguous. The local catalog supplies creative workflow guidance; it is not a live server catalog.

For the selected entry, load only its linked guide and [the MCP workflow](references/mcp-workflow.md). Reuse the user's supplied brief and materials. Ask only for missing inputs that affect the requested result. A complete creation or revision request should proceed without an extra planning ceremony.

Preserve the requested count, language, references, product facts and unchanged elements. Translate the chosen preset into a coherent task message using the existing MCP schemas. Do not add an invented `preset_id` argument, claim a native slash command was registered, or call a nonexistent preset-resolver tool.

Distinguish browsing, creative advice, generation, revision, status and preview. Browsing or critique alone must not submit a paid task. Return actual artifacts and the existing room's state; a chosen preset is not evidence of a completed design.

## Preset-specific guides

- [Listing Images](references/listing-images.md)
- [A Plus](references/a-plus.md)

Referenced files: 5 — file references are metadata, not package contents.

View saved version →

---
name: get-started
description: Help a user who asks to set up Designkit, browse its available experts
  or presets, or choose a first marketing design workflow. Do not activate for every
  ordinary creation or revision request.
---

# Get started with Designkit

When the user wants to browse or open the visual studio, use the available `designkit_open_studio` tool (or `designkit_open_studio_panel` in a conversation). Opening the studio is read-only and does not authorize generation. Do not invent a tool if it has not appeared: use the workflow menu below instead and explain that the visual studio requires a compatible ChatGPT host and an updated Designkit connection. The sidebar/fullscreen entry is separate from the five packaged skills. If a complete creative request is already given, follow its expert workflow directly rather than forcing a trip through the studio.


Read [the workflow menu](references/workflow-menu.json) when the user asks what is available or needs help choosing a workflow. Offer the five expert entries with relevant examples instead of dumping every preset. Support natural-language choices; local aliases are not required.

- New marketplace/product assets, including A+: `ecommerce-design`.
- New promotional or social visuals: `social-campaign-design`.
- New identity concepts and branded applications: `brand-visual-design`.
- Changes to an existing design: `design-revision`.
- Product promotion, UGC-style or close-up video generation, briefs and shot plans: `video-creation`.

Follow the chosen packaged skill and its selected preset. Reuse context rather than repeating the whole briefing process. If the user has already asked for a specific design, hand over that request directly. Browsing or setup alone does not authorize a paid sample.

Use the host's normal account-connection flow if tools require login. Never ask for passwords, email codes, tokens or API keys in chat. Explain account credit use when relevant. Authentication does not authorize unrelated generation, public sharing, purchases or a change of account.

Images and videos use the same `designkit_create_task` tool, with progress and actual media from `designkit_get_artifacts`. The absence of a separate video tool does not mean video generation is unavailable. `designkit_get_profile` identifies the connected account; it is not a capability inventory.

For video requests, distinguish a concept or storyboard from an actual completed video, and follow the video expert's returned-media checks. Do not claim live competitor metrics, social-account access, automatic publishing, precise layering, manufacturing output, voice cloning or garment fitting unless an available tool actually supports the requested operation. Explain a specific missing capability and offer a relevant available workflow when helpful.

Referenced files: 2 — file references are metadata, not package contents.

View saved version →

---
name: social-campaign-design
description: Create new marketing posters, image-ad concepts, branded social posts,
  educational visual posts, and coordinated carousels with Designkit. Use for a campaign
  or topic that needs finished visual assets; use design-revision for changes to existing
  work.
---

# Marketing and Social Design

Use the [bundled preset catalog](references/presets.json) to match the user's requested outcome, including natural-language phrases or an alias they explicitly use. Present a short menu only when asked to browse or when the goal is genuinely ambiguous. The local catalog supplies creative workflow guidance; it is not a live server catalog.

For the selected entry, load only its linked guide and [the MCP workflow](references/mcp-workflow.md). Reuse the user's supplied brief and materials. Ask only for missing inputs that affect the requested result. A complete creation or revision request should proceed without an extra planning ceremony.

Preserve the requested count, language, references, product facts and unchanged elements. Translate the chosen preset into a coherent task message using the existing MCP schemas. Do not add an invented `preset_id` argument, claim a native slash command was registered, or call a nonexistent preset-resolver tool.

Distinguish browsing, creative advice, generation, revision, status and preview. Browsing or critique alone must not submit a paid task. Return actual artifacts and the existing room's state; a chosen preset is not evidence of a completed design.

## Preset-specific guides

- [Campaign Design](references/campaign-design.md)

Referenced files: 4 — file references are metadata, not package contents.

View saved version →

---
name: video-creation
description: Generate product promotion, UGC-style and close-up videos through Designkit's
  unified designkit_create_task tool, then check progress and actual video media with
  designkit_get_artifacts. Also use for video briefs, scripts and shot plans; a planning
  request alone does not authorize generation.
---

# Video creation

Designkit generates images and videos through the same `designkit_create_task` entrypoint. For a video-production request, specify video output, duration, aspect ratio and available references in the task brief, then follow `designkit_get_artifacts`. A dedicated video-generation or video-export tool is not required. `designkit_get_profile` returns account identity only; it does not enumerate capabilities or prove that upstream generation login is healthy.

Use this expert when the user wants a product promotion video, a UGC-style product video, or a product close-up. Support both a complete brief and an early idea that needs a short script or shot plan. A request for ideas or a script alone does not authorize paid video production.

Read the [bundled video presets](references/presets.json), choose the one that fits the user's intent, then read [the video workflow](references/video-workflow.md) and [the MCP workflow](references/mcp-workflow.md). Local preset aliases are conversational shorthand, not registered host commands or server-side IDs.

Reuse the supplied material, product facts, language, duration, ratio and creative choices. Ask only for missing information that affects the requested result. When the user explicitly requests a fictional product concept, do not require a nonexistent product photograph. When accurate depiction of an actual product matters, obtain usable source material.

For production, hand the brief to the existing Designkit task tools using their actual schemas. Do not invent a video-generation tool, a model route, a preset-resolver API or a dedicated voice/character parameter. Follow real server questions and account requirements. A successful submission is not a completed video.

Return the actual video artifact and available playback/download links. If the backend returns only a storyboard, image, script, question or error, identify that result accurately instead of claiming the video is finished. Do not silently substitute an image for the requested video.

Referenced files: 4 — file references are metadata, not package contents.