principle-tagging
Skill5 starsChanged 8 months agoMITView on GitHub
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.
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
MUST tag by principle: "hierarchy-through-scale-contrast" not "dark UI"
- Distinctive: line 18
MUST complete this sentence for every reference: "This is a good example of ___"
- Distinctive: line 19
NEVER tag by aesthetic alone: "gradient", "minimal", "dark mode" are useless tags
- Distinctive: line 20
SHOULD include one sentence about why this reference was saved
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Principle Tagging
Tag by what it teaches, not what it looks like.
How to use
/principle-taggingApply 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
In this repository38 other files it gives its agents.
- absence-auditSkill
- decision-tracingSkill
- system-deconstructionSkill
- version-archaeologySkill
- audience-translationSkill
- critique-vocabularySkill
- design-rationaleSkill
- written-critiqueSkill
- field-notesSkill
- learning-by-makingSkill
- quality-checklistSkill
- self-assessmentSkill
- flow-patternsSkill
- motion-designSkill
- timing-feedbackSkill
- constraint-evaluationSkill
- design-rankingSkill
- taste-as-strategySkill
- taste-gapSkill
- taste-vs-trendsSkill
- tradeoff-assessmentSkill
- consumption-disciplineSkill
- cross-domain-seeingSkill
- detail-observationSkill
- screenshot-surgerySkill
- visual-auditSkill
- cross-pollinationSkill
- library-architectureSkill
- daily-routinesSkill
- design-critiqueSkill
- teaching-tasteSkill
- type-as-signalSkill
- type-selectionSkill
- type-systemsSkill
- color-systemsSkill
- craft-signalsSkill
- hierarchy-principlesSkill
- spatial-rhythmSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

