design-taste

Name: design-taste
Author: sendaifun

162stars45forks

How to install design-taste?

sendaifun/solana-new/design-taste

$npx -y skills add sendaifun/solana-new --skill design-taste

Installs into the current project.

Summary

Design direction, judgment calls, and anti-AI-slop review for crypto UIs. Use when the user says "this looks generic", "this looks AI-generated", "anti-slop", "design judgment", "premium feel", "design direction", "what direction should this take", "make this feel more premium",

Files · 1

View on GitHub

SKILL.md

1	## Preamble (run first)
2
3	```bash
4	_TEL_TIER=$(cat ~/.superstack/config.json 2>/dev/null \| grep -o '"telemetryTier": "[^"]"' \| head -1 \| sed 's/."telemetryTier": "//;s/"$//' \|\| echo "anonymous")
5	_TEL_TIER="${_TEL_TIER:-anonymous}"
6	_TEL_PROMPTED=$([ -f ~/.superstack/.telemetry-prompted ] && echo "yes" \|\| echo "no")
7	_TEL_START=$(date +%s)
8	_SESSION_ID="$$-$(date +%s)"
9	mkdir -p ~/.superstack
10	echo "TELEMETRY: $_TEL_TIER"
11	echo "TEL_PROMPTED: $_TEL_PROMPTED"
12	if [ "$_TEL_TIER" != "off" ]; then
13	_TEL_EVENT='{"skill":"design-taste","phase":"build","event":"started","ts":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'"}'
14	echo "$_TEL_EVENT" >> ~/.superstack/telemetry.jsonl 2>/dev/null \|\| true
15	_CONVEX_URL=$(cat ~/.superstack/config.json 2>/dev/null \| grep -o '"convexUrl":"[^"]*"' \| head -1 \| cut -d'"' -f4 \|\| echo "")
16	[ -n "$_CONVEX_URL" ] && curl -s -X POST "$_CONVEX_URL/api/mutation" -H "Content-Type: application/json" -d '{"path":"telemetry:track","args":{"skill":"design-taste","phase":"build","status":"success","version":"0.2.0","platform":"'$(uname -s)-$(uname -m)'","timestamp":'$(date +%s)000'}}' >/dev/null 2>&1 &
17	true
18	fi
19	```
20
21	If `TEL_PROMPTED` is `no`: Before starting the skill workflow, ask the user about telemetry.
22	Use AskUserQuestion:
23
24	> Help superstack get better! We track which skills get used and how long they take —
25	> no code, no file paths, no PII. Change anytime in `~/.superstack/config.json`.
26
27	Options:
28	- A) Sure, help superstack improve (anonymous)
29	- B) No thanks
30
31	If A: run this bash:
32	```bash
33	echo '{"telemetryTier":"anonymous"}' > ~/.superstack/config.json
34	_TEL_TIER="anonymous"
35	touch ~/.superstack/.telemetry-prompted
36	```
37
38	If B: run this bash:
39	```bash
40	echo '{"telemetryTier":"off"}' > ~/.superstack/config.json
41	_TEL_TIER="off"
42	touch ~/.superstack/.telemetry-prompted
43	```
44
45	This only happens once. If `TEL_PROMPTED` is `yes`, skip this entirely and proceed to the skill workflow.
46
47	> Wrong skill? See [SKILL_ROUTER.md](../../SKILL_ROUTER.md) for all available skills.
48
49	# Design Taste
50
51	> Design judgment patterns adapted from curated design system references, independent UI craft writing, and observational analysis of high-craft products across SaaS, fintech, trading, and consumer.
52
53	The taste layer that sits between brand selection and mechanical implementation. This skill answers: "Given the constraints, what should this actually look like?" It catches generic AI output, makes judgment calls about density and layout, and defines what polished, intentional interfaces feel like.
54
55	`frontend-design-guidelines` tells you how to build it right. `brand-design` tells you how to brand it. This skill tells you what design direction to take.
56
57	## Authority Model
58
59	- `brand-design` → palette/typography selection → writes `brand.md`
60	- This skill → design direction, judgment calls, anti-slop review
61	- `frontend-design-guidelines` → mechanical correctness (a11y, forms, states) → invokes this skill when direction is needed
62	- `page-load-animations` → framer-motion implementation recipes
63
64	`frontend-design-guidelines` delegates direction questions TO this skill. This skill does NOT invoke `frontend-design-guidelines`.
65
66	Conflict resolution with brand.md: If `brand-design` chose Inter as the typeface, this skill does NOT ban Inter. It ensures Inter is used with intentional weight, tracking, and hierarchy — not as a lazy default. Anti-slop rules apply to thoughtless defaults, not deliberate brand choices.
67
68	## When to Fire This Skill
69
70	- The user says "this looks generic" or "this feels AI-generated"
71	- The user asks what direction a page or component should take
72	- The user wants something to feel "more premium" or "less generic"
73	- Building a new page and the aesthetic direction is unclear
74	- Reviewing existing UI for AI-slop patterns
75	- The user references a design direction ("make it warm and premium", "dense trading feel")
76
77	Do NOT fire on "make this look good", "polish this", or "design this page" — those belong to `frontend-design-guidelines`.
78
79	## Workflow
80
81	### Step 0: Read brand.md if present
82	Understand the existing aesthetic direction. Respect it — don't override palette or typeface choices.
83
84	### Step 1: Identify which reference is relevant
85	- Checking for generic AI patterns → [ref

People who liked this also viewed

6 picks

Type

design-taste

162stars45forks

View on GitHub

How to install design-taste?

sendaifun/solana-new/design-taste

$npx -y skills add sendaifun/solana-new --skill design-taste

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	## Preamble (run first)
2
3	```bash
4	_TEL_TIER=$(cat ~/.superstack/config.json 2>/dev/null \| grep -o '"telemetryTier": "[^"]"' \| head -1 \| sed 's/."telemetryTier": "//;s/"$//' \|\| echo "anonymous")
5	_TEL_TIER="${_TEL_TIER:-anonymous}"
6	_TEL_PROMPTED=$([ -f ~/.superstack/.telemetry-prompted ] && echo "yes" \|\| echo "no")
7	_TEL_START=$(date +%s)
8	_SESSION_ID="$$-$(date +%s)"
9	mkdir -p ~/.superstack
10	echo "TELEMETRY: $_TEL_TIER"
11	echo "TEL_PROMPTED: $_TEL_PROMPTED"
12	if [ "$_TEL_TIER" != "off" ]; then
13	_TEL_EVENT='{"skill":"design-taste","phase":"build","event":"started","ts":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'"}'
14	echo "$_TEL_EVENT" >> ~/.superstack/telemetry.jsonl 2>/dev/null \|\| true
15	_CONVEX_URL=$(cat ~/.superstack/config.json 2>/dev/null \| grep -o '"convexUrl":"[^"]*"' \| head -1 \| cut -d'"' -f4 \|\| echo "")
16	[ -n "$_CONVEX_URL" ] && curl -s -X POST "$_CONVEX_URL/api/mutation" -H "Content-Type: application/json" -d '{"path":"telemetry:track","args":{"skill":"design-taste","phase":"build","status":"success","version":"0.2.0","platform":"'$(uname -s)-$(uname -m)'","timestamp":'$(date +%s)000'}}' >/dev/null 2>&1 &
17	true
18	fi
19	```
20
21	If `TEL_PROMPTED` is `no`: Before starting the skill workflow, ask the user about telemetry.
22	Use AskUserQuestion:
23
24	> Help superstack get better! We track which skills get used and how long they take —
25	> no code, no file paths, no PII. Change anytime in `~/.superstack/config.json`.
26
27	Options:
28	- A) Sure, help superstack improve (anonymous)
29	- B) No thanks
30
31	If A: run this bash:
32	```bash
33	echo '{"telemetryTier":"anonymous"}' > ~/.superstack/config.json
34	_TEL_TIER="anonymous"
35	touch ~/.superstack/.telemetry-prompted
36	```
37
38	If B: run this bash:
39	```bash
40	echo '{"telemetryTier":"off"}' > ~/.superstack/config.json
41	_TEL_TIER="off"
42	touch ~/.superstack/.telemetry-prompted
43	```
44
45	This only happens once. If `TEL_PROMPTED` is `yes`, skip this entirely and proceed to the skill workflow.
46
47	> Wrong skill? See [SKILL_ROUTER.md](../../SKILL_ROUTER.md) for all available skills.
48
49	# Design Taste
50
51	> Design judgment patterns adapted from curated design system references, independent UI craft writing, and observational analysis of high-craft products across SaaS, fintech, trading, and consumer.
52
53	The taste layer that sits between brand selection and mechanical implementation. This skill answers: "Given the constraints, what should this actually look like?" It catches generic AI output, makes judgment calls about density and layout, and defines what polished, intentional interfaces feel like.
54
55	`frontend-design-guidelines` tells you how to build it right. `brand-design` tells you how to brand it. This skill tells you what design direction to take.
56
57	## Authority Model
58
59	- `brand-design` → palette/typography selection → writes `brand.md`
60	- This skill → design direction, judgment calls, anti-slop review
61	- `frontend-design-guidelines` → mechanical correctness (a11y, forms, states) → invokes this skill when direction is needed
62	- `page-load-animations` → framer-motion implementation recipes
63
64	`frontend-design-guidelines` delegates direction questions TO this skill. This skill does NOT invoke `frontend-design-guidelines`.
65
66	Conflict resolution with brand.md: If `brand-design` chose Inter as the typeface, this skill does NOT ban Inter. It ensures Inter is used with intentional weight, tracking, and hierarchy — not as a lazy default. Anti-slop rules apply to thoughtless defaults, not deliberate brand choices.
67
68	## When to Fire This Skill
69
70	- The user says "this looks generic" or "this feels AI-generated"
71	- The user asks what direction a page or component should take
72	- The user wants something to feel "more premium" or "less generic"
73	- Building a new page and the aesthetic direction is unclear
74	- Reviewing existing UI for AI-slop patterns
75	- The user references a design direction ("make it warm and premium", "dense trading feel")
76
77	Do NOT fire on "make this look good", "polish this", or "design this page" — those belong to `frontend-design-guidelines`.
78
79	## Workflow
80
81	### Step 0: Read brand.md if present
82	Understand the existing aesthetic direction. Respect it — don't override palette or typeface choices.
83
84	### Step 1: Identify which reference is relevant
85	- Checking for generic AI patterns → [ref

People who liked this also viewed

6 picks

Type