Design For Ai

Community

podo

design-for-ai

Design-foundations system for Claude Code built on Design for Hackers: a four-stage workflow (research, plan, mock, build) with a seeded design-DNA dealer, dual-blind review, and doctrine skills for usability, data visualisation and prototyping.

Overview

Publisher	podo
Repository	`design-agent-skills`
Skill name	`design-for-ai`
Stars	27
Forks	3
Bundled files	1
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.
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 podo on GitHub. Read the source before you install it.

Installation

Install the Design For Ai 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/podo/design-agent-skills/tree/main/skills/design-for-ai
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/podo/design-agent-skills.git /tmp/design-agent-skills
mkdir -p .claude/skills
cp -r /tmp/design-agent-skills/skills/design-for-ai .claude/skills/design-for-ai

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

Use it in TypingMind

Enable Design For Ai 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 Design For Ai 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 Design For Ai 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.

design-for-ai

Catalogue stub — full package: ryanthedev/design-for-ai

Decision tree

Is the full skill already installed? This package installs 4 skills (prototype, clarify, usability, data-viz); checking the first.
- Global: f=~/.agents/skills/prototype/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"
- Project: f=.agents/skills/prototype/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"
- installed → the skill is installed as prototype, invoke it and proceed
- pointer → go to step 2

Detect scope, then install:

bash
[ -e ~/.agents/skills/design-for-ai ] && echo "global" || echo "project"

Global:

bash
npx skills add ryanthedev/design-for-ai --skill prototype clarify usability data-viz -g -y

Project:

bash
npx skills add ryanthedev/design-for-ai --skill prototype clarify usability data-viz -y

Claude Code: send a command as a chat message starting with ! to run it without leaving the conversation.

Claude Code plugin route:


/plugin marketplace add ryanthedev/rtd-claude-inn
/plugin install design-for-ai@rtd

Heads-up

Requires: Node.js for the plugin's palette, dealer and detector scripts (scripts/*.mjs); Optional: a browser MCP so the prototype skill can render and screenshot mocks
License: MIT per plugin.json and README; no LICENSE file in the repository
Name collision: prototype is also written by emilkowalski-skill (its install or its catalogue pointer); installing both overwrites the earlier one.

Invoke after install

Claude Code plugin route (the full system): /design-for-ai:research, then /design-for-ai:plan, /design-for-ai:mock, /design-for-ai:build
Skill name: prototype — renders a self-contained HTML mock or wireframe from design tokens and page specs
Skill name: clarify — turns an underspecified design request into a confirmed brief
Skill name: usability — heuristic evaluation, UX laws, operability questions
Skill name: data-viz — chart type, truthful encoding, dashboard layout
Trigger phrases: "design for AI", "rtd design", "design research plan mock build"

What it does

Teaches the agent design vocabulary instead of default AI-looking output (cyan-on-dark heroes, uniform card grids, glassmorphism everywhere). The workflow takes any design idea from brief to a viewable, gated artifact: research facilitates the brief, plan turns it into a phased design plan, mock renders a throwaway prototype and gates on your sign-off, and build executes the plan phase by phase with build, review and commit steps. A seeded dealer picks composition, hue and signature from named references (any axis can be pinned by you), and review is dual-blind: an isolated critique plus a deterministic AI-tell detector.

The commands, agents and doctrine files come only with the Claude Code plugin route. npx skills add installs the four standalone skills; usability and data-viz are doctrine files the workflow reads, so on Claude Code they are marked as not directly invocable.

When NOT to use

Lightweight UI polish on an existing component — use taste-skill for faster, lower-overhead iteration
Accessibility-specific audits focused on ARIA, keyboard navigation, or WCAG compliance — use fixing-accessibility or wcag-audit-patterns

Bundled files

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

stub.yaml1 KB

Frequently asked questions

What does the Design For Ai AI skill do?

Why use Design For Ai on TypingMind?

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

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/podo/design-agent-skills/tree/main/skills/design-for-ai. 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 Design For Ai?

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 Design For Ai?

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

Is the Design For Ai AI skill free?

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

Frontend Slides

affaan-m

CommunityPopular

Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a…

Plan Canvas

Open plans and HTML artifacts in a local browser canvas where the human annotates elements, chats, and approves or requests changes without leaving the page. Use when presenting a plan for review, or…

Improve Codebase Architecture

mattpocock

CommunityPopular

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

Grilling

Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

design-for-ai

Decision tree

Invoke after install

What it does

When NOT to use

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now