Native Craft

Q: Why use Native Craft on TypingMind?

Because you install it once and use it with any model. Native Craft 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.

Q: How do I install Native Craft in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Bandersnatch0x/design-playbook/tree/main/packages/design-playbook/skills/native-craft. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Q: Which AI models can use Native Craft?

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.

Q: How many AI models can I use with Native Craft?

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

Q: Is the Native Craft AI skill free?

It is published on GitHub by Bandersnatch0x. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

Q: 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.

Q: 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.

Community

Bandersnatch0x

native-craft

Native-feel declaration for desktop apps. Use when a cross-platform desktop app (macOS+Windows) must feel indistinguishable from native. Invoked before ui-picker for native-desktop targets, not web pages.

Overview

Publisher	Bandersnatch0x
Repository	`design-playbook`
Skill name	`native-craft`
Stars	3
Forks	0
Bundled files	1
Links	Skill source Repository

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.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by Bandersnatch0x on GitHub. Read the source before you install it.

Installation

Install the Native Craft 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/Bandersnatch0x/design-playbook/tree/main/packages/design-playbook/skills/native-craft
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/Bandersnatch0x/design-playbook/tree/main/packages/design-playbook/skills/native-craft

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/Bandersnatch0x/design-playbook.git /tmp/design-playbook
mkdir -p .claude/skills
cp -r /tmp/design-playbook/packages/design-playbook/skills/native-craft .claude/skills/native-craft

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

Use it in TypingMind

Enable Native Craft 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 Native Craft 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 Native Craft 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.

native-craft

Native-feel is a Design I/O platform declaration: it fixes the render-surface seam and the native conventions before any web shell is picked. It is the native-desktop twin of craft-guard (which owns web craft). The two do not overlap.

Inspired by yetone/native-feel-skill (MIT) - see NOTICE. Depth lives in references/native-feel.md. Do not load it until this skill applies.

When to apply / skip

Apply when the target is a desktop app that must feel native on macOS + Windows (launcher, system utility, all-day productivity tool).
Skip when: one OS only (build pure native), Electron-is-fine polish bar, internal tool, cold-start < 100 ms hard, or pure web/mobile. The decision gate in references/native-feel.md rules this stack out for those shapes - say so directly.

The declaration: place the seam at the rendering surface

The cross-platform boundary is drawn at the WebView surface, nowhere else.

Below the seam - windowing, hotkeys, materials, file dialogs, tray, a11y, input methods, context menu - native, written twice in idiomatic Swift / C#. No abstraction is fast or correct enough.
Above the seam - React tree, business logic, extension API, AI orchestration - shared, written once in TS.

Test every platform decision: is this above or below the rendering surface? Below then write it twice. Above then write it once. Refuse to draw the line elsewhere.

Native-feel tenets (cite by short name when advising)

Seam at render surface - the boundary altitude where neither side can mimic the other.
Adopt the platform, don't compete - the OS draws blur, scrollbars, dark mode, focus rings better than you. "Let the OS do it" is the implementation. Custom is last resort.
Perception is performance - users feel promises kept (keystroke, frame, latency), not MB/FPS. Define the perception target before optimizing.
Cross boundaries intentionally - every IPC is a design decision: async, batched, schema-typed, observable. Never treat IPC like a function call.
Iteration loop is the product - hot-reload (~200 ms) vs native recompile (~30 s) is 150x. The cross-platform tax buys this, protect it.

Pipeline integration

native-craft runs at plan / shell, before ui-picker:

Run the decision gate (references/native-feel.md). If it rules native-feel out, stop - tell the user to use Electron / pure native / web.
Declare the seam: what is native (below) vs shared TS (above).
Declare native conventions (materials, cursor, windowing, keyboard, drag-drop) - the audit in references/native-feel.md.
Hand to ui-picker for the shared UI shell; craft-guard still applies above the seam but must defer to native conventions below it (e.g. no cursor: pointer, no web toasts, OS materials).

Done when

The decision gate has been run and native-feel is either confirmed in-scope or ruled out (with the reason stated).
The seam is declared: every platform-touching feature labeled native (below) or shared (above), no "convenient" third line.
Native conventions that block native-feel are listed for the surface in scope (cursor, context menu, materials, window controls, scroll, motion, keyboard, drag-drop).
craft-guard rules above the seam and native conventions below it are reconciled - no conflict where web idiom would telegraph "web app".

Recirculate

Observable	Declaration
App feels like a web page (cursor:pointer, web toasts, box-shadow windows)	`native-craft` conventions
Wrong seam (UI in native, or platform code in TS)	`native-craft` seam
Slow perception despite low memory	`native-craft` perception tenet
Used this stack for a one-OS / Electron-fine / <100ms app	`native-craft` decision gate (rule out)

Depth: decision gate + native-conventions audit then references/native-feel.md. Full evidence (WebView survival, IPC contract, memory truths) then original native-feel-skill (user installs separately).

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

references/native-feel.md4 KB

Frequently asked questions

What does the Native Craft AI skill do?

Why use Native Craft on TypingMind?

Because you install it once and use it with any model. Native Craft 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 Native Craft in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Bandersnatch0x/design-playbook/tree/main/packages/design-playbook/skills/native-craft. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Native Craft?

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 Native Craft?

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

Is the Native Craft AI skill free?

It is published on GitHub by Bandersnatch0x. Check the repository for licensing terms. 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

Deploy Release Test

vercel

OrganizationPopular

Validate a commit-specific Next.js preview package and manually trigger the entire Next.js deployment test suite through the test_e2e_deploy_release.yml GitHub Actions workflow. Use only when asked to…

Insight Error Page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new `errors/<slug>.mdx` page, auditing an existing one, or checking that a page matches the framework fix…

Mcp Apps Builder

**MANDATORY for ALL MCP server work** - mcp-use framework best practices and patterns. **READ THIS FIRST** before any MCP server work, including: - Creating new MCP servers - Modifying existing MCP…

Canary

Post-deploy canary monitoring. (gstack)

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

native-craft

When to apply / skip

The declaration: place the seam at the rendering surface

Native-feel tenets (cite by short name when advising)

Pipeline integration

Done when

Recirculate

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now