Design Rationale — Designer Skills — AI skill

When to use it

Use for controversial UI decisions, departures from a design system or handoff rationale. Requires supplied research and constraints; it cannot generate evidence or validate a decision by itself. Intended for written rationale, not live design negotiation. No runtime testing was performed.

Compatible agents

Claude CodeGemini CLI

Installation

In Claude Code run /plugin marketplace add Owl-Listener/designer-skills, then /plugin install designer-toolkit@designer-skills. This includes design-rationale. See the upstream README for Gemini CLI setup.

Review the source and instructions before installing in your agent.

License

MIT

Last checked Oct 21, 2026.

Pair this skill with a visual reference

A skill guides how your agent works; a design reference shows the direction you want. Choose an example for a specific job, such as the headline hierarchy or form layout, and keep your project's existing design rules explicit.

Start with design references you can inspect, then use our guide to briefing an AI coding agent to turn observations into requirements. If you need implementation components, compare UI libraries for your stack.

These pages are public. Browsing a skill does not install it, and TastefulKit's design-reference MCP tools do not search the AI-skill directory.