Dragoon0x/taste-skills / skills/reference-building/principle-tagging
principle-tagging
VerifiedTag design references by principle, not aesthetic. Build a library you can actually search. Use when saving references, organizing inspiration, or building a design library that returns useful results.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.5 KB |
SKILL.md
View on GitHub---
name: principle-tagging
description: "Tag design references by principle, not aesthetic. Build a library you can actually search. Use when saving references, organizing inspiration, or building a design library that returns useful results."
---
# Principle Tagging
Tag by what it teaches, not what it looks like.
## How to use
- `/principle-tagging` Apply principle-based tagging to references in this conversation.
## Constraints
### Tagging Rules
- MUST tag by principle: "hierarchy-through-scale-contrast" not "dark UI"
- MUST complete this sentence for every reference: "This is a good example of ___"
- NEVER tag by aesthetic alone: "gradient", "minimal", "dark mode" are useless tags
- SHOULD include one sentence about why this reference was saved
### Principle Tag Categories
- Hierarchy: hierarchy-through-scale, hierarchy-through-color, hierarchy-through-weight, hierarchy-through-space
- Space: density-with-clarity, generous-whitespace, rhythm-through-spacing, vertical-rhythm
- Type: type-as-primary-texture, type-scale-contrast, type-restraint
- Color: restrained-palette, color-as-wayfinding, neutrals-with-accent, color-meaning
- Motion: motion-as-feedback, subtle-transitions, spatial-continuity, motion-restraint
- Interaction: progressive-disclosure, direct-manipulation, keyboard-first, smart-defaults
### Anti-Patterns
- Saving references without any tag at all
- Using more than 3 tags per reference (if everything applies, nothing is specific)
- Tagging with trend names instead of principle names
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |