C:\Users\ISHAAN\.claude\skills\ishaan-ui\references\intake.md

1 # Intake: the opening conversation 2 3 Goal: learn enough to make strong decisions, in one friendly round. People skip questions; that's fine, decide sensibly and say what you chose. 4 5 ## Opening message (adapt the wording, keep it short) 6 7 > Before I start, want to brainstorm the direction together, or should I ask a few quick questions and take it from there? Either way, here's what helps most: 8 9 Then ask, grouped and numbered, with a default in brackets for each: 10 11 ### 1. Which path 12 - Are we **building a new site**, or **rebuilding an existing one**? If existing: the URL or repo. 13 - Any **reference sites** you love (and what you love about each: the layout, the motion, the colours, the feel)? 14 15 ### 2. The brand 16 - Name, what it does, and who it's for, in a sentence or two. 17 - The **one thing** a visitor should believe after five seconds. 18 - Tone: pick a few words (e.g. warm / precise / playful / editorial / technical / luxurious). 19 20 ### 3. Palette 21 - Do you have brand colours? Hex values if possible. 22 - If not: any colours you love or hate? [default: I derive a palette from the brand and references] 23 - Light, dark, or both? [default: one well-made light theme; dark only if it fits the brand] 24 25 ### 4. Type 26 - Brand fonts? [default: I propose a pairing, usually an expressive display face + a quiet grotesk] 27 28 ### 5. Scope and stack 29 - Pages: landing, pricing, auth, dashboard/app, tool pages, blog…? 30 - Stack: framework, styling, animation library [default: whatever the repo already uses; otherwise Next.js + Tailwind + Motion] 31 - Anything that must keep working exactly as now (forms, auth, payments, URLs)? 32 33 ### 6. Truth and assets 34 - Which numbers, logos, testimonials and claims are real and approved to show? (I never invent social proof.) 35 - Do you have photography or illustration, or should I create custom art (procedural or with image-generation prompts you can run)? 36 37 ## After answers 38 39 Reply with a one-screen **direction brief** before building: 40 - The chosen visual idea in one sentence, and the two runner-up ideas you rejected (one line each). 41 - Palette (hex), type pairing, motion personality (e.g. "slow, eased, soft blur; nothing bouncy except micro-interactions"). 42 - Page/section list. 43 Then proceed unless they object. Don't wait for approval on small choices. 44 45 ## If they say "just go" 46 47 Infer everything from the repo, existing copy and any reference, state your assumptions in two or three lines, and start. 48 

$ cd "C:/Users/ISHAAN/.claude/skills/ishaan-ui" && ls -R && cat references/from-scratch.md references/taste.md

.: assets CHANGELOG.md ishaan-ui.skill LICENSE.md README.md references scripts SKILL.md VERSION ./assets: glass.css icon-template.tsx ./references: assets.md checklist.md components.md from-scratch.md intake.md motion.md recreate.md taste.md ./scripts: render-art.mjs # Path A: Create a website from scratch ## 1. Direction brief (from intake) Visual idea, palette, type, motion personality, page list. See `intake.md` → "After answers". ## 2. Foundations first 1. **Tokens** in one CSS file: canvas, surface, surface-2, ink/ink-2/ink-3, line, accent, accent-hover, accent-ink, accent-soft, status, radii, shadows, easing curves (`--ease: cubic-bezier(.22,1,.36,1)`, `--spring: cubic-bezier(.34,1.56,.64,1)`). Map them into the styling system (e.g. Tailwind `@theme`). 2. **Fonts** via the framework loader; expose `--font-display`, `--font-body`, `--font-mono`. 3. **Utilities**: glass / glass-strong / glass-inset, skeleton shimmer, keyframes (`assets/glass.css`). 4. **Brand mark**: a custom logo mark drawn in SVG that expresses the visual idea (e.g. a loupe for a "see clearly" brand) + a wordmark set in the display face. 5. **Icon set**: draw the first 10–15 icons the site needs in one consistent hand (`assets.md`). 6. **Art**: decide the environment (sky, paper, landscape, texture). Render it with `scripts/render-art.mjs` or write prompts, and wire images with slots. ## 3. The landing page skeleton (adapt, don't copy) A reliable premium sequence; change order and content to fit the brand: 1. **Nav**: transparent full-width bar that becomes a floating glass pill on scroll; centre links; secondary + primary button right; account menu when signed in. 2. **Hero**: big display headline (plain line + italic turn), one-sentence lede, one primary action. Below it a large rounded panel holding the environment art with the **real product UI** floating in glass, lightly interactive. Decorative elements (branches, shapes) tucked behind the panel edges with slow parallax. 3. **How it works**: centered heading whose italic line ink-fills on scroll; a numbered accordion on the left that auto-advances (progress hairline) and a panel on the right that shows the real component for each step. 4. **One or two scroll-driven, interactive sections** that teach the product's core idea by letting the visitor *do* it (see `motion.md` → scroll sections). 5. **Cards over an environment**: three glass cards, each with a small real component inside. 6. **A brand-object moment**: an emblem, a stamp, a ticket, a postcard — an object from the visual metaphor that makes the page memorable. 7. **Pricing** (honest), FAQ if useful. 8. **Closing CTA** over the environment, flowing into a **footer set inside art** (landscape, texture). ## 4. App / dashboard (if in scope) - Same tokens, a quieter environment: blurred version of the brand art, tinted for time of day. - Navigation as a floating glass dock (left on desktop, bottom on mobile) with a moving active "bead", hover name-tags, and an account menu that always offers Home, Tools and Sign out. - Every page: big serif masthead (no crumb label above it), glass panes, custom data visuals (dials, ink-well gauges, glass bars), real empty states, a skeleton loading route in the page's own shape. ## 5. Auth A memorable object (e.g. a postcard: picture side + message side with stamp and postmark) with a gentle 3D tilt toward the pointer. Inputs are glass-inset; the primary button uses the accent. Already-signed-in visitors skip the form. ## 6. Then: motion, components, assets, checklist Read `motion.md`, `components.md`, `assets.md`, finish with `checklist.md`. # Taste: what makes a website feel premium ## Contents 1. The core idea 2. Finding the visual idea (never the first one) 3. Colour 4. Typography 5. Layout and rhythm 6. Copy 7. Honesty 8. The anti-slop list (with reasons) --- ## 1. The core idea Premium sites feel *authored*. One person with taste made consistent decisions about everything: a single visual metaphor, one accent colour, two typefaces, a motion personality, and an asset style that could only belong to this brand. Generic sites feel *assembled*: a hero from here, a feature grid from there, icons from a library, a gradient because gradients are popular. So every decision should answer: *does this belong to this brand and this idea?* If a component could be dropped onto any other site unchanged, it is not finished. ## 2. Finding the visual idea (never the first one) Before designing, generate 3 or 4 directions and write each as one sentence. Examples of the shape (not to copy): - "Painted pastoral skies with glass panes floating over them; calm, warm, human." - "A printed field guide: engraved line art, stamps, postmarks, paper grain." - "Instrument panel: watch-bezel dials, hairlines, precise mono numerals." Discard the first (it's usually the most common), then pick the one that best fits the brand's promise. Strong sites often combine one *environment* (sky, paper, studio, night city) with one *object language* (glass, stamps, dials, lenses). Name the metaphor and let it generate details: a "lens" brand gets a loupe logo, a loader where the lens opens, a scanning transition. Write down why you chose it in one line; tell the user. ## 3. Colour - **Derive, don't default.** Start from the brand's existing colours, the product's subject, and the reference. Never ship a framework's default palette. - **Structure**: canvas (the page), surface (cards), ink (text, 2–3 steps), one accent, status colours (success/warning/danger) tuned to the palette, a line colour at low alpha. - **Warm neutrals beat pure greys.** Off-white canvases (e.g. a cream around `#f2efe5`) and warm near-black ink (e.g. `#2b2927`) read as crafted; pure `#fff`/`#000` read as default. - **One accent, used with intent**: primary buttons, key highlights, focus rings, a few accent words. If everything is accented, nothing is. - **Pastel accents need contrast care.** If the accent is soft (e.g. a pastel apricot), put ink-coloured text on it, and create a darker "accent-ink" shade for any small accent text so it passes contrast. - **Status colours** should be desaturated to sit in the palette (a sage green, a burnt amber, a brick red), not neon. - Put colours in CSS custom properties (tokens) and map them into the styling system; components only use tokens. ## 4. Typography - **Pairing**: an expressive display face for headings + a calm grotesk for UI and body. A serif display with an *italic second line or italic accent word* is a strong default for warm brands; a tight grotesk display suits technical brands. - **Scale with confidence**: hero headlines are big (64–110px desktop), tight leading (0.95–1.05), slight negative tracking. Body 15–18px with 1.5–1.6 line height, muted ink. - **Italic as emphasis**, not bold. Split headlines into a plain line and an italic line. - **Numbers**: tabular figures; big numerals in the display face look editorial. - Load fonts with the framework's font loader (no layout shift). At most two families plus a mono if genuinely needed. ## 5. Layout and rhythm - Generous vertical rhythm (100–160px between sections on desktop), narrow measure for text (≤ 600px), wide for product visuals. - Centered headline sections alternate with asymmetric splits (text left / live UI right). - Big rounded "panels" (24–32px radius) that hold an environment (painted sky, photo, texture) with glass UI floating inside are a reliable premium device. - Let decorative elements break the grid (branches overlapping a panel edge), but never cover content or interactive UI; put them behind the panel if they collide. - Mobile is designed, not squashed: re-order, reduce decoration, keep tap targets ≥ 44px, no horizontal scroll. ## 6. Copy - Headlines are specific and human: what the product does for the reader, in their words. Avoid category slogans. - Short sentences. No hype words ("revolutionary", "unlock", "supercharge", "seamless", "leverage"). - Every section heading should make sense on its own, without a label above it. - Microcopy is part of the design: empty states, loading labels, errors ("A passing cloud"). ## 7. Honesty - Never invent testimonials, logos, user counts, ratings or metrics. Leave them out or ask. - Sample data in demos uses obviously fictional names and `.example` domains, and is labelled as sample where it could be mistaken for real. - Label estimates as estimates. Don't claim integrations or features that don't exist. ## 8. The anti-slop list (and why) | Don't | Why | Do instead | |---|---|---| | Icon libraries (lucide, heroicons, etc.) | Instantly recognisable; makes every site look the same | Draw a custom SVG set in one hand (`assets.md`) | | Prebuilt component kits used as-is | Same shapes and spacing as thousands of sites | Write components for the brand; restyle any library you must keep | | Eyebrow/kicker tags above titles ("FEATURES", "Built for:", "STUDIO / OVERVIEW") | Reads as AI template filler and clutters the hierarchy | Let the heading carry the meaning; put context in body copy | | Purple-blue gradients, glowing orbs, glassmorphism with no environment behind it | The default "AI startup" look | Glass only over a real painted/photographic environment; palette from the brand | | Emoji as icons or bullets | Cheapens the voice | Custom glyphs or nothing | | Mock UIs drawn as grey boxes | Feels fake and generic | Render the product's real components with sample data, animated and interactive | | Fake social proof | Damages trust, can be screenshotted | Omit, or show honest proof (live tool results, real numbers) | | Animating everything on load | Noise; slows perception | Motion with purpose: reveal, explain, reward | | Default fonts and default colours | Unauthored | Chosen pairing, derived palette | | Generic stock photos | Interchangeable | Custom procedural art, or precise generation prompts | Shell cwd was reset to C:\Users\ISHAAN\AppData\Roaming\Claude\scratch-workspaces\3533f088-c8d0-458d-b705-5218a2e4535a\b4994459-b278-418a-8465-5d51f726134a\scratch-2026-10-10-5250ed

$ cd "C:/Users/ISHAAN/.claude/skills/ishaan-ui" && cat references/motion.md references/components.md

# Motion: loaders, transitions, blur, reveals, scroll, interaction ## Contents 1. Motion personality 2. The intro loader 3. Page transitions 4. Appearing: reveals and soft blur 5. Scroll-triggered and scroll-driven sections 6. Interactive components and micro-interactions 7. Loading states 8. Performance and pitfalls (read this) --- ## 1. Motion personality Decide it once: e.g. "slow, eased, soft blur; springy only on small things you touch". Defaults: - Ease: `cubic-bezier(.22,1,.36,1)` for most things; `cubic-bezier(.76,0,.24,1)` for sheets and curtains; springs (stiffness ~500, damping ~30–40) for small UI like a sliding active indicator. - Durations: micro 150–300ms, reveals 600–900ms, sheets 400–600ms, intro ≤ 3s total. - Everything respects `prefers-reduced-motion`: render the final state, no transforms. ## 2. The intro loader Purpose: a branded first impression that **tells the metaphor**, plays once per session, and never blocks a repeat visitor. Pattern ("the mark opens"): 1. Canvas-coloured overlay. The logo mark draws itself (SVG `pathLength` 0→1), the wordmark fades up from a slight blur. 2. The mark's interior fills with the brand's art (e.g. a sky inside a lens). 3. The overlay is revealed *through* the mark: animate a radial mask hole from 0 to ~160vmax centred on the mark (`mask-image: radial-gradient(circle at X Y, transparent R, #000 R+1px)` with a motion value). 4. Mark `sessionStorage` and unmount. Rules: decide visibility **before first paint** with a tiny inline script that sets `html[data-intro="done"]` when it has played or reduced motion is on, and hide the overlay with CSS on that attribute (no flash, no hydration mismatch). Lock scroll only while it plays. Hide it in print. Make it brand-specific: a stamp being pressed, a page being turned, a dial sweeping, ink pouring: whatever the metaphor suggests. ## 3. Page transitions Purpose: continuity and a sense of place, **without slowing navigation**. Related to the loader in vocabulary, different in shape. Pattern ("the sheet / the scan"): - Intercept internal link clicks (capture phase; skip modifier keys, new tabs, downloads, same-path hash links). **Call `router.push` immediately**: the animation dresses the wait, it must never add to it. - A canvas-coloured sheet rises with a curved leading edge (animate border-radius from a large ellipse to 0), shows the destination name in the display face, while a small brand object (e.g. a loupe) travels a hairline. - When the pathname changes (the new route rendered), wait only for the sheet to finish rising (~400ms minimum), then lift it away with a curved trailing edge. - If loading is slow, keep the sheet up and switch the object into a looping "scanning" motion with a quiet "Loading…": the transition becomes the loader. - Treat "the route changed away from where the click happened" as arrival, so redirects (e.g. to login) also lift the sheet. Add a long fallback timeout. - **Prefetch** on `pointerenter`, `touchstart` and `focusin` of internal links. - Skip entirely for reduced motion. ## 4. Appearing: reveals and soft blur - Section content: fade + 14–24px rise + blur(6px→0) on enter, once, staggered 60–100ms. - Headlines: masked word rise, or the **scroll-fill**: letters of the italic line ink from a pale tone to full ink as the line scrolls from 90% to 45% of the viewport. - Panels with art: scale 1.04→1 crossfade when content changes. - Glass appears with backdrop blur already applied; don't animate `backdrop-filter`. - Data visuals animate their value: dials sweep (stroke-dashoffset transition), numerals count up, gauges fill. ## 5. Scroll-triggered and scroll-driven sections Use 2–3 per landing page, each one teaching the product by letting the visitor *do* the core action. - **Sticky stage**: section height 300–420vh, inner container `sticky top-0 h-[100svh]`; map `scrollYProgress` to a step or a continuous value. - **Story in steps**: left list of steps (active expands, others dim); right stage changes scene per step. - **Live re-scoring**: scrolling applies improvements one by one and the real score UI re-computes and animates; clicking takes manual control ("Back to scroll mode" link). - **Typed file / config playground**: lines appear as you scroll; real logic re-evaluates the result per line; lines are clickable to toggle. - **Accordion that auto-advances** while in view, pauses on hover, with a hairline progress bar on the active item. - Mobile: drop stickiness (render the same content in flow) but keep the interactivity. - Reduced motion: show the final state, keep click interactivity. ## 6. Interactive components and micro-interactions - Magnetic primary buttons (small spring pull toward the pointer), 1px press on active. - Cursor-following warm spotlight inside cards (`radial-gradient` at pointer position). - Icon medallions that tilt (−8deg) and scale on card hover, with a spring curve. - Shared-layout "bead" behind the active nav/dock item and segmented controls (`layoutId`). - Tooltips/name-tags that slide out of glass on hover. - Pointer-driven 3D tilt (±2–3deg) on a hero object such as an auth postcard; mouse only. - Toggle pills that pop (scale 0.8→1 spring) when their state changes. - A delete icon whose lid lifts on hover; a compass that rotates when its menu opens. Every icon can have one tiny behaviour. ## 7. Loading states (never a blank screen) - Route-level skeleton in the **page's own shape** (glass panes, shimmer blocks matching cards and lists) plus a small brand-object loader line ("Opening your studio…"). - In-tool async work: a "working" checklist where steps go up next → in process (spinner) → done (check), paced by a timer while the request runs. - Buttons show a spinner and a verb ("Signing out…", "Saving…") and disable. - Optimistic UI where safe; graceful errors with a way to retry. ## 8. Performance and pitfalls (read this) - **Never animate live SVG filters** (feTurbulence/displacement) on large areas, they stall rendering. Pre-render art to WebP (`scripts/render-art.mjs`). - **`backdrop-filter` breaks under some ancestors**: an ancestor with `filter`, `opacity < 1`, `mask`, or `backdrop-filter` becomes the "backdrop root", so glass inside blurs nothing. Don't put blur/filter animations on containers of glass; animate opacity/transform only, or animate the glass element itself. - **Body background paints above negative z-index**: a `fixed -z-10` backdrop disappears behind the body background. Use `z-0` for the backdrop and `relative z-10` for content. - **Hydration**: values computed differently on server and client (floating-point SVG coordinates, `Date.now()`, locale dates, local hour) cause mismatches. Round coordinates, compute time-dependent text after mount (via `setTimeout(…,0)`, since `requestAnimationFrame` pauses in background tabs). - **Decorative layers must not cover UI**: put overlapping art behind panels (lower z) and clip/fade it with a mask so it never trails into the next section. - Sticky scroll sections are measured in vh; tall headless screenshots distort them, so verify those in a normal-height browser. - Prefer transforms and opacity; avoid animating layout. Respect reduced motion. # Components: build them for the brand Write every component yourself. These are proven patterns; adapt their shape to the visual idea. ## Surfaces - **glass**: translucent warm-white gradient, `backdrop-filter: blur(28px) saturate(1.4)`, 1px white/70 border, inset top highlight, long soft shadow. Only over an environment (art, blurred sky), never over flat colour. - **glass-strong**: more opaque, for dense content and popovers. - **glass-inset**: white/40 with inner shadow, for inputs, chips, icon wells. - Radii: 12px controls, 18–24px cards, 28–32px panels. - Provide `prefers-reduced-transparency` and print fallbacks (solid surface). ## Buttons - Primary: accent fill, ink text, inset top highlight, small accent-tinted shadow, 1px press. Secondary: glass-inset or a warm neutral fill. Rectangular with soft corners (10–14px) reads more premium than full pills for most brands. - Every async button: spinner + present-tense verb, disabled while busy. ## Inputs - glass-inset, 48px tall, 12px radius, accent focus ring (`0 0 0 4px accent/30%`). - Big "front door" input for the product's core action: a glass bar with the tool's own glyph in a well, a primary action, and quiet example chips ("try …") under it. ## Navigation - **Marketing nav**: transparent → floating glass pill on scroll (animate max-width); hover mega-menu in the display face; signed-in visitors get "Your studio" + an avatar menu (Overview, Saved items, Sign out). - **App dock**: vertical glass dock fixed left, centered; logo (with "Back to home" name-tag), primary destinations, divider, tools popover, avatar menu (Home, All tools, Sign out). Bottom dock on mobile. A `layoutId` bead marks the active item. - There is always a visible way home and a way to sign out from every page. ## Headings - Masthead: big display heading with an italic turn and a one-line lede. **Nothing above it.** - Section headings: two lines, second italic; optionally scroll-filled. ## Data visuals (custom, never default chart skins) - **Bezel dial**: 60 hairline ticks around a ring, score arc in a status tone, numeral in the display face, sweeping + counting on change. - **Ink-well gauge**: glass test-tube fill...