Open Design Preview

Organization

feimacode

open-design-preview

Open an Open Design artifact in a live browser preview, where you can see it update as it changes, click elements to comment on them, and compare check screenshots before and after — use whenever the user asks to see, show, preview or open an Open Design artifact, or wants to comment on one visually

Overview

Publisher	feimacode
Repository	`open-design-agent-kit`
Skill name	`open-design-preview`
Stars	4
Forks	1
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by feimacode on GitHub. Read the source before you install it.

Installation

Install the Open Design Preview AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/feimacode/open-design-agent-kit/tree/main/.agents/skills/open-design-preview
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/feimacode/open-design-agent-kit/tree/main/.agents/skills/open-design-preview

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/feimacode/open-design-agent-kit.git /tmp/open-design-agent-kit
mkdir -p .claude/skills
cp -r /tmp/open-design-agent-kit/.agents/skills/open-design-preview .claude/skills/open-design-preview

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Open Design Preview in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Open Design Preview on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Open Design Preview is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Show an Open Design artifact in the browser preview.

Request: the rest of the user's message (if there is none, ask the user: "Which design should the preview show?")

How to talk to the user. Many people using Open Design don't write code, so:

Use the user's own words. If they say "artifact", "design tokens" or give a file path, use those terms back; otherwise use the plain words below.
Keep the machinery out of replies: no tool names, no ids like od:prototype:poster-hero, no internal files (.artifact.json, .comments.json, config.json), and not the words "register", "manifest", "sidecar", "entry" or "surface", unless the user used them first.
Explain a print term the first time it comes up, in one short clause, and not again.
Say where a file is the way the user would find it ("in your Open Design folder, under seed-swap-flyer"). Give a raw path only where the user can click it (Claude Code, Claude Desktop's Code tab, VS Code) or asks for it.
End each reply that finishes a step with one line on what they can do next, with at most two options ("Want it in Instagram sizes too, or is it ready to print?").

Instead of	Say
artifact, entry, registered	your design, saved
design system, active design system	your style (the first time: "a saved style: colours, fonts and spacing")
surface, skill, template, recipe	kind of design, starting layout, or nothing
workspace, output directory	your folder, your Open Design folder
bleed	print edge ("a few millimetres extra that the printer trims off")
trim size	final size
preflight findings, errors	"I checked it and fixed…", "one thing to look at:"
export	save as PDF, save as an image
inline preview, MCP App	the preview above

Work out which artifact is meant. Registered artifacts are the files under the Open Design output folder (default .open-design/) that have a .artifact.json file next to them. Use the one the request names; if it names none, use the one you made or changed most recently in this conversation. If that still doesn't settle it, call open_open_design_preview without entryPath: the preview then lists every design, and the user picks there.
Call open_open_design_preview with that entryPath.
Tell the user in one or two sentences what happened, using the tool's result: where the preview opened (or the URL to open, when it couldn't open a window), that it reloads by itself when the design changes, and that they can click Comment, then an element, to leave a comment, and Send to agent when they want you to apply them.

Frequently asked questions

What does the Open Design Preview AI skill do?

Why use Open Design Preview on TypingMind?

Because you install it once and use it with any model. Open Design Preview is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Open Design Preview in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/feimacode/open-design-agent-kit/tree/main/.agents/skills/open-design-preview. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Open Design Preview?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Open Design Preview?

As many as you like. As long as a model supports skills, you can use Open Design Preview with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Open Design Preview AI skill free?

Yes. It is published on GitHub by feimacode under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Wacli

openclaw

OrganizationPopular

Send third-party WhatsApp messages or sync/search WhatsApp history via wacli, not normal active chats.

Himalaya

Himalaya CLI for IMAP/SMTP mail: list, read, search, compose, reply, forward, copy, move, delete.

Nano Pdf

Edit PDFs with natural-language instructions using the nano-pdf CLI.

Subagent Driven Development

obra

CommunityPopular

Use when executing implementation plans with independent tasks in the current session

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Frequently asked questions

Related AI Skills

Set up your own AI workspace now