ui-ux-master 1.2.0 → 1.5.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +170 -182
- package/SKILL.md +89 -47
- package/docs/package-publishing.md +84 -0
- package/index.cjs +39 -0
- package/index.d.ts +17 -0
- package/index.mjs +30 -0
- package/package.json +86 -11
- package/references/brand-method-card-based-discovery.md +285 -0
- package/references/brand-method-conversion-simplicity.md +276 -0
- package/references/brand-method-ecosystem-bundling.md +263 -0
- package/references/brand-method-editorial-brand-world.md +265 -0
- package/references/brand-method-enterprise-trust-hub.md +298 -0
- package/references/brand-method-playful-familiarity.md +284 -0
- package/references/brand-method-premium-restraint.md +270 -0
- package/references/brand-method-product-cinema.md +258 -0
- package/references/brand-method-technical-authority.md +290 -0
- package/references/brand-method-utility-command-center.md +278 -0
- package/references/color-psychology-branding.md +286 -0
- package/references/color-scale-system.md +347 -0
- package/references/competitive-landscape.md +32 -6
- package/references/design-discovery-protocol.md +171 -0
- package/references/design-system-schema.md +407 -0
- package/references/industry-reasoning-rules.md +504 -0
- package/references/landing-page-patterns.md +327 -0
- package/references/output-quality-gates.md +246 -0
- package/references/tech-stack-guidelines.md +636 -0
- package/references/ui-styles-catalog.md +552 -0
- package/references/visual-directions.md +362 -0
- package/tests/install-smoke.test.mjs +93 -12
|
@@ -0,0 +1,298 @@
|
|
|
1
|
+
# Brand Method: Enterprise Trust Hub
|
|
2
|
+
|
|
3
|
+
Use this skill when building for B2B SaaS, enterprise software, infrastructure, finance, healthcare, industrial, or any context where the buyer is a professional making a high-stakes purchasing decision.
|
|
4
|
+
|
|
5
|
+
Reference brands: Microsoft, Cisco, Oracle, SAP, IBM, Siemens, Salesforce, GE, Goldman Sachs, JPMorgan Chase, Philips, HSBC, Bank of America.
|
|
6
|
+
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
## When to Apply This Method
|
|
10
|
+
|
|
11
|
+
Apply Enterprise Trust Hub when:
|
|
12
|
+
- The buyer is a professional: IT decision-maker, CFO, compliance officer, procurement team.
|
|
13
|
+
- The sales cycle is long (weeks to months), involving multiple stakeholders.
|
|
14
|
+
- Proof of security, compliance, reliability, and ROI must be on the page.
|
|
15
|
+
- The primary CTA is "Contact Sales", "Request Demo", or "Get Pricing".
|
|
16
|
+
- The product is B2B software, infrastructure, finance, healthcare systems, or industrial.
|
|
17
|
+
|
|
18
|
+
Do not apply when:
|
|
19
|
+
- The buyer is a consumer (use Product Cinema, Playful Familiarity, or Conversion Simplicity).
|
|
20
|
+
- Brand storytelling is the primary goal (use Editorial Brand World).
|
|
21
|
+
- The product is simple and direct sign-up (use Conversion Simplicity).
|
|
22
|
+
|
|
23
|
+
---
|
|
24
|
+
|
|
25
|
+
## Layout Structure
|
|
26
|
+
|
|
27
|
+
### Header
|
|
28
|
+
- Logo left.
|
|
29
|
+
- Mega-navigation: audience/role, product/solution, industry, resources, pricing (if available), login, primary CTA ("Get Demo" or "Contact Sales").
|
|
30
|
+
- Mega-nav dropdowns: clean grids of links with icons, grouped by category.
|
|
31
|
+
- Sticky on scroll.
|
|
32
|
+
|
|
33
|
+
### Homepage Structure (in order)
|
|
34
|
+
1. **Hero** — clear value proposition (what it does + for whom + key outcome). Primary CTA above fold.
|
|
35
|
+
2. **Social proof bar** — 5-8 recognizable customer logos, muted/grayscale.
|
|
36
|
+
3. **Product capability overview** — 3-4 card/icon blocks, one capability each.
|
|
37
|
+
4. **Solution or audience routing** — "For IT Teams | For Finance | For Operations" segmentation.
|
|
38
|
+
5. **Feature deep-dive** — alternating image/text blocks, one feature per section.
|
|
39
|
+
6. **Proof section** — metric cards ("40% faster", "99.99% uptime"), case study card(s).
|
|
40
|
+
7. **Security / compliance** — badges, certifications, brief copy (SOC2, ISO 27001, HIPAA, GDPR).
|
|
41
|
+
8. **CTA section** — "Start Free Trial" or "Talk to Sales", with objection-handling copy.
|
|
42
|
+
9. **Resource section** — whitepaper, webinar, or docs teaser.
|
|
43
|
+
|
|
44
|
+
### Solution / Product Pages
|
|
45
|
+
- Clear breadcrumb.
|
|
46
|
+
- Hero: product name, value prop, screenshot/diagram, CTA.
|
|
47
|
+
- Feature sections: alternating layout, screenshot or diagram + explanation.
|
|
48
|
+
- Integration section: compatible tools/platforms logos.
|
|
49
|
+
- Pricing teaser (or full pricing page link).
|
|
50
|
+
- Case study or customer quote.
|
|
51
|
+
- Related products/solutions.
|
|
52
|
+
- Footer CTA.
|
|
53
|
+
|
|
54
|
+
### Navigation
|
|
55
|
+
- Mega-navigation with grouped links.
|
|
56
|
+
- Role/industry segmentation in nav or above nav.
|
|
57
|
+
- Search available in nav.
|
|
58
|
+
- Mobile: hamburger → accordion mega-nav.
|
|
59
|
+
|
|
60
|
+
---
|
|
61
|
+
|
|
62
|
+
## Color Scheme
|
|
63
|
+
|
|
64
|
+
### Primary Palette by Sub-category
|
|
65
|
+
|
|
66
|
+
**Enterprise Tech / SaaS (Microsoft, Salesforce, IBM)**
|
|
67
|
+
- Background: `#FFFFFF`
|
|
68
|
+
- Primary: `#0078D4` (Microsoft blue), `#00A1E0` (Salesforce), `#1F70C1` (IBM)
|
|
69
|
+
- Surface: `#F4F6F9`
|
|
70
|
+
- Text: `#323130` or `#1A1A1A`
|
|
71
|
+
- Secondary text: `#605E5C`
|
|
72
|
+
- CTA: primary color as background, white text
|
|
73
|
+
- Hover: darken 10%
|
|
74
|
+
- Border: `#EDEBE9`
|
|
75
|
+
- Success: `#107C10`
|
|
76
|
+
- Warning: `#D83B01`
|
|
77
|
+
- Error: `#A4262C`
|
|
78
|
+
|
|
79
|
+
**Finance / Banking (Goldman Sachs, JPMorgan, HSBC)**
|
|
80
|
+
- Background: `#FFFFFF`
|
|
81
|
+
- Primary: Navy `#003366` or `#002D72`
|
|
82
|
+
- Gold accent: `#C8A96E` or `#B8860B` (sparingly, for premium signals)
|
|
83
|
+
- Surface: `#F7F8FA`
|
|
84
|
+
- Text: `#1A1A2E`
|
|
85
|
+
- CTA: navy background, white text
|
|
86
|
+
- Secondary CTA: outlined navy
|
|
87
|
+
|
|
88
|
+
**Healthcare / Pharma (Philips, 3M)**
|
|
89
|
+
- Background: `#FFFFFF`
|
|
90
|
+
- Primary: `#0072CE` (calm blue) or `#00A7B5` (teal)
|
|
91
|
+
- Surface: `#F0F7FF`
|
|
92
|
+
- Text: `#1A2B3C`
|
|
93
|
+
- Accent for health: teal, green — calming, clinical trust
|
|
94
|
+
|
|
95
|
+
**Industrial / Infrastructure (Siemens, GE)**
|
|
96
|
+
- Background: `#FFFFFF`
|
|
97
|
+
- Primary: `#009999` (Siemens teal) or `#0067B1` (GE blue)
|
|
98
|
+
- Surface: `#F5F5F5`
|
|
99
|
+
- Text: `#333333`
|
|
100
|
+
- Accent: brand teal or blue, never decorative
|
|
101
|
+
|
|
102
|
+
### Rules
|
|
103
|
+
- Conservative palette: blue, white, and neutral grays carry enterprise trust.
|
|
104
|
+
- Never use bright orange, yellow, or green as primary CTA in a finance or healthcare context.
|
|
105
|
+
- Security section: dark background with trust icons is acceptable and expected.
|
|
106
|
+
- Proof metrics: use brand color for the number, neutral for the description.
|
|
107
|
+
|
|
108
|
+
---
|
|
109
|
+
|
|
110
|
+
## Typography
|
|
111
|
+
|
|
112
|
+
### Scale
|
|
113
|
+
| Role | Size | Weight | Notes |
|
|
114
|
+
|---|---|---|---|
|
|
115
|
+
| H1 / hero headline | 36-52px | 600-700 | Clear value prop |
|
|
116
|
+
| H2 / section title | 26-36px | 600-700 | |
|
|
117
|
+
| H3 / feature title | 18-22px | 600 | |
|
|
118
|
+
| Body | 15-17px | 400 | 1.6-1.7 line-height |
|
|
119
|
+
| Proof metric | 40-60px | 700-800 | Tabular numerals |
|
|
120
|
+
| Metric label | 14-16px | 400 | Below the number |
|
|
121
|
+
| CTA | 14-16px | 600 | |
|
|
122
|
+
| Navigation | 14px | 500 | |
|
|
123
|
+
| Badge / certification | 11-12px | 600 | All-caps or bold |
|
|
124
|
+
|
|
125
|
+
### Font Pairings
|
|
126
|
+
| Context | Font |
|
|
127
|
+
|---|---|
|
|
128
|
+
| Enterprise SaaS | Segoe UI (Microsoft), Salesforce Sans, or Inter |
|
|
129
|
+
| Finance | Georgia (editorial), Helvetica Neue, or IBM Plex Sans |
|
|
130
|
+
| Healthcare | Source Sans Pro, Open Sans, Roboto |
|
|
131
|
+
| Industrial | Roboto, Noto Sans, or system font |
|
|
132
|
+
|
|
133
|
+
### Rules
|
|
134
|
+
- Avoid decorative or display typefaces — clarity and authority over style.
|
|
135
|
+
- Body text line-height must be ≥ 1.6 — enterprise docs are information-dense.
|
|
136
|
+
- Metric numbers: use `font-variant-numeric: tabular-nums` and a display weight.
|
|
137
|
+
|
|
138
|
+
---
|
|
139
|
+
|
|
140
|
+
## Spacing System
|
|
141
|
+
|
|
142
|
+
| Token | Value | Use |
|
|
143
|
+
|---|---|---|
|
|
144
|
+
| `--space-xs` | 4px | Icon gaps |
|
|
145
|
+
| `--space-sm` | 8px | Inline elements |
|
|
146
|
+
| `--space-md` | 16px | Card padding, form inputs |
|
|
147
|
+
| `--space-lg` | 24-32px | Section inner padding |
|
|
148
|
+
| `--space-xl` | 48-64px | Between major sections |
|
|
149
|
+
| `--space-2xl` | 80-96px | Hero and CTA sections |
|
|
150
|
+
|
|
151
|
+
- Enterprise pages are information-dense by design — tighter than consumer pages.
|
|
152
|
+
- Never so dense that scanning is difficult: group related content, use dividers or cards.
|
|
153
|
+
- Card padding: 24-32px. Cards should feel substantial, not cramped.
|
|
154
|
+
|
|
155
|
+
---
|
|
156
|
+
|
|
157
|
+
## Motion and Interaction
|
|
158
|
+
|
|
159
|
+
### Principles
|
|
160
|
+
- Animation is minimal and purposeful — this is a professional context, not entertainment.
|
|
161
|
+
- Proof metric numbers can count up on scroll: `0 → 40%`, duration 800ms, ease-out.
|
|
162
|
+
- Feature illustrations: subtle fade-in on scroll.
|
|
163
|
+
- No parallax, no cinematic scrolling, no custom cursors.
|
|
164
|
+
|
|
165
|
+
### Key Component States
|
|
166
|
+
| Component | States |
|
|
167
|
+
|---|---|
|
|
168
|
+
| Primary CTA | Default, hover (darken 8%), active (darken 12%), focus (ring), loading, disabled |
|
|
169
|
+
| Secondary CTA | Default (outlined), hover (fill lightly), focus |
|
|
170
|
+
| Accordion / FAQ | Collapsed, expanded (smooth 200ms height transition), focus |
|
|
171
|
+
| Mega-nav dropdown | Closed, opening (200ms fade + translate), open, closing |
|
|
172
|
+
| Form input | Default, focused (border color), filled, error (red border + message), success |
|
|
173
|
+
| Customer logo | Default (grayscale 50%), hover (full color 100%) |
|
|
174
|
+
|
|
175
|
+
### Form UX
|
|
176
|
+
- Label above input always (not inside as placeholder-only).
|
|
177
|
+
- Inline validation: only after user leaves the field (blur), not on keystroke.
|
|
178
|
+
- Submit: clear loading state, success message, error recovery.
|
|
179
|
+
- Required fields: marked with `*` and explained ("* Required").
|
|
180
|
+
|
|
181
|
+
---
|
|
182
|
+
|
|
183
|
+
## Responsive Behavior
|
|
184
|
+
|
|
185
|
+
| Breakpoint | Key changes |
|
|
186
|
+
|---|---|
|
|
187
|
+
| Mobile 375px | Single column. Mega-nav → hamburger + accordion. Proof metrics stack. CTA full-width. Feature sections stack vertically. |
|
|
188
|
+
| Tablet 768px | 2-column feature sections. Mega-nav collapses. |
|
|
189
|
+
| Desktop 1024px | Full mega-nav. 3-column capability grid. Alternating feature layout. |
|
|
190
|
+
| Wide 1440px+ | Content max-width 1200-1440px centered. No full-bleed backgrounds except CTA/footer. |
|
|
191
|
+
|
|
192
|
+
- Mobile: mega-nav must work as well as desktop — executives use phones.
|
|
193
|
+
- Mobile: proof metrics still prominent — enterprise buyers research on mobile.
|
|
194
|
+
|
|
195
|
+
---
|
|
196
|
+
|
|
197
|
+
## Accessibility Requirements
|
|
198
|
+
|
|
199
|
+
- Mega-nav: keyboard-navigable with arrow keys within mega-nav dropdowns. `Escape` closes. Focus returns to trigger.
|
|
200
|
+
- Proof metrics: `aria-label="40 percent faster"` — not just "40%".
|
|
201
|
+
- Customer logos: `alt="[Company Name] logo"` or `aria-label` if CSS background.
|
|
202
|
+
- Form: every input has a `<label>`. Error messages are programmatically associated (`aria-describedby`). Required fields marked with `aria-required="true"`.
|
|
203
|
+
- Accordion: `aria-expanded`, `aria-controls`, button as trigger.
|
|
204
|
+
- Tables (pricing, comparison): use `<th scope="col/row">`, proper header association.
|
|
205
|
+
- Color: never use color alone to communicate status — pair with icon or text.
|
|
206
|
+
- PDF downloads: ensure PDFs are tagged and accessible (mention this in handoff).
|
|
207
|
+
- Security / certification badge images: `alt` text names the certification.
|
|
208
|
+
- All text: minimum 4.5:1 contrast.
|
|
209
|
+
|
|
210
|
+
---
|
|
211
|
+
|
|
212
|
+
## UX Principles for This Method
|
|
213
|
+
|
|
214
|
+
1. **Route by role, not by product.** Enterprise buyers think "I'm a CTO" not "I want product SKU 7."
|
|
215
|
+
2. **Proof before promise.** Show the customer logos, the metrics, the case study early. Enterprise buyers are skeptical.
|
|
216
|
+
3. **Make complex simple.** Diagrams, progressive disclosure, comparison tables — never walls of feature bullets.
|
|
217
|
+
4. **Respect the sales cycle.** Provide self-serve research paths (docs, pricing, case studies) AND demo/contact paths.
|
|
218
|
+
5. **Security and compliance are features.** They belong on the product page, not buried in footer.
|
|
219
|
+
6. **Trust is earned incrementally.** Layer proof throughout the page: logos → metric → case study → cert → CTA.
|
|
220
|
+
7. **Forms are gates, not walls.** Ask for minimum information at each stage. Qualify progressively.
|
|
221
|
+
|
|
222
|
+
---
|
|
223
|
+
|
|
224
|
+
## Component Specs
|
|
225
|
+
|
|
226
|
+
### Proof Metric Card
|
|
227
|
+
```
|
|
228
|
+
Background: white or very light surface
|
|
229
|
+
Border: 1px solid var(--border) or none
|
|
230
|
+
Padding: 32px 24px
|
|
231
|
+
Metric number: 48-60px, brand primary, font-weight 700
|
|
232
|
+
Label: 14-16px, text-secondary, margin-top 8px
|
|
233
|
+
Optional icon: 24-32px, muted brand color, above number
|
|
234
|
+
Border-radius: 8px
|
|
235
|
+
```
|
|
236
|
+
|
|
237
|
+
### Customer Logo Strip
|
|
238
|
+
```
|
|
239
|
+
Display: flex, gap 32-48px, align-items: center, flex-wrap: wrap
|
|
240
|
+
Logo image: grayscale filter 80-100%, opacity 0.5-0.6
|
|
241
|
+
Logo image hover: filter none, opacity 1.0, transition 200ms
|
|
242
|
+
Max-height per logo: 32-40px
|
|
243
|
+
Heading above: "Trusted by teams at" in muted text-secondary
|
|
244
|
+
```
|
|
245
|
+
|
|
246
|
+
### Mega-Navigation Dropdown
|
|
247
|
+
```
|
|
248
|
+
Position: absolute, full-width or column-aligned below nav
|
|
249
|
+
Background: white
|
|
250
|
+
Shadow: 0 8px 24px rgba(0,0,0,0.08)
|
|
251
|
+
Padding: 24-32px
|
|
252
|
+
Grid: 3-4 columns of grouped links
|
|
253
|
+
Link groups: heading (11px, all-caps, text-muted), links (14px, weight 400)
|
|
254
|
+
Icon per link: 16-20px, brand color
|
|
255
|
+
Open/close: aria-expanded, transition 200ms opacity + translateY
|
|
256
|
+
```
|
|
257
|
+
|
|
258
|
+
### CTA Section
|
|
259
|
+
```
|
|
260
|
+
Background: brand primary or dark surface
|
|
261
|
+
Padding: 64-80px
|
|
262
|
+
H2: 28-36px, white/contrasting
|
|
263
|
+
Sub-copy: 16-18px, secondary white
|
|
264
|
+
CTA button: white background, brand-colored text, or outlined
|
|
265
|
+
Secondary CTA: outlined, white border, white text
|
|
266
|
+
Spacing between CTAs: 16px
|
|
267
|
+
```
|
|
268
|
+
|
|
269
|
+
---
|
|
270
|
+
|
|
271
|
+
## Anti-Patterns to Avoid
|
|
272
|
+
|
|
273
|
+
- Do not bury the CTA below the fold without any CTA in the hero.
|
|
274
|
+
- Do not use vague value propositions ("We make business better") — be specific about what, for whom, and the outcome.
|
|
275
|
+
- Do not require registration to read case studies or pricing pages.
|
|
276
|
+
- Do not show a wall of features without diagrams, screenshots, or social proof.
|
|
277
|
+
- Do not use stock photography of people shaking hands or smiling at laptops — use real product screenshots.
|
|
278
|
+
- Do not hide pricing — at minimum, acknowledge it exists and offer a pricing page.
|
|
279
|
+
- Do not use small fonts for compliance/security copy — it must be readable.
|
|
280
|
+
- Do not mix consumer design patterns (countdown timers, emoji-heavy copy) in an enterprise context.
|
|
281
|
+
- Do not use `color: red` for all error states — also provide icon and text.
|
|
282
|
+
|
|
283
|
+
---
|
|
284
|
+
|
|
285
|
+
## QA Checklist
|
|
286
|
+
|
|
287
|
+
- [ ] Hero value proposition is clear in 5 seconds without reading body text.
|
|
288
|
+
- [ ] Customer logos visible above fold or within first scroll.
|
|
289
|
+
- [ ] At least one proof metric with source/context.
|
|
290
|
+
- [ ] Mega-nav keyboard navigable (arrow keys, Escape closes).
|
|
291
|
+
- [ ] All form inputs have visible labels.
|
|
292
|
+
- [ ] Form error messages are programmatically associated with inputs.
|
|
293
|
+
- [ ] Security / compliance section present with specific certifications.
|
|
294
|
+
- [ ] Mobile: mega-nav works as hamburger accordion.
|
|
295
|
+
- [ ] Mobile: CTAs accessible without horizontal scroll.
|
|
296
|
+
- [ ] All text meets 4.5:1 contrast.
|
|
297
|
+
- [ ] Pricing is findable within 2 clicks or clearly explained.
|
|
298
|
+
- [ ] Page loads LCP ≤ 2.5s (enterprise buyers measure performance).
|
|
@@ -0,0 +1,284 @@
|
|
|
1
|
+
# Brand Method: Playful Familiarity
|
|
2
|
+
|
|
3
|
+
Use this skill when building for food and beverage retail, family brands, toys, children's platforms, casual consumer apps, or any context where the primary emotion is delight, comfort, and ease.
|
|
4
|
+
|
|
5
|
+
Reference brands: McDonald's, KFC, Burger King, Domino's, Starbucks, LEGO, Nintendo, Coca-Cola, Nestlé, Colgate, Costco.
|
|
6
|
+
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
## When to Apply This Method
|
|
10
|
+
|
|
11
|
+
Apply Playful Familiarity when:
|
|
12
|
+
- The brand uses friendly, familiar, or joyful tone as a key differentiator.
|
|
13
|
+
- The audience is broad: families, children, casual users, all age groups.
|
|
14
|
+
- The primary task is order, find, or buy — but the experience should feel fun, not cold.
|
|
15
|
+
- Brand characters, mascots, or iconic imagery are key recognition assets.
|
|
16
|
+
|
|
17
|
+
Do not apply when:
|
|
18
|
+
- The brand is luxury or premium (use Premium Restraint).
|
|
19
|
+
- The product is enterprise software or professional tools (use Enterprise Trust Hub or Technical Authority).
|
|
20
|
+
- The primary goal is brand storytelling without task completion (use Editorial Brand World).
|
|
21
|
+
|
|
22
|
+
---
|
|
23
|
+
|
|
24
|
+
## Layout Structure
|
|
25
|
+
|
|
26
|
+
### Hero
|
|
27
|
+
- Brand imagery dominant: food photography, character/mascot, product in context.
|
|
28
|
+
- Warm, bright, inviting — the hero should make the user feel good immediately.
|
|
29
|
+
- Headline: short, friendly, direct. "Order Now." "What are you craving?" "Start Building."
|
|
30
|
+
- CTA: bold, large, visible — "Order Now", "Find a Store", "Shop Now."
|
|
31
|
+
- Promotional strip: thin banner above or below hero with current offer.
|
|
32
|
+
|
|
33
|
+
### Navigation
|
|
34
|
+
- Clear, simple, icons + labels.
|
|
35
|
+
- Categories visible in nav or below hero (not hidden in hamburger on desktop).
|
|
36
|
+
- Key CTAs in nav: "Order Now", "Delivery", "Store Finder."
|
|
37
|
+
- Mobile: bottom navigation bar (food ordering / consumer apps) OR clear hamburger.
|
|
38
|
+
|
|
39
|
+
### Homepage Sections (in order)
|
|
40
|
+
1. **Hero** — brand world, CTA, current promotion.
|
|
41
|
+
2. **Featured offers / menu highlights** — 3-4 featured items with prices, large photos.
|
|
42
|
+
3. **Order method selection** — Delivery / Takeaway / Dine-in (food brands).
|
|
43
|
+
4. **Brand story snippet** — 1-2 paragraphs or a visual story block, friendly tone.
|
|
44
|
+
5. **Loyalty / rewards** — app or rewards program teaser.
|
|
45
|
+
6. **Location finder** — map or zip code input.
|
|
46
|
+
|
|
47
|
+
### Menu / Product Page
|
|
48
|
+
- Large food photography or product imagery.
|
|
49
|
+
- Clear product name, price, description (friendly tone).
|
|
50
|
+
- Customization options (size, extras, add-ons): large touch targets, visible choices.
|
|
51
|
+
- "Add to Order" / "Add to Cart": prominent, colored, full-width on mobile.
|
|
52
|
+
- Allergen info: accessible, visible, not buried.
|
|
53
|
+
|
|
54
|
+
---
|
|
55
|
+
|
|
56
|
+
## Color Scheme
|
|
57
|
+
|
|
58
|
+
### Palette Archetypes
|
|
59
|
+
|
|
60
|
+
**Fast Food (McDonald's, KFC, Burger King)**
|
|
61
|
+
- McDonald's: `#FFC72C` (yellow) + `#DA291C` (red) on white
|
|
62
|
+
- KFC: `#E4002B` (red) + `#000000` on white
|
|
63
|
+
- Burger King: `#E8611A` (orange/red) + `#502314` (brown) + cream `#F5F0E5`
|
|
64
|
+
- Rule: high-energy primaries, white background, CTA uses the brightest brand color.
|
|
65
|
+
|
|
66
|
+
**Coffee / Comfort (Starbucks)**
|
|
67
|
+
- Primary: `#00704A` (green)
|
|
68
|
+
- Background: `#FFFFFF` or `#F9F4EE` (warm cream)
|
|
69
|
+
- Accent: `#CBA258` (gold, reward tier)
|
|
70
|
+
- Text: `#1E3932` (deep green)
|
|
71
|
+
|
|
72
|
+
**Family Toys (LEGO)**
|
|
73
|
+
- Primary: `#F5CC0A` (LEGO yellow) + `#D91F26` (red) + `#006CB7` (blue)
|
|
74
|
+
- Background: `#FFFFFF`
|
|
75
|
+
- Text: `#1A1A1A`
|
|
76
|
+
- Use multiple brand colors in theme/product routing — each theme has its own color.
|
|
77
|
+
|
|
78
|
+
**Family Food Brands (Nestlé, Colgate)**
|
|
79
|
+
- Background: `#FFFFFF`
|
|
80
|
+
- Primary: brand blue or red
|
|
81
|
+
- Surface: light pastel of primary color at 10-20% opacity
|
|
82
|
+
- Text: `#1A1A1A`
|
|
83
|
+
- Warm accent: yellow or green for health cues
|
|
84
|
+
|
|
85
|
+
**Gaming / Family Entertainment (Nintendo)**
|
|
86
|
+
- Primary: `#E4000F` (red)
|
|
87
|
+
- Background: `#FFFFFF`
|
|
88
|
+
- Game character/art provides additional color
|
|
89
|
+
- Text: `#1A1A1A`
|
|
90
|
+
|
|
91
|
+
### Rules
|
|
92
|
+
- Colors must be high-energy and identifiable — the brand color is the experience.
|
|
93
|
+
- CTA must use the brand's most energetic color.
|
|
94
|
+
- White backgrounds prevent color fatigue when using multiple brand colors.
|
|
95
|
+
- Never use muted, desaturated tones for primary elements — that signals premium, not playful.
|
|
96
|
+
|
|
97
|
+
---
|
|
98
|
+
|
|
99
|
+
## Typography
|
|
100
|
+
|
|
101
|
+
### Scale
|
|
102
|
+
| Role | Size | Weight | Notes |
|
|
103
|
+
|---|---|---|---|
|
|
104
|
+
| Hero headline | 32-56px | 700-900 | Friendly bold, may be condensed |
|
|
105
|
+
| Section headline | 22-32px | 700 | |
|
|
106
|
+
| Product name | 16-20px | 600-700 | |
|
|
107
|
+
| Product description | 14-16px | 400 | Friendly tone, short |
|
|
108
|
+
| Price | 18-24px | 700 | Tabular numerals, brand accent |
|
|
109
|
+
| CTA | 15-18px | 700 | |
|
|
110
|
+
| Navigation label | 13-14px | 500-600 | |
|
|
111
|
+
| Promo badge | 11-13px | 700-800 | All-caps or bold |
|
|
112
|
+
|
|
113
|
+
### Font Pairings
|
|
114
|
+
| Brand type | Font |
|
|
115
|
+
|---|---|
|
|
116
|
+
| Fast food | Nunito Black / ExtraBold, Fredoka One, or brand custom |
|
|
117
|
+
| Coffee / lifestyle | Lato Bold, Raleway, or circular |
|
|
118
|
+
| Family toys | Nunito, Poppins, or Fredoka One |
|
|
119
|
+
| Family food/health | Rounded Sans: Nunito, Quicksand, or Poppins |
|
|
120
|
+
| Gaming consumer | Custom or Barlow, Exo 2, or Noto Sans Bold |
|
|
121
|
+
|
|
122
|
+
### Rules
|
|
123
|
+
- Use rounded fonts — sharp serifs and thin weights feel cold for playful brands.
|
|
124
|
+
- Headlines must command attention immediately — heavy weight, high contrast.
|
|
125
|
+
- Never use decorative fonts that sacrifice legibility.
|
|
126
|
+
|
|
127
|
+
---
|
|
128
|
+
|
|
129
|
+
## Spacing System
|
|
130
|
+
|
|
131
|
+
| Token | Value | Use |
|
|
132
|
+
|---|---|---|
|
|
133
|
+
| `--space-xs` | 4px | Icon nudges |
|
|
134
|
+
| `--space-sm` | 8px | Label margins |
|
|
135
|
+
| `--space-md` | 16px | Card padding, button padding |
|
|
136
|
+
| `--space-lg` | 24px | Between product cards |
|
|
137
|
+
| `--space-xl` | 40-48px | Section separation |
|
|
138
|
+
| `--space-2xl` | 64-80px | Hero padding |
|
|
139
|
+
|
|
140
|
+
- Product grids: 16-20px gutters.
|
|
141
|
+
- CTA buttons: generous padding (16px × 32px minimum) — must feel easy to tap.
|
|
142
|
+
- Cards: 16px padding, 8-12px border-radius.
|
|
143
|
+
|
|
144
|
+
---
|
|
145
|
+
|
|
146
|
+
## Motion and Interaction
|
|
147
|
+
|
|
148
|
+
### Principles
|
|
149
|
+
- Microinteractions should delight — bouncy, friendly, never cold or mechanical.
|
|
150
|
+
- Add-to-cart / Order: satisfying animation (checkmark pop, cart count bounce).
|
|
151
|
+
- Promo banner: gentle left-right auto-scroll with pause on hover.
|
|
152
|
+
- Product card: hop/lift on hover, 150ms.
|
|
153
|
+
|
|
154
|
+
### Mascot / Character Animation
|
|
155
|
+
- Character appears on key moments: empty cart ("Add your first item!"), order success, loyalty milestone.
|
|
156
|
+
- Keep to a few frames — simple, not complex.
|
|
157
|
+
- `prefers-reduced-motion`: replace all bounce/spring animations with instant transitions.
|
|
158
|
+
|
|
159
|
+
### Loading
|
|
160
|
+
- Skeleton: match card dimensions, shimmer animation.
|
|
161
|
+
- Order confirmation: celebratory micro-animation (checkmark or confetti), then settled state.
|
|
162
|
+
|
|
163
|
+
### Transitions
|
|
164
|
+
- Button tap: scale `0.95` on press, bounce back, 150ms spring.
|
|
165
|
+
- Card hover: `translateY(-4px)`, `box-shadow` lift, 150ms ease.
|
|
166
|
+
|
|
167
|
+
---
|
|
168
|
+
|
|
169
|
+
## Responsive Behavior
|
|
170
|
+
|
|
171
|
+
| Breakpoint | Key changes |
|
|
172
|
+
|---|---|
|
|
173
|
+
| Mobile 375px | Hero: full-width, stacked CTA. Menu: single-column. Bottom nav bar. Large tap targets. Price prominent on card. |
|
|
174
|
+
| Tablet 768px | 2-column menu grid. Nav visible. |
|
|
175
|
+
| Desktop 1024px | 3-4 column product grid. Full nav visible. |
|
|
176
|
+
| Wide 1440px+ | Max-width 1280px. Product grid up to 5 columns. |
|
|
177
|
+
|
|
178
|
+
- Mobile is the primary experience for food ordering — optimize for thumb reach.
|
|
179
|
+
- Bottom nav bar on mobile: 5 items max, icons + labels.
|
|
180
|
+
- "Add to Order" button: sticky at bottom of product detail on mobile.
|
|
181
|
+
|
|
182
|
+
---
|
|
183
|
+
|
|
184
|
+
## Accessibility Requirements
|
|
185
|
+
|
|
186
|
+
- Food photography alt text: describe the food item, not "image of food" — e.g., `alt="Big Mac burger with sesame bun, lettuce, cheese, and special sauce"`.
|
|
187
|
+
- Menu customization: radio buttons or checkboxes with visible labels. `<fieldset>` + `<legend>` per option group.
|
|
188
|
+
- Allergen info: must be a text element, visible by default, not only revealed on hover.
|
|
189
|
+
- Bottom navigation: `role="navigation"`, `aria-label="Main navigation"`. Active item: `aria-current="page"`.
|
|
190
|
+
- Promotions and badges: always include text content, not just color/icon.
|
|
191
|
+
- Character/mascot images: `alt` describes the character's action, not just "mascot."
|
|
192
|
+
- Order confirmation: `aria-live="polite"` for success message.
|
|
193
|
+
- Touch targets: all buttons and links minimum 44×44px — critical for food ordering on mobile.
|
|
194
|
+
- Promo banner: auto-scrolling must pause on focus and on `prefers-reduced-motion`.
|
|
195
|
+
|
|
196
|
+
---
|
|
197
|
+
|
|
198
|
+
## UX Principles for This Method
|
|
199
|
+
|
|
200
|
+
1. **Make the primary task impossible to miss.** Ordering or finding a location is the job — never bury it.
|
|
201
|
+
2. **Delight is earned through speed, not decoration.** A fast, frictionless order is more delightful than a bouncy animation on a slow page.
|
|
202
|
+
3. **Familiarity is a feature.** Use recognizable patterns (bottom nav, large cards, price prominent) — users already know this language.
|
|
203
|
+
4. **Food photography sells.** Invest in imagery. A great photo of food is worth 1000 feature descriptions.
|
|
204
|
+
5. **Broad audience.** Someone's grandmother should be able to order without frustration. Do not assume tech literacy.
|
|
205
|
+
6. **Loyalty creates habit.** Rewards and loyalty flows are high-value — design them to be simple and visible.
|
|
206
|
+
|
|
207
|
+
---
|
|
208
|
+
|
|
209
|
+
## Component Specs
|
|
210
|
+
|
|
211
|
+
### Menu Product Card
|
|
212
|
+
```
|
|
213
|
+
Width: flexible
|
|
214
|
+
Border-radius: 12px
|
|
215
|
+
Background: white
|
|
216
|
+
Border: 1px solid var(--border)
|
|
217
|
+
Image: 16:9 or square, object-fit: cover, border-radius top
|
|
218
|
+
Product name: 16-18px, weight 700, margin-top 12px
|
|
219
|
+
Description: 13-14px, text-secondary, 2-line clamp
|
|
220
|
+
Price: 16-20px, weight 700, brand accent color
|
|
221
|
+
CTA: "Add" button, right-aligned or full-width, brand primary
|
|
222
|
+
```
|
|
223
|
+
|
|
224
|
+
### CTA Button (Playful)
|
|
225
|
+
```
|
|
226
|
+
Background: brand primary
|
|
227
|
+
Text: white, 15-18px, weight 700
|
|
228
|
+
Padding: 14-16px 28-36px
|
|
229
|
+
Border-radius: 8-12px
|
|
230
|
+
Hover: darken 8%, scale 1.02
|
|
231
|
+
Active: scale 0.97, darken 12%
|
|
232
|
+
Focus: 3px solid brand-darker, offset 2px
|
|
233
|
+
Bounce animation on add-to-cart: scale 1.1 → 1.0, 200ms spring
|
|
234
|
+
```
|
|
235
|
+
|
|
236
|
+
### Loyalty Badge / Reward
|
|
237
|
+
```
|
|
238
|
+
Background: brand accent (gold or contrasting)
|
|
239
|
+
Text: 12-13px, bold, white or dark
|
|
240
|
+
Border-radius: 6-8px (pill: 20px)
|
|
241
|
+
Icon: star or flame, 14px, inline
|
|
242
|
+
Padding: 4px 10px
|
|
243
|
+
Positioned: bottom-left of product card image (absolute)
|
|
244
|
+
```
|
|
245
|
+
|
|
246
|
+
### Promo Banner
|
|
247
|
+
```
|
|
248
|
+
Background: brand accent
|
|
249
|
+
Text: 13-14px, bold, white or dark
|
|
250
|
+
Height: 40-44px
|
|
251
|
+
Auto-scroll interval: 4-5s
|
|
252
|
+
Pause on hover + focus
|
|
253
|
+
Indicator dots: below banner, small (6px), brand light color
|
|
254
|
+
```
|
|
255
|
+
|
|
256
|
+
---
|
|
257
|
+
|
|
258
|
+
## Anti-Patterns to Avoid
|
|
259
|
+
|
|
260
|
+
- Do not hide the menu behind 3 clicks.
|
|
261
|
+
- Do not use small, light, or thin typography — broad audiences include elderly users.
|
|
262
|
+
- Do not use low-contrast food badges or promo text on colorful backgrounds.
|
|
263
|
+
- Do not autoplay promotional audio.
|
|
264
|
+
- Do not require account creation before viewing the menu.
|
|
265
|
+
- Do not use dark patterns for upsells — every "add extra" must be a clear opt-in, not pre-checked.
|
|
266
|
+
- Do not use countdown timers for items that are not actually time-limited.
|
|
267
|
+
- Do not rely solely on color to convey allergen information.
|
|
268
|
+
|
|
269
|
+
---
|
|
270
|
+
|
|
271
|
+
## QA Checklist
|
|
272
|
+
|
|
273
|
+
- [ ] Primary CTA ("Order Now", "Add to Cart") visible above fold on mobile.
|
|
274
|
+
- [ ] Bottom nav (if used): all items labeled, accessible, active state clear.
|
|
275
|
+
- [ ] Food photography loads with skeleton placeholder.
|
|
276
|
+
- [ ] Menu customization uses `<fieldset>` + `<legend>` with keyboard-navigable options.
|
|
277
|
+
- [ ] Allergen info visible as text, not hover-only.
|
|
278
|
+
- [ ] All interactive elements ≥ 44×44px touch target.
|
|
279
|
+
- [ ] "Add to Order" sticky button on mobile product detail.
|
|
280
|
+
- [ ] Loyalty / rewards section reachable within 2 taps.
|
|
281
|
+
- [ ] Order confirmation announces success to screen reader (`aria-live`).
|
|
282
|
+
- [ ] `prefers-reduced-motion`: all bounce/spring animations replaced with instant transitions.
|
|
283
|
+
- [ ] No pre-checked upsell options (dark pattern check).
|
|
284
|
+
- [ ] Page loads in under 3s on 4G (food ordering is mobile-first, often on poor connections).
|