Content

Q: Why use Content on TypingMind?

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

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/TaewoooPark/UIForge/tree/main/skills/content. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Q: Which AI models can use Content?

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 Content?

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

Q: Is the Content AI skill free?

Yes. It is published on GitHub by TaewoooPark under the MIT license. 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

TaewoooPark

content

UIForge's microcopy layer — words are UI. Use when writing or fixing any interface text: headlines, subheads, button/CTA labels, empty states, error and loading messages, tooltips, form labels, onboarding, or marketing copy, or when copy feels generic, hypey, or "AI-written." Enforces outcome-driven labels, error/empty states that help, a hype-word blocklist, and a specificity test so every claim is checkable — the difference between a page that reads as crafted and one that reads as a template.

Overview

Publisher	TaewoooPark
Repository	`UIForge`
Skill name	`content`
Stars	8
Forks	1
Bundled files	Instructions only
License	MIT
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.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by TaewoooPark on GitHub. Read the source before you install it.

Installation

Install the Content 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/TaewoooPark/UIForge/tree/main/skills/content
Enable the skill in any chat where you want it available.

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/TaewoooPark/UIForge.git /tmp/UIForge
mkdir -p .claude/skills
cp -r /tmp/UIForge/skills/content .claude/skills/content

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

Use it in TypingMind

Enable Content 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 Content 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 Content 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.

Content — write the interface

Copy is a design surface, not filler poured in at the end. Users scan, don't read (NN/g: 79% scan; rewriting marketese to objective, concise, scannable copy tested +124% usability). And "words are UI" (Polaris) — labels, empty states, and errors are where a product feels human or feels generated.

Buttons & actions — state the outcome

Verb + object, ≤ 3 words, sentence case. Never "Submit," "Click here," or "Learn more" in isolation. "Send invoice." "Create project." "Start free trial." (Intuit measured "Send invoice" vs "Submit" at +18% CTR.)
Destructive actions = Verb + Noun ("Delete project," "Remove member") so the consequence is unmistakable — never a bare "Delete" / "OK."
One primary action per view; secondaries are quieter in both weight and word.

Errors — what happened + how to fix

Say what went wrong and what to do next, in plain words. No blame, no codes as the whole message, never "An error occurred."
Preserve the user's input. Point at the field. "That email's already in use — sign in instead?" beats "Invalid input."

Empty & loading states — never blank

Empty = why it's empty + one clear next action + a hint of the payoff. It's a first-run activation moment, not a dead end. "No projects yet. Create one to start tracking builds." + the button.
Loading: skeletons over spinners; show nothing under ~300ms (a flash reads as a glitch); consider optimistic UI for likes/CRUD.

Headlines & marketing — the specificity test

Every headline needs ≥ 1 checkable element: a number, a name, a timeframe, or a mechanism. The test: if the line could be pasted onto a competitor's site unchanged, it's a slogan — rewrite it.

"Ship faster" → "Deploy in under 90 seconds."
"Powerful analytics" → "Query 10B events without a data team."
Lead with the user's problem, not your product's adjectives (inverted pyramid — front-load the point).

The hype blocklist (ban these)

Marketese lowers measured usability and is the copy signature of AI output. Blocklist and replace:

Banned	Replace with
unlock / supercharge / elevate / revolutionize / streamline	the literal outcome + a number
seamless / seamlessly integrate	"connects to Slack, GitHub, Jira in two clicks"
world-class / enterprise-grade / game-changing / cutting-edge	a specific proof
"Trusted by thousands"	"Trusted by 4,200 engineering teams"
"In today's fast-paced world…"	delete; open on the user's problem
exclamation overuse, em-dash overuse	one clean statement

Voice & mechanics

One voice; tone flexes to the user's state (playful on success, plain and calm on errors).
Write for a ~9th-grade reading level; sentences < 25 words; active voice; concrete over abstract.
Placeholders are not labels (they vanish on focus and fail a11y) — every field gets a visible label; every icon gets a text label / aria-label.
Numbers use tabular-nums; real currency/units; consistent capitalization (pick sentence case for UI and hold it).

Hand back copy the other skills can drop in verbatim — and flag any claim you couldn't make specific, so it gets a real proof point or gets cut.

Frequently asked questions

What does the Content AI skill do?

Why use Content on TypingMind?

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

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/TaewoooPark/UIForge/tree/main/skills/content. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Content?

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 Content?

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

Is the Content AI skill free?

Yes. It is published on GitHub by TaewoooPark 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

Spec Driven Development

addyosmani

CommunityPopular

Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when drafting a PRD or requirements document with objectives and…

Release Announcement

Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.

Mode Creator

Interactively create, install, activate, and verify custom claude-mem modes, including domain-specific observation types, concept tags, optional Telegram alerts, bot setup, worker restart, and…

Version Bump

Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging,…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Content — write the interface

Buttons & actions — state the outcome

Errors — what happened + how to fix

Empty & loading states — never blank

Headlines & marketing — the specificity test

The hype blocklist (ban these)

Voice & mechanics

Frequently asked questions

Related AI Skills

Set up your own AI workspace now