Premium scroll site: a different concept for every topic
The user gives ONE topic. You do the work of a creative director plus a front-end engineer: invent a concept that fits that topic, choose the scroll animations that express it, build the whole site in UZ / RU / EN, test it, deliver one index.html. Two different topics must produce two visibly different sites (different story, palette, type, layout rhythm and signature animation). Never ship the same skeleton twice.
Files in this skill (tools, not the design):
assets/engine.js: generic scroll engine. Any[data-pin]section gets--p(scroll progress 0 to 1); the body gets--page. Also reveal-on-enter, counters, tilt and the i18n switcher. Inline it into the page.assets/patterns.md: 15 tested scroll patterns (horizontal journey, clip-path portal, zoom-through, line draw, card stack, colour-world shift, parallax, 3D turn, counters, text rise, masked text, frame sequence, speed marquee, tilt, split swap) as CSS that reads--p. Combine and invent beyond them.assets/template.html: ONE example (a tech product page) showing engine plus layout. Use it only as a reference for structure. Do not copy its section order or look unless the topic is truly similar.assets/three-object.js: optional tested Three.js scroll-driven 3D object (chrome, aluminium, smoked glass, acrylic). See design-system.md section 3 for the importmap.assets/brand-identity.md: MANDATORY brand and colour procedure (research honestly, choose ONE of 14 approved palettes, token set, name/slogan/concept, fonts with Uzbek support, logo SVG, brand sheet). Palette and brand decisions come from here.assets/contest-rules.md: MANDATORY effort, pages, story, quality gates, test and integration rules for olympiad / ticket / timed work. In a contest or ticket the ticket text wins first, then contest-rules.md, then this file's defaults.assets/app-starter.html: contest starter, a working multi-page offline app (see Modes).assets/flow-test.example.jsandassets/make-docs.jssupport testing and documents.OLIMPIADA_YORIQNOMA.md(plugin root) is the participant's day guide, andcontest-prompt.mdis a paste-in version of these rules for tools that cannot load skills.assets/qa.js: Playwright check (phone and desktop, three languages).assets/design-system.md: the MANDATORY art-direction rules (selective Apple-style glass UI, Nike-style cinematic motion, premium 3D and lighting, typography, micro-interactions, performance and accessibility). Read it before the Concept step and obey it in every site; it decides materials, glass usage and motion language, while the Concept step decides each brand's palette and identity.
Modes
- Showcase mode (default: user names a topic): one premium scroll site as described below.
- Contest / ticket mode (olympiad, "Eng yaxshi veb-sayt", ticket, timed task, or the user says so). The result is a WORKING WEB APP that completes the ticket, NOT a landing page. Read
assets/contest-rules.md(scoring rubric, defects, deliverables) first. Procedure:- Paste or read the ticket. Write the acceptance table: every mandatory section/action as T1..Tn with a one-line pass test. Stage minimums: district = 3 meaningful sections plus 1 finished user action and clear navigation; regional = 3 pages or 2 linked actions, wrong-input checking and a result; republic = 4 pages or 3 linked actions, saved data, empty and error states. Only what the ticket requires is scored; extras never cover a defect.
- Budget time (60 min: plan 5 / build 40 / test 10 / submit 5; 120 min: 10/80/20/10; 240 min: 25/155/40/20). Early submission gives no bonus.
- Start from
assets/app-starter.html(offline, one file, hash router, 4 pages, validation, empty/success states, localStorage, UZ/RU/EN). Replace content, tokens, items and flows for the ticket. Use ticket-supplied data exactly (names, dates, addresses unchanged). Use only synthetic test data; label test forms as test. - OFFLINE and ONE FILE: no CDN, no web fonts, no external images, no remote scripts. System font stack. Three.js or any library only if the ticket allows and it is inlined locally; otherwise CSS/SVG/canvas.
- Build the mandatory flows first and make them pass; only then polish (art direction, motion). Premium visuals are judged inside UX (10) and creativity (10); function (30) and tech use (20) weigh more.
- Test:
node assets/qa.js ./index.html(390/768/1366, three languages, offline) and a flow test adapted fromassets/flow-test.example.jsfor T1..Tn. Fix every failure. - Docs: fill
contest.jsonand runnode assets/make-docs.js contest.jsonto generate README, test report, tools and sources, prompt log, defence plan, self-score and submission checklist. Copy 3 to 5 screenshots fromqa/. - Never leave passwords, tokens or keys in client code. Do not assume integrations (Supabase, Telegram, Google login) are allowed; use them only if the ticket says so.
- Keep replies short; do not narrate tools; no extra variants.
Workflow
1. Concept (write it in 6 lines to yourself, then 1 line to the user)
Answer, specifically for this topic:
- Feeling: 3 adjectives (a bakery: warm, tactile, slow; a racing app: sharp, fast, loud).
- Visual metaphor: the one image or motion that IS the topic (bread rising = scale and warm colour shift; a route = line draw; a library = card stack; a skyline = parallax layers; a gym = counters and speed marquee; a dentist = clean light mode with zoom-through).
- Palette and brand: follow
assets/brand-identity.md(one of the 14 approved palettes, full token set, name, slogan, logo SVG). Light, warm or colourful worlds are allowed and often better than dark; contrast first (text 4.5:1). Existing brand colours of the user always win. - Typography: one display face and one text face from Google Fonts with Latin and Cyrillic support (for example Inter Tight, Manrope, Unbounded, Onest, Golos Text, Montserrat, Playfair Display for luxury, Bebas Neue/Oswald for sport). Display type is huge (
clamp()up to 8 to 20vw) with tight tracking. - Signature interaction: ONE hero scroll moment that nobody forgets (a portal opening, a zoom through the logo, a product turning 200 degrees, a path being drawn across the screen, a background that changes season).
- Supporting motions: 3 to 5 patterns from
patterns.md(or invented), each used for the content it suits. Variety rule: use at least 3 patterns that the template does not use, and a section order that follows the topic's story (problem, product, proof, price, contact are not fixed).
2. Content
Use facts the user gave exactly. Everything else is concrete draft copy, with unknowns marked [narx], [manzil], [telefon]. NEVER invent statistics, prices, awards, testimonials or user counts. Counters only with real numbers.
3. Build
- One
index.html: inline CSS and JS,engine.jsinlined, fonts by Google Fonts<link>. - Structure each pinned scene as
<section data-pin style="height:NNNvh"><div class="stage" style="position:sticky;top:0;height:100svh">. Animate withcalc()andvar(--p)ontransform,opacity,clip-path,filter. Sub-ranges:clamp(0,(var(--p) - a)/(b - a),1). - Visuals without photos: build them from CSS gradients, SVG (paths, blobs, grids, icons drawn inline), big type, emoji-free shapes, canvas. Do not hotlink images; use user-supplied images only, with width and height.
- Always include: sticky nav with UZ/RU/EN switch (
data-l="uz"buttons), hero, signature scene, supporting scenes, a clear call-to-action (phone, Telegram or form link), footer. - Devices: every animation must work on phone (360 to 430), tablet (768 to 1024, portrait and landscape) and desktop. Use
clamp()sizes, fluid grids and breakpoints at 700px and 1024px; pinned heights about 70 percent on phone, 85 percent on tablet; horizontal-journey cards 84vw on phone, 46vw on tablet, 560px on desktop. Touch devices get no hover-only effects; tablets use the touch path ((hover:hover)gate in engine.js). Test at 390x844, 768x1024 and 1366x768. - Responsive: design at 390px first. Pinned heights about 30 percent shorter under 700px. No hover-only interactions.
body{overflow-x:clip}, neveroverflow-x:hiddenon html and body together. Pinned stages use100svh. - Reduced motion:
engine.jsadds.static; write CSS so the final state is readable without animation (.static .stage{position:static;height:auto}).
3b. Brand sheet
After the build, include in the final message a compact brand sheet (palette name and hex tokens, fonts, slogan, concept, logo SVG) as described in brand-identity.md.
4. Three languages, complete
- One global
D={uz:{...},ru:{...},en:{...}}; every visible string usesdata-i18n="key"(data-htmlwhen it contains<br>or tags). Includetitleper language. If you generate DOM from text (word-by-word reveal, marquees), do it inwindow.onLang=function(l){...}. - Natural copy in each language, not word for word. Uzbek Latin with proper o‘ g‘ ’. Russian is 20 to 30 percent longer: shorten text, do not shrink type. Headlines are short and end with a period.
- SEO:
<title>, description, og tags,hreflanguz/ru/en/x-default using?lang=, canonical, JSON-LD when the entity is real.
5. QA (required, before delivering)
node <skill>/assets/qa.js ./index.html (needs Playwright). It checks, at 390x844, 768x1024 and 1366x768 in uz, ru, en: console errors, horizontal overflow, empty translated nodes, missing dictionary keys, and saves screenshots to ./qa/. Then LOOK at the screenshots (Read PNGs) of the signature scene and the ru phone set. Fix, rerun until clean. Also scroll through every pinned scene once and confirm the animation really runs (read --p and a computed style at 10, 50, 90 percent). If you cannot run a browser, say so plainly; do not claim tests you did not run. An emulator is not a real phone.
6. Deliver
Send index.html with SendUserFile. One short message: the concept in one sentence, the signature animation, the three languages, what was tested, placeholders to fill, and one next step (domain, SEO files, more sections).
Quality bar (what "Nike / Apple" means here)
- One idea per screen, huge type, generous space, almost no body text.
- Motion has purpose: it explains or reveals, it is never decoration only. Ease with
cubic-bezier(.2,.7,.2,1); scroll-linked motion is smooth and reversible. - Consistent system: one radius scale, one spacing rhythm, one accent usage rule.
- Performance: 60 fps on a mid phone: no layout reads in scroll handlers, no
box-shadowanimation, images lazy, file under about 500 KB without media.