yuv-design
The mandatory web-design defaults for Yuval Avidani. Whenever you build any web surface (a marketing page, a dashboard, a single artifact, a React component) and a brand isn't explicitly specified by the project, these defaults apply. They give Yuval's work a recognizable fingerprint without any per-request copy-paste of fonts or colors.
This skill is the frontend / web counterpart to yuv-viral-video (which carries the same brand into rendered MP4s).
Battle-tested rules (lessons from production — do not relearn)
These are not opinions. Each one cost an iteration in a real session and is now a hard rule. Read all 12 before starting any frontend output.
1. Bilingual = toggle, NEVER side-by-side
If the project is bilingual (EN + HE / EN + AR / EN + FA), build a language toggle (button in nav, default EN, switch to HE shows Hebrew content). Do not show both languages simultaneously stacked or columned. Side-by-side bilingual UI causes:
- Massive headlines collide visually (Anton 8vw + Rubik 5vw = visual overlap)
- Mobile breaks because two columns can't both fit
- Users complain "the fonts override each other" — and they're right
The toggle pattern: data-lang="en" and data-lang="he" attributes on every translatable element, plus a universal CSS rule:
html:not([lang="he"]) [data-lang="he"] { display: none !important; }
html[lang="he"] [data-lang="en"] { display: none !important; }
Plus a JS handler that sets html[lang], swaps document.title, persists to localStorage, and updates active button. Full code template in patterns.md → "Bilingual toggle".
2. Mobile = hamburger, ALWAYS, at ≤ 880px with > 6 nav items
If the nav has more than 6 links, build a hamburger menu for max-width: 880px. Don't let the nav wrap onto 5 lines and eat the viewport. This is not optional. Default desktop nav + collapsible mobile menu is the spec. Full code template in patterns.md → "Mobile hamburger nav".
3. One display headline per section, never two stacked
Anton at any size > 50vw / 6vw is HEAVY by design (font-weight 400 is its only weight, but it's a condensed display face). Stacking two display headlines (e.g., EN h1 + HE h1) creates visual overlap because line-heights below 1.0 cause descenders to invade the next line's ascenders. Solution: toggle (rule 1), or one headline + one secondary subhead at ≤ 50% of the headline size.
4. Never assign HTML strings as element content with anything that isn't 100% literal author-controlled
- Use
el.textContent = valuefor plain text - Use
createElement+appendChildfor structured content - Reserve assigning HTML strings as element content for compile-time constants only (string literals you wrote)
- Assigning a variable as HTML content will be blocked by security hooks even when "safe" — and if the variable ever takes user input, it's an XSS hole. Just don't.
5. document.title is part of language toggle
Don't just swap visible content — also call document.title = TITLES[lang]. Otherwise the browser tab title stays English forever, which screams "half-built bilingual" to native speakers.
6. Install command is per-skill, never per-repo
If the skills repo has 5 skills and the user wants 1, the install command must reference that 1 skill — git clone --depth 1 --filter=blob:none --sparse <repo> /tmp/x && cd /tmp/x && git sparse-checkout set skills/<this-skill> && cp -R skills/<this-skill> ~/.claude/skills/. Do not use npx skills add <repo> as the recommended path for a single skill — it's interactive and forces the user to pick from a list.
7. Spec-driven content (zero hallucination)
When the user says "add a CTA for X" / "embed link to Y", read the actual page first with the right tool:
- WebFetch → HTML-static pages (blogs, docs, GitHub)
curl→ API endpoints, raw HTML inspection- Claude-in-Chrome → JS-rendered SPAs (Teachable, learn.*, builder.io sites)
Don't guess. Don't paraphrase. Quote. If a field isn't on the page, write "not on page" and ask.
8. Mobile-first responsive = baseline check, not a polish stage
Before declaring any frontend work done, resize the preview to 375×812 (iPhone size) and screenshot. If you see:
- Text overflowing the viewport horizontally
- A nav wrapping to > 2 lines
- Headlines that are barely readable
- A grid that should be 2 columns but is 1 narrow column with overflow
…it's not done. Fix before shipping.
9. Always IntersectionObserver for any catalog with > 8 GSAP demos
A page with 10+ GSAP timelines all running simultaneously will cook the user's CPU. Pause demos when their stage is offscreen:
const observer = new IntersectionObserver((entries) => {
entries.forEach(e => {
const tl = e.target.__tl;
if (!tl) return;
if (e.isIntersecting) tl.play();
else tl.pause();
});
}, { threshold: 0.15 });
stages.forEach(s => observer.observe(s));
Each stage stores its timeline at stage.__tl = tl. Standard pattern across the catalog.
10. Effect-ID copy chip pattern (catalog/showcase sites)
For any "browse and pick" interface (effects catalog, design system, component library), every item has a copyable identifier:
- Pink/yellow chip with monospace font
- Click to copy
- Toast confirmation
- Use
e.stopPropagation()if the chip is inside a clickable card so the parent link doesn't navigate - Pattern in
patterns.md→ "Effect ID chip"
11. Hero = real Hyperframes-compatible composition
For any major site (catalog, landing, marketing), the hero section should use real Hyperframes data-* attributes (data-composition-id, data-start, data-duration, data-width="1920", data-height="1080") on the stage element. This way the site itself is a Hyperframes artifact — the user can run hyperframes render on the same code to get an MP4 promo for the site. Two outputs (web + video) from one source. Pattern in patterns.md → "Hyperframes hero reel".
12. SSL cert nudge for GitHub Pages custom domain
If the GH Pages cert state stays at none for > 15 min after DNS propagates correctly:
gh api -X PUT /repos/{owner}/{repo}/pages -f "cname="
sleep 5
gh api -X PUT /repos/{owner}/{repo}/pages -f "cname=<custom-domain>"
This kicks the Let's Encrypt validation flow. Don't wait the rumored 24 hours — toggle and it lands within 15 min.
When this skill applies
- The user is Yuval Avidani.
- The output is a web surface — a
.htmlfile, a React component, a Next.js page, a dashboard, a marketing site. - The project hasn't specified its own palette, type system, or brand. (When the project HAS its own system, that wins — these are defaults for the empty state, not overrides.)
Typography — mandatory defaults
English
| Role | Font | Weight | Treatment |
|---|---|---|---|
| Display / headlines / hero text / CTAs / wordmarks | Anton | 400 (only weight) | UPPERCASE always · letter-spacing -0.03em to -0.04em · line-height 0.9–1.0 |
| Body / UI / paragraphs | Inter | 400 / 500 / 600 / 700 | line-height 1.5 · default tracking |
Hebrew
| Role | Font | Weight | Treatment |
|---|---|---|---|
| Display / headlines / RTL hero text | Rubik | 900 (Black) | line-height 0.95–1.05 |
| Body / UI / paragraphs | Assistant | 400 / 500 / 600 / 700 | line-height 1.55–1.7 (Hebrew needs more) · dir="rtl" on container |
Mixed bilingual
Stack both fonts in one font-family and let the browser route per-glyph:
:root {
--font-display: 'Anton', 'Rubik', sans-serif;
--font-body: 'Inter', 'Assistant', sans-serif;
}
Latin chars take Anton/Inter, Hebrew chars fall through to Rubik/Assistant. One declaration handles bilingual text.
Banned
- Serif fonts as defaults
system-ui/ default font stack- Anton on Hebrew text (renders as hollow X — Anton is Latin-only)
- Title Case on display headlines (always uppercase or always lowercase, never mixed)
Google Fonts import (always)
<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
<link href="https://fonts.googleapis.com/css2?family=Anton&family=Assistant:wght@400;500;600;700&family=Inter:wght@400;500;600;700&family=Rubik:wght@400;500;700;900&display=swap" rel="stylesheet">
Drop Hebrew fonts only if the project is English-only AND will never localize.
RTL setup for Hebrew pages
<!DOCTYPE html>
<html lang="he" dir="rtl">
.card {
padding-inline: 2rem;
margin-inline-start: auto;
border-inline-start: 2px solid var(--pink);
}
Use logical properties (*-inline-*) over physical (*-left, *-right).
Color palette — the signature
:root {
--pink: #FF1464; /* primary brand · CTAs · accents · the thread */
--yellow: #E5FF00; /* accent · dominates when used */
--black: #0A0A0A; /* warm near-black, never blue-black */
--off-white: #FAFAF7; /* paper-feel, replaces pure #FFFFFF entirely */
--bone: #F5EEE4; /* transitional sections, cream */
--charcoal: #1A1A1A; /* primary text on light */
--warm-gray: #8B8680; /* secondary text on light */
--light-gray: #A8A39D; /* secondary text on dark */
}
Strict rules
- Pure
#FFFFFFis banned. Use--off-white. Page backgrounds, cards, inverted text — all#FAFAF7. - Blue is banned as a default. No navy, no slate, no indigo, no cool tones. If the project legitimately requires blue (banking, medical), use it — otherwise warm family only.
- Pink is the thread. Logo, primary CTA, section accents. Used consistently across a site is what makes the work recognizable.
- Yellow dominates when it appears. Never timid. If yellow shows up, it's a full-bleed background block, a section divider, a hero highlight bar, or a large pull-quote field — not a tiny accent swatch.
- Gradients only pink → yellow, on small surfaces only (buttons, text underlines, icon fills). Never a full-page gradient wash.
Tailwind config
module.exports = {
theme: {
extend: {
colors: {
pink: '#FF1464',
yellow: '#E5FF00',
black: '#0A0A0A',
'off-white': '#FAFAF7',
bone: '#F5EEE4',
charcoal: '#1A1A1A',
'warm-gray': '#8B8680',
'light-gray': '#A8A39D',
},
fontFamily: {
display: ['Anton', 'Rubik', 'sans-serif'],
body: ['Inter', 'Assistant', 'sans-serif'],
mono: ['JetBrains Mono', 'ui-monospace', 'monospace'],
},
maxWidth: { content: '1440px' },
boxShadow: {
warm: '0 8px 32px rgba(255, 20, 100, 0.08)',
'warm-lg':'0 20px 60px rgba(255, 20, 100, 0.12)',
},
},
},
};
Never use the default Tailwind palette names (slate-*, zinc-*, gray-*, emerald-*, cyan-*, indigo-*, violet-*, rose-*) in Yuval's projects.
Layout & component defaults
| Property | Value | Reason |
|---|---|---|
| Border radius — cards | 0 (Brutalist) or 40–56px (Glassmorphism) |
The 8/12/16px "corporate-rounded" middle ground is the strongest AI-template tell on the planet. Avoid. |
| Border radius — pill CTAs | 999px |
Always. |
| Shadows | warm-toned, e.g. 0 20px 60px rgba(255, 20, 100, 0.12) |
Never the default blue-black rgba(0,0,0,0.1). |
| Whitespace | generous | Premium feel comes from restraint, not density. |
| Layout | asymmetric > grid-perfect | Offset columns. Overlapping. One element breaking the grid. |
| Section padding (vertical) | desktop 120–160px · mobile 64–80px | Wide breathing room. |
| Max content width | 1440px centered | Don't stretch full-bleed by default. |
| Icons | Phosphor or Lucide, single-color stroke override | Never multicolor icon sets. |
Grain texture (always on light backgrounds)
body { background-color: var(--off-white); position: relative; }
body::before {
content: '';
position: fixed;
inset: 0;
pointer-events: none;
z-index: 1;
opacity: 0.025;
background-image: url("data:image/svg+xml,%3Csvg viewBox='0 0 200 200' xmlns='http://www.w3.org/2000/svg'%3E%3Cfilter id='n'%3E%3CfeTurbulence type='fractalNoise' baseFrequency='0.9' numOctaves='3' /%3E%3C/filter%3E%3Crect width='100%25' height='100%25' filter='url(%23n)'/%3E%3C/svg%3E");
}
Lift to 0.04 for more pronounced grain, drop to 0.01 for subtler.
Animation defaults
Every animation needs a reason. The site should feel alive but never restless. Hovers are deliberate. Reveals are scroll-triggered. Numbers count up on viewport entry. Connecting lines draw themselves.
Library preferences (in order)
- GSAP (https://gsap.com) — primary. Use SplitText for headline reveals, ScrollTrigger for scroll-driven sequences, MotionPath for paths. Prefer over Framer Motion for non-trivial work — GSAP produces higher-end results and is seekable (matters for Hyperframes capture).
- Three.js with React Three Fiber — for 3D when the project can justify it.
- MediaPipe — for gesture/pose interactions when the project has a signature "wow" moment.
- Lottie — when the designer ships a
.jsonvector animation. - CSS-only micro-interactions — fine for hover states, focus rings, button press. Don't reach for a library.
Easing vocabulary
| Use | Easing |
|---|---|
| Card entrance / overshoot | back.out(1.7) |
| SplitText reveal | power3.out or power4.out |
| Slam beats / hero punches | expo.out |
| Idle floats / breathing | sine.inOut |
| Playful springy | elastic.out(1.2, 0.5) |
| Mechanical / clinical | power3.inOut |
GSAP SplitText hero reveal (reference)
import gsap from 'gsap';
import { SplitText } from 'gsap/SplitText';
import { ScrollTrigger } from 'gsap/ScrollTrigger';
gsap.registerPlugin(SplitText, ScrollTrigger);
const split = new SplitText('.hero-headline', { type: 'words,chars' });
gsap.from(split.chars, {
scrollTrigger: { trigger: '.hero-headline', start: 'top 80%' },
yPercent: 100,
opacity: 0,
duration: 0.8,
ease: 'power4.out',
stagger: 0.02,
});
Hyperframes compatibility (free insurance)
Yuval often captures sites as video for keynotes, social reels, and marketing. Hyperframes (https://github.com/heygen-com/hyperframes) renders HTML to deterministic, frame-by-frame video.
Patterns to follow by default
Semantic HTML5 elements (
<section>,<article>,<header>,<nav>,<footer>). Div soup is harder to target for frame capture.Mark video-destined regions:
<!-- HYPERFRAMES_VIDEO_SLOT: hero --> <section class="hero">...</section> <!-- /HYPERFRAMES_VIDEO_SLOT -->Prefer GSAP timelines (seek-driven) over CSS
@keyframeswhen a sequence might later be captured. GSAP can be seeked to an exact time (tl.seek(2.5)); CSS keyframes can't reliably.Avoid wall-clock dependencies. No
Date.now(), nosetIntervalyou can't seek. Use scroll position, explicit GSAP timelines, orrequestAnimationFrametied to a deterministic clock.
Not every project will be captured — but these patterns are free.
What NOT to do (explicit defaults to avoid)
- Stock photography. No generic business people, abstract cityscapes, Unsplash textures. Prefer abstract geometric, custom-generated, or Yuval's own (Hope cheetah, Marcus lion, AI-generated big cat content) over stock.
- Emoji in marketing / business / enterprise sites. Personal blogs, casual projects, social content — fine. Enterprise / client work — no.
- Soft drop-shadow rounded-corner "template" cards. Flat white card, 12px radius,
0 4px 6px rgba(0,0,0,0.1)shadow. The dominant AI-slop visual. Never ship this. - Default Tailwind palette names. Use the custom palette or the project's brand.
- Multicolor icon sets. Phosphor / Lucide single-color stroke only.
- Cookie banners, chat widgets, marketing popups in demos. Production concerns. Demos stay clean.
- The "AI-generated feel": templated layouts, generic hero → features → pricing → footer with no personality. Lorem ipsum. Placeholder text like "Your tagline here." Write real copy or realistic placeholder copy specific to the project.
- Pure
#FFFFFF. Use#FAFAF7. - Blue as a default accent. Warm family only unless required.
A starter snippet — English hero
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
<link href="https://fonts.googleapis.com/css2?family=Anton&family=Inter:wght@400;500;600;700&display=swap" rel="stylesheet">
<style>
:root {
--pink: #FF1464;
--yellow: #E5FF00;
--black: #0A0A0A;
--off-white: #FAFAF7;
--charcoal: #1A1A1A;
}
* { box-sizing: border-box; margin: 0; padding: 0; }
body {
font-family: 'Inter', sans-serif;
background: var(--off-white);
color: var(--charcoal);
line-height: 1.5;
}
.hero {
min-height: 100vh;
display: grid;
grid-template-columns: 1.2fr 1fr;
align-items: center;
padding: 120px 80px;
max-width: 1440px;
margin-inline: auto;
}
.hero h1 {
font-family: 'Anton', sans-serif;
font-size: clamp(4rem, 9vw, 10rem);
text-transform: uppercase;
letter-spacing: -0.04em;
line-height: 0.9;
}
.hero h1 em { font-style: normal; color: var(--pink); }
.cta {
display: inline-block;
margin-top: 3rem;
padding: 1.25rem 2.5rem;
background: var(--pink);
color: var(--off-white);
font-family: 'Anton', sans-serif;
text-transform: uppercase;
letter-spacing: 0.02em;
border-radius: 999px;
text-decoration: none;
font-size: 1.125rem;
}
</style>
</head>
<body>
<!-- HYPERFRAMES_VIDEO_SLOT: hero -->
<section class="hero">
<div>
<h1>Fly high<br>with <em>yuv.ai</em></h1>
<a href="#" class="cta">Start learning</a>
</div>
<div><!-- right column reserved for image / 3D / animation --></div>
</section>
<!-- /HYPERFRAMES_VIDEO_SLOT -->
</body>
</html>
A starter snippet — Hebrew RTL
<!DOCTYPE html>
<html lang="he" dir="rtl">
<head>
<meta charset="UTF-8">
<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
<link href="https://fonts.googleapis.com/css2?family=Assistant:wght@400;500;600;700&family=Rubik:wght@400;700;900&display=swap" rel="stylesheet">
<style>
:root { --pink: #FF1464; --yellow: #E5FF00; --off-white: #FAFAF7; --charcoal: #1A1A1A; }
* { box-sizing: border-box; margin: 0; padding: 0; }
body {
font-family: 'Assistant', sans-serif;
background: var(--off-white); color: var(--charcoal);
line-height: 1.6;
}
.hero { padding-block: 120px; padding-inline: 80px; max-width: 1440px; margin-inline: auto; }
.hero h1 {
font-family: 'Rubik', sans-serif;
font-weight: 900;
font-size: clamp(3rem, 7vw, 8rem);
line-height: 1;
}
.hero h1 em { font-style: normal; color: var(--pink); }
.cta {
display: inline-block;
margin-block-start: 2rem;
padding-block: 1rem;
padding-inline: 2rem;
background: var(--pink);
color: var(--off-white);
font-family: 'Rubik', sans-serif;
font-weight: 700;
border-radius: 999px;
text-decoration: none;
}
</style>
</head>
<body>
<section class="hero">
<h1>תעוף גבוה<br>עם <em>yuv.ai</em></h1>
<a href="#" class="cta">בואו נתחיל</a>
</section>
</body>
</html>
One-line self-check before shipping
- No
#FFFFFFanywhere — replaced with#FAFAF7. - No default Tailwind color classes (
slate-*,zinc-*,indigo-*, etc.). - Anton is uppercase with negative letter-spacing wherever it appears.
- Hebrew pages have
dir="rtl"on<html>and use logical CSS properties. - No 8px or 12px border radius —
0,999px, or 40–56px (glass cards) only. - Shadows are warm-toned, not blue-black.
- If the project involves Hebrew, both Hebrew font pairs (Rubik + Assistant) are loaded.
- GSAP is used for any non-trivial motion (not Framer Motion / pure CSS keyframes).
If any of these fail, fix before delivering.
Companion skill
For video output (rendered MP4), use yuv-viral-video — same brand system, video-tuned hex values, same Anton+Rubik display fonts, but optimized for H264 rendering through Hyperframes.