56 results available
Sign in
Skills directory

premium-frontend-ui

github

·

Last changed
Hardened

This skill has been hardened by Chainguard

Last changed

This version passed the hardening gate. Hardening applied 13 targeted changes and preserved all other text. Classified findings before hardening: 0. Classified findings closed: 0. Classified findings remaining: 0. Unclassified scanner findings remaining: 1. Review findings closed: 11. Review findings remaining: 1.


Open before hardening

None

Open after hardening

None


Expand
File
Group
Subtype
Severity
Status

No findings available

0 findings


SKILL.md

Immersive Frontend UI Craftsmanship

As an AI engineering assistant, your role when building premium frontend experiences 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.


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)

The user's first interaction must set expectations.

  • Implementation: Prefer progressive rendering so content is readable before assets finish loading. Add a lightweight preloader component that handles asset resolution (fonts, initial images, 3D models) only when heavy 3D models or large assets require one, keep it short, and let users skip it.
  • 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. Give the parent element an accessible label with the full text, and hide the split spans from screen readers.
  • 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: By default, output sticky headers that react to scroll direction (hide on scroll down, reveal on scroll up), unless the user prefers a static navbar. Keep the focused element visible when the header hides.
  • Interactivity: Include hover states that reveal rich content (e.g., mega-menus that display image previews of the hovered link). Make these menus open and operate with keyboard focus and touch as well as hover.

3. The Motion Design System

Animation is not an afterthought; it is the connective tissue of a premium site. By default, when the user asks for premium or immersive output, 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. Keep the native cursor available and keep focus indication visible.
  • 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: Where appropriate, recommend or implement highly specified variable fonts or premium typefaces over system defaults. Prefer self hosting fonts and assets, use font display swap with system font fallbacks, and respect font licenses.
  • 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 all motion that is not essential, including scroll smoothing, parallax, pinning, horizontal scroll, preloader transitions, magnetic buttons and custom cursors, in @media (prefers-reduced-motion: no-preference). Also check the reduced motion setting in script before starting GSAP or Lenis, and preserve native keyboard, focus and anchor navigation. 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, installed only from the official npm registry under their official package names with exact pinned versions and a committed lockfile, adding only the libraries the requested features need:

For React / Next.js Targets

  • Structure the application to support Framer Motion for layout transitions and spring physics.
  • Recommend Lenis, using the current package published under the plain lenis name rather than the deprecated studio freight scope, 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.
  • Prefer installing vanilla Lenis from the npm registry with a pinned version and a committed lockfile, for scroll smoothing. If a CDN script tag is required, pin an exact version and include a subresource integrity hash and an anonymous cross origin attribute. Apply the same rule to any GSAP or SplitType script loaded from a CDN.
  • 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," apply these defaults, respecting existing project conventions and confirming with the user before adding new dependencies, preloaders, scroll smoothing, or custom cursors:

  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.

Install

Install with chainctl
chainctl skill install public/github/premium-frontend-ui:latest
Get started with chainctl
View source

Harden your own skills

Bring Chainguard's hardening pipeline to your first-party skills — custom rulesets, automated remediation, full audit trail.

Provenance

Upstream sourcehttps://github.com/github/awesome-copilot
Upstream commit2201a49dd6f972ac4f685d03361d58c9c9206690
OCI reference

skills.chainreg.biz/public/github.com/github/skills/premium-frontend-ui:latest

License

MIT

Files

HARDENING.md

LICENSE

SKILL.md


The trusted source for open source

Talk to an expert
PrivacyTerms

Product

Chainguard ContainersChainguard LibrariesChainguard VMsChainguard OS PackagesChainguard ActionsChainguard Agent SkillsIntegrationsPricing
© 2026 Chainguard, Inc. All Rights Reserved.
Chainguard® and the Chainguard logo are registered trademarks of Chainguard, Inc. in the United States and/or other countries.
The other respective trademarks mentioned on this page are owned by the respective companies and use of them does not imply any affiliation or endorsement.