# Premium Frontend UI > Premium frontend UI direction for immersive, high-performance web experiences with strong motion, typography, and visual systems. Use when building high-end landing pages, polished interactive components, or portfolio-style sites. - Skill: `bg-szy/premium-frontend-ui` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add bg-szy/premium-frontend-ui` - Raw SKILL.md: https://api.skillmd.com/api/skills/bg-szy/premium-frontend-ui/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Design & Media - Author: bg-szy (https://skillmd.com/u/bg-szy) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/bg-szy/premium-frontend-ui --- # Immersive Frontend UI Craftsmanship When building premium frontend experiences, your role goes beyond outputting functional HTML and CSS. You must architect **immersive digital environments**. This skill provides the blueprint for generating highly intentional, award-level web applications that prioritize aesthetic quality, deep interactivity, and flawless performance. When a user requests a high-end landing page, an interactive portfolio, or a specialized component that requires top-tier visual polish, apply the following rigorous standards to every line of code you generate. --- - Leverage native parallel subagent dispatch and 200k+ context windows where available. ## 1. Establishing the Creative Foundation Before generating layout code, ensure you understand the core emotional resonance the UI should deliver. Do not default to generic, unopinionated code. Commit to a strong visual identity in your CSS and component structure: - **Editorial Brutalism**: High-contrast monochromatic palettes, oversized typography, sharp rectangular edges, and raw grid structures. - **Organic Fluidity**: Soft gradients, deeply rounded corners, glassmorphism overlays, and bouncy spring-based physics. - **Cyber / Technical**: Dark mode dominance, glowing neon accents, monospaced typography, and rapid, staggered reveal animations. - **Cinematic Pacing**: Full-viewport imagery, slow cross-fades, profound use of negative space, and scroll-dependent storytelling. --- ## 2. Structural Requirements for Immersive UI When scaffolding a page or generating core components, include the following architectural layers to transform a standard page into an experience. ### 2.1 The Entry Sequence (Preloading & Initialization) A blank screen is unacceptable. The user's first interaction must set expectations. - **Implementation**: Generate a lightweight preloader component that handles asset resolution (fonts, initial images, 3D models). - **Animation**: Output code that transitions the preloader away fluidly—such as a split-door reveal, a scale-up zoom, or a staggered text sweep. ### 2.2 The Hero Architecture The top fold must command attention immediately. - **Visuals**: Output code that implements full-bleed containers (`100vh`/`100dvh`). - **Typography Engine**: Ensure headlines are broken down syntactically (e.g., span wrapping by word or character) to allow for cascading entrance animations. - **Depth**: Utilize subtle floating elements or background clipping paths to create a sense of scale and depth behind the primary copy. ### 2.3 Fluid & Contextual Navigation - **Implementation**: Do not generate standard static navbars. Output sticky headers that react toscroll direction (hide on scroll down, reveal on scroll up). - **Interactivity**: Include hover states that reveal rich content (e.g., mega-menus that display image previews of the hovered link). --- ## 3. The Motion Design System Animation is not an afterthought; it is the connective tissue of a premium site. Always implement the following motion principles: ### 3.1 Scroll-Driven Narratives Generate code utilizing modern scroll libraries (like GSAP's ScrollTrigger) to tie animations to user progress. - **Pinned Containers**: Create sections that lock into the viewport while secondary content flows past or reveals itself. - **Horizontal Journeys**: Translate vertical scroll data into horizontal movement for specific galleries or showcases. - **Parallax Mapping**: Assign subtle, varying scroll-speeds to background elements, midground text, and foreground imagery. ### 3.2 High-Fidelity Micro-Interactions The cursor is the user's avatar. Build interactions around it. - **Magnetic Components**: Write logic that calculates the distance between the mouse pointer and a button, pulling the button towards the cursor dynamically. - **Custom Tracking Elements**: Generate custom cursor components that follow the mouse with calculated interpolation (lerp) for a smooth drag effect. - **Dimensional Hover States**: Use CSS Transforms (`scale`, `rotateX`, `translate3d`) to give interactive elements weight and tactile feedback. --- ## 4. Typography & Visual Texture The aesthetics of your generated code must reflect premium craftsmanship. - **Type Hierarchy**: Enforce massive contrast in scale. Headlines should utilize extreme sizing (`clamp()` functions spanning up to `12vw`), while body copy remains incredibly crisp (`16px-18px` minimum). - **Font Selection**: Always recommend or implement highly specified variable fonts or premium typefaces over system defaults. - **Atmospheric Filters**: Implement CSS/SVG noise overlays (`mix-blend-mode: overlay`, opacity `0.02 - 0.05`) to remove digital sterility and add photographic grain. - **Lighting & Glass**: Utilize `backdrop-filter: blur(x)` combined with ultra-thin, semi-transparent borders to create modern, frosted-glass depth. --- ## 5. The Performance Imperative A beautiful site that stutters is a failure. Enforce strict performance guardrails in all generated code: - **Hardware Acceleration**: Only animate properties that do not trigger layout recalculations: `transform` and `opacity`. Code that animates `width`, `height`, `top`, or `margin` should be fiercely avoided. - **Render Optimization**: Apply `will-change: transform` intelligently on complex moving elements, but remove it post-animation to conserve memory. - **Responsive Degradation**: Wrap custom cursor logic and heavy hover animations in `@media (hover: hover) and (pointer: fine)` to ensure pristine performance on touch devices. - **Accessibility**: Wrap heavy continuous animations in `@media (prefers-reduced-motion: no-preference)`. Never sacrifice user accessibility for aesthetic flair. --- ## 6. Implementation Ecosystem When the user asks you to implement these patterns, leverage industry-standard libraries tailored to their framework: ### For React / Next.js Targets - Structure the application to support **Framer Motion** for layout transitions and spring physics. - Recommend **Lenis** (`@studio-freight/lenis`) for smooth scrolling context. - Implement **React Three Fiber** (`@react-three/fiber`) if webGL or 3D interactions are requested. ### For Vanilla / HTML / Astro Targets - Rely heavily on **GSAP** (GreenSock Animation Platform) for timeline sequencing. - Utilize vanilla **Lenis** via CDN for scroll hijacking and smoothing. - Use **SplitType** for safe, accessible typography chunking. --- ## Summary of Action Whenever you receive a prompt to "Build a premium landing page," "Create an Awwwards-style component," or "Design an immersive UI," you must automatically: 1. Wrap the output in a robust, scroll-smoothed architecture. 2. Provide CSS that guarantees perfect performance using composited layers. 3. Integrate sweeping, staggered component entrances. 4. Elevate the typography using fluid scales. 5. Create an intentional, memorable aesthetic footprint. ## Component Review Rubric Reference Apply the shared [Component Review Rubric](../frontend-design/SKILL.md#component-review-rubric) before approving premium UI components, then apply this skill's visual craft bar. ## Anti-Patterns - Starting from a generic template without adapting it: The output may look polished but still miss the real audience or medium. - Ignoring final render or export review: Layout bugs often appear only after the asset is opened in its destination tool. - Fixing content and presentation in one pass: It becomes hard to tell whether a problem is structural or visual. ## Verification Protocol Before claiming the `premium-frontend-ui` workflow succeeded: 1. Pass/fail: The request matches this skill's documented activation boundary. 2. Pass/fail: Required inputs, dependencies, and safety checks were resolved or reported as blockers. 3. Pass/fail: The narrowest relevant workflow was completed without inventing unavailable tools or results. 4. Pass/fail: Output was checked with the most relevant local test, inspection, render, or source evidence. 5. Pressure test: Repeat the decision with the preferred integration unavailable and confirm the fallback remains safe and actionable. 6. Success metric: The result, evidence, and any unverified limitation are explicit enough for another agent to reproduce. ## Cross-Client Portability This skill is written to stay usable across GitHub Copilot, Claude Code, and Codex. - GitHub Copilot: keep the folder in a Copilot-visible skill path or wrap the workflow in project instructions when folder discovery is unavailable. - Claude Code: keep the folder in a local skills directory or a compatible plugin source. - Codex: install or sync the folder into `$CODEX_HOME/skills/premium-frontend-ui` and restart Codex after major changes. ## MCP Availability And Fallback Preferred MCP Server: None required - Fallback prompt: "Use the Immersive Frontend UI Craftsmanship skill without MCP. Rely on the local `SKILL.md`, bundled references or scripts, and manual verification. Show the exact commands, evidence, and final checks you used before concluding." - If the current host does not expose a matching server, use the bundled references, scripts, native toolchain, and manual workflow already described in this skill. - Treat direct local verification, rendered output, logs, tests, or screenshots as the fallback evidence path before completion. ## Related Skills - [frontend-design](../frontend-design/SKILL.md): Use it when the workflow also needs UI composition and front-end design direction. - [web-design-reviewer](../web-design-reviewer/SKILL.md): Use it when the workflow also needs browser-based UI review and responsive QA. - [stitch-design](../stitch-design/SKILL.md): Use it when the workflow also needs turning interface designs into implementation-ready assets. - [canvas-design](../canvas-design/SKILL.md): Use it when the workflow also needs visual composition and presentation-ready diagram work.