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 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.

<!-- PORTABILITY:START -->

Verification Protocol

Before claiming "skill applied successfully":

1. Pass/fail: The Premium Frontend Ui guidance is tied to a concrete route, component, screen, or design artifact. 2. Pass/fail: Component states cover loading, empty, error, success, and responsive breakpoints where applicable. 3. Pass/fail: Accessibility, visual hierarchy, and interaction behavior are reviewed against the shared component rubric. 4. Pressure-test scenario: Review the component on a narrow mobile viewport, keyboard-only path, and slow-loading state. 5. Success metric: Zero generic UI approval; every approval cites rendered behavior or source evidence.

Cross-Client Portability

This skill is written to stay usable across GitHub Copilot, Claude Code, Codex, and Gemini CLI.

• GitHub Copilot: keep the folder in a Copilot-visible skill or plugin path, or wrap the workflow as project instructions if the host does not support portable skill folders directly.
• Claude Code: keep the folder in a local skills directory or a compatible plugin or marketplace source.
• Codex: install or sync the folder into $CODEX_HOME/skills/<skill-name> and restart Codex after major changes.
• Gemini CLI: this repository generates a project command named /skills:premium-frontend-ui from this skill. Rebuild commands with python scripts/export-gemini-skill.py premium-frontend-ui and then run /commands reload inside Gemini CLI.

<!-- PORTABILITY:END -->

<!-- MCP:START -->

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.

<!-- MCP:END -->

Related Skills

• frontend-design: Use it when the workflow also needs UI composition and front-end design direction.
• web-design-reviewer: Use it when the workflow also needs browser-based UI review and responsive QA.
• stitch-design: Use it when the workflow also needs turning interface designs into implementation-ready assets.
• canvas-design: Use it when the workflow also needs visual composition and presentation-ready diagram work.

Changelog

[2026-04-25] - Version 1.2 Verification Protocol Refresh

Added

• Added a Verification Protocol section with skill-specific pass/fail checks, one pressure-test scenario, and a measurable success metric.
• Added guidance to leverage native parallel subagent dispatch and 200k+ context windows where available.
• Added or referenced the shared Component Review Rubric for frontend component review.

Changed

• Updated SKILL.md frontmatter to version: "1.2" and last_updated: 2026-04-25.
• Reframed activation guidance toward symptom -> action triggers and standardized two-stage review wording where applicable.

[2026-04-24] - Version 1.1 Refresh

Changed

• Updated the SKILL frontmatter version to 1.1 for the 2026-04-24 catalog refresh.

All notable changes to the premium-frontend-ui skill will be documented in this file.

[2026-04-24] - Skill Refresh

Changed

• Standardized the SKILL frontmatter with version metadata, last-updated date, tags, and a concise catalog description.
• Reformatted the portability and MCP guidance with a preferred server line, a copy-paste fallback prompt, and consistent bullet lists.
• Added a catalog-standard Anti-Patterns section and refreshed the Related Skills links at the end of the skill.

[2026-04-24] - Upstream Metadata Refresh

Changed

• Added upstream author metadata from https://github.com/github/awesome-copilot commit 63d08d51f792d53feec8c1c06897cee870e83c18.

Tested

• Confirmed the current upstream change for this skill is limited to SKILL.md frontmatter metadata.

[2026-04-04] - Initial Import and Portability Upgrade

Added

• Imported this skill from https://github.com/github/awesome-copilot at skills/premium-frontend-ui.
• Added cross-client portability guidance for GitHub Copilot, Claude Code, Codex, and Gemini CLI.
• Added the repo-standard MCP or no-MCP fallback guidance for this skill.

Changed

• Rewrote the activation description and opening guidance to be host-neutral instead of Copilot-specific.

Tested

• Validated SKILL.md frontmatter and Gemini command export readiness with python scripts/validate-skills.py.