Principle-Based Design Reference Tags — AI skill

When to use it

Use to curate a searchable reference collection: describe each reference, complete “This is a good example of …”, and add up to three principle-oriented tags for hierarchy, space, type, color, motion or interaction. Produces metadata suggestions, not a storage or search integration. The rejection of aesthetic tags is an opinionated heuristic; preserve project-specific taxonomy where useful. Not installed, executed or runtime-tested during discovery. GitHub stars are repository-wide, not a rating of this skill.

Compatible agents

Claude CodeCursorWindsurfOpenCodeClineCodexAiderContinue

Installation

Upstream single-skill installer: npx github:0xDragoon/taste-skills add principle-tagging. Default destination is .taste-skills/; point your agent at that directory. Alternatively copy skills/reference-building/principle-tagging/SKILL.md into a principle-tagging/SKILL.md folder in your agent’s skill directory. Review the upstream README, DISCLAIMER.md and TERMS.md first.

Review the source and instructions before installing in your agent.

License

MIT

Last checked Oct 26, 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.