Ivx Cf Jeremylongshore Claude Code Plugins Plus Skills Top Design

Top-Design: Award-Winning Digital Experiences

Create websites and applications at the level of world-class digital agencies. This skill embodies the craft of studios that consistently win FWA, Awwwards, CSS Design Awards, and Webby Awards.

Core Principle

Every pixel is intentional -- nothing default, nothing accidental. The agencies you are emulating -- Locomotive, Studio Freight, AREA 17, Active Theory, Hello Monday -- share a common DNA: typography IS the design (not decoration, but architecture), motion creates emotion (animation serves narrative, not novelty), white space is a weapon (tension through restraint), and performance is non-negotiable (60fps or nothing).

The foundation: What separates 10/10 from 8/10 is not incremental improvement but a qualitative leap. An 8/10 design has good typography, nice colors, and smooth animations. A 10/10 design has typography that makes you gasp, colors that feel invented for this specific project, and animations that tell stories. The gap is not skill -- it is intention. Every decision at the 10/10 level answers the question: "Does this serve the experience, or is it just filling space?"

Scoring

Goal: 10/10. When reviewing or creating digital experiences, rate them 0-10 using the rubric below. A 10/10 means the design would be featured on Awwwards. Always provide the current score and specific improvements needed to reach 10/10.

Scoring Rubric

Category Scoring (Each 0-10)

TYPOGRAPHY (Weight: 25%)

VISUAL COMPOSITION (Weight: 25%)

MOTION & INTERACTION (Weight: 20%)

COLOR & ATMOSPHERE (Weight: 15%)

DETAILS & CRAFT (Weight: 15%)

Quick Score Formula

Total = (Typography x 0.25) + (Composition x 0.25) + (Motion x 0.20) + (Color x 0.15) + (Details x 0.15)

The Seven Pillars of 10/10 Design

1. Typography as Architecture

Core concept: Typography is not decoration layered onto a design -- it IS the design. The typeface you choose, the scale you set, and the tracking you refine dictate everything else: color palette mood, animation style, spacing rhythm, and overall personality. When someone scrolls past your hero and does not pause, your typography is not working.

Why it works: Dramatic scale contrast creates immediate visual hierarchy that communicates even when content is blurred or viewed from across the room. Large display type with tight tracking commands attention like architecture commands a skyline, while intimate body text draws readers into the content. This tension between monumental and personal is what makes people stop scrolling.

Key insights:

• Massive scale contrast is non-negotiable -- the ratio between display and body should be at minimum 10:1 (e.g., 180px headline / 14px body), with viewport-filling type at the extreme end making body text feel intimate
• Negative tracking on large type (-0.02em to -0.05em) tightens display text into cohesive visual units, while generous line-height for body (1.5-1.7) ensures readability
• Font selection defines tier -- display fonts should come from premium foundries (Pangram Pangram, Dinamo, Grilli Type, Klim, Commercial Type) or quality Google alternatives (Space Grotesk, Instrument Serif, Fraunces); never Inter, Roboto, Arial, or system-ui for hero experiences
• Variable fonts enable weight animation on hover states and transitions, adding dynamism without layout shift
• Optical alignment over mathematical alignment -- human perception is imperfect, so text must be adjusted visually, not just numerically
• Control every line break on headlines -- text that breaks beautifully requires manual intervention at key breakpoints

Product applications:

Copy patterns:

• Display: single powerful statement, 3-7 words maximum
• Subhead: one sentence that contextualizes the display type
• Body: 16-18px minimum, generous line-height, moderate measure (45-75 characters)
• The "typography stare test": blur your eyes -- does the type hierarchy still read? If everything looks the same importance when blurred, you have failed

Ethical boundary: Typography choices should enhance readability and accessibility, not sacrifice legibility for aesthetic novelty. Ensure body text meets WCAG contrast requirements and remains readable at standard viewing distances.

See: references/typography.md for font pairing strategies, type scale systems, and advanced CSS typography.

2. Layout & Composition

Core concept: Master the grid so you can break it with intention. Every violation should feel deliberate, not accidental. The rhythm of density and breathing room -- full-viewport hero, intimate text section, massive single word, dense grid -- creates a reading experience that holds attention.

Why it works: White space is not empty space -- it is active design material that creates tension, controls pacing, and makes viewers lean in. Asymmetric layouts generate visual energy that centered, symmetrical compositions cannot achieve. When elements overlap, bleed, or extend beyond their containers with intention, the design feels alive and confident rather than constrained.

Key insights:

• White space as a weapon -- amateurs fill every gap with content, professionals use padding liberally, 10/10 designers use white space to create tension that controls the reader's eye
• Asymmetric balance creates interest -- offset elements from center (e.g., one column offset in a 12-column grid), let images bleed and extend beyond containers
• Unexpected scale shifts create rhythm -- the alternation between massive and intimate, dense and sparse, creates a narrative pacing that prevents monotony
• Elements should overlap, bleed, or extend with intention -- breaking the container signals confidence and craftsmanship
• The grid paradox -- a strong underlying grid is necessary precisely so you can break it meaningfully; without the grid, breaks are just chaos
• The screenshot test -- if someone would not screenshot a section and share it, you are missing signature moments

Product applications:

Copy patterns:

• Hero: position text off-center with intentional alignment to grid
• Sections: alternate between full-width immersion and contained reading
• Cards: vary sizes within grids -- not everything needs to be the same dimensions
• Images: mix full-bleed, contained, and overlapping treatments

Ethical boundary: Layout experimentation must not compromise navigation clarity or content accessibility. Users should always understand where they are, how to move forward, and how to access critical information regardless of compositional choices.

See: references/layout-systems.md for grid frameworks, breakpoints, and responsive patterns.

3. Motion & Animation

Core concept: Every animation must answer "Why does this move?" Motion is not polish applied at the end -- it is core to the design, prototyped early and developed alongside visual design. The three laws of elite motion are: purpose over decoration, custom curves (never linear), and orchestration over isolation.

Why it works: Choreographed motion creates a cinematic experience that guides attention, communicates hierarchy, and creates emotional resonance. When elements animate in relationship to each other rather than independently, the result feels cohesive and intentional. Custom easing curves (exponential, quartic) give movement a physical quality that default browser easing cannot achieve.

Key insights:

• Custom easing is mandatory -- ease, ease-in, ease-out, and linear are banned; use cubic-bezier(0.16, 1, 0.3, 1) (expo out), cubic-bezier(0.25, 1, 0.5, 1) (quart out), cubic-bezier(0.87, 0, 0.13, 1) (expo in-out)
• Page load choreography follows a strict timeline -- background/structure (0-200ms), hero title words staggered (200-600ms, 80ms stagger), subtitle (400-800ms), navigation cascade (600-900ms), supporting elements (800-1200ms)
• Scroll-triggered sequences reveal elements as they enter viewport -- not all at once; parallax used sparingly and only on non-essential elements
• Pinned sections for storytelling moments and horizontal scroll for galleries (with clear affordance) create immersive reading experiences
• Default browser scroll is unacceptable -- use Lenis or Locomotive Scroll for smooth, custom scroll behavior
• 60fps is non-negotiable -- if an animation drops frames, simplify or remove it

Product applications:

Copy patterns:

• Reveal: text lines slide up individually with stagger (not fade in as a block)
• Hover: elements respond with custom cursor, scale shift, or color transition
• Scroll: content reveals progressively, never all at once
• Transition: pages morph rather than cut or fade

Ethical boundary: Motion must never block interaction, cause motion sickness, or prevent users from accessing content. Always respect prefers-reduced-motion and ensure all content is accessible without animation. Animations longer than 1.2s require clear justification.

See: references/animation-patterns.md for scroll animations, page transitions, and micro-interactions with code.

4. Color & Contrast

Core concept: Color should feel invented for each specific project -- not pulled from a generic palette generator. The three approaches are monochromatic tension (95% one dominant color, 5% accent that pops), bold signature (own a color combination and make it unmistakable), and contextual shifting (color responds to content, with sections having distinct palettes).

Why it works: Color creates atmosphere before a single word is read. When colors feel owned by a specific project, they become part of the brand's identity. Pure black (#000000) and pure white (#ffffff) feel digital and lifeless; slightly warm variants (#0a0a0a, #fafaf9) feel physical and considered. The restrained use of a single accent color creates moments of surprise that draw the eye exactly where intended.

Key insights:

• Never use pure black or pure white -- warm variants create a physical quality that pure digital colors lack
• The functional color hierarchy -- text-primary, text-secondary (60% opacity), text-tertiary (40% opacity), surface, border (10% opacity) -- creates consistent depth across all components
• Accent color creates moments of surprise -- a single strong accent (#ff4d00 or similar) used sparingly has more impact than a complex multi-color palette
• Contextual color shifts between sections signal content changes and create visual chapters
• The squint test -- squint at your design; if the important elements do not stand out through contrast alone, your color hierarchy is failing
• Colors must work in both light and dark contexts -- design the system, not individual instances

Product applications:

Copy patterns:

• Define CSS custom properties for your full color system: --color-dark, --color-light, --color-accent
• Build functional tokens on top: --color-text-primary, --color-text-secondary, --color-surface
• Use opacity-based variants (rgba(10, 10, 10, 0.6)) for consistent secondary/tertiary text
• Accent color appears on CTAs, links, and single-detail moments -- never everywhere

Ethical boundary: Color choices must meet WCAG 2.1 AA contrast requirements at minimum. Atmospheric design cannot come at the cost of readability for users with visual impairments. Test all color combinations with contrast checkers.

See: references/case-studies.md for agency technique breakdowns including color system analysis.

5. Scroll-Based Design

Core concept: Scroll is the primary interaction on the web, and it should feel designed, not default. The best digital experiences treat the scroll as a narrative device -- controlling pacing, creating reveals, building tension, and delivering signature moments tied to scroll position.

Why it works: Default browser scroll is mechanical and uniform, treating all content as equally important. Custom scroll behavior (via Lenis or Locomotive Scroll) creates a smooth, weighted feel that mirrors physical objects. When scroll position drives animations, reveals, and transitions, the user's movement through content becomes an active, participatory experience rather than passive consumption.

Key insights:

• Smooth scroll is the foundation -- implement Lenis or Locomotive Scroll for the weighted, physical scroll feel that every award-winning site uses
• Parallax must be purposeful -- used sparingly and only on non-essential decorative elements; never on text or critical content
• Pinned sections create storytelling beats -- locking a section in place while content transforms within it creates cinematic moments
• Horizontal scroll for galleries requires clear visual affordance so users know to scroll sideways
• Scroll-triggered reveals should be progressive -- elements enter as they become visible, creating a sense of discovery
• Scroll velocity can modulate animation speed -- fast scrolling compresses animations, slow scrolling expands them, creating a responsive feel

Product applications:

Copy patterns:

• Use data-scroll, data-scroll-speed, and data-scroll-direction attributes for declarative scroll behavior
• Implement intersection observers for lightweight scroll-triggered class toggling
• Reserve GSAP ScrollTrigger for complex, multi-step scroll-driven animations
• Always provide a non-scroll fallback for accessibility

Ethical boundary: Scroll hijacking that prevents users from scrolling at their own pace is hostile UX. Custom scroll should enhance the experience, not trap users. Always allow users to scroll freely through content, and never make scroll-driven animations mandatory for accessing information.

See: references/animation-patterns.md for scroll animation implementation patterns.

6. Performance & Loading

Core concept: Performance is not an optimization step -- it is a design constraint from day one. A beautiful animation that drops frames, a stunning font that causes layout shift, or a gorgeous image that takes three seconds to load all fail the craft test. 60fps is the floor, not the ceiling.

Why it works: Users perceive performance as quality. A site that loads instantly and scrolls fluidly feels premium, regardless of visual complexity. Conversely, a visually stunning site that stutters or delays feels broken. The best agencies achieve both visual ambition and technical performance by making performance a first-class design decision: choosing GPU-accelerated properties, subsetting fonts, optimizing images, and testing on real devices.

Key insights:

• Fonts must be subset and preloaded -- only include the glyphs you need, use font-display: swap or optional, and preload critical font files
• Images must be optimized -- use WebP/AVIF with fallbacks, implement responsive srcset, and lazy-load below-the-fold images
• Animations must be GPU-accelerated -- only animate transform and opacity; never animate width, height, top, left, or margin
• No layout shifts -- Cumulative Layout Shift (CLS) must be near zero; reserve space for images, fonts, and dynamic content
• LCP under 2.5s -- Largest Contentful Paint is the key metric; optimize the critical rendering path for the hero
• First contentful paint must feel instant -- use custom skeleton/loading animations as designed elements, not afterthoughts

Product applications:

Copy patterns:

• Audit with Lighthouse, targeting 90+ on all metrics
• Test on real devices, not just simulators -- simulators lie about performance and feel
• Implement loading="lazy" on all images below the fold
• Use will-change sparingly and only on elements about to animate
• Profile animations with Chrome DevTools Performance panel at 4x CPU throttle

Ethical boundary: Performance optimization must not strip away accessibility features, skip semantic HTML, or remove meaningful content. Fast-but-inaccessible is not a valid tradeoff.

See: references/technical-stack.md for libraries, tools, and performance optimization techniques.

7. Micro-Interactions

Core concept: The details that signal craft live in the 1% that most designers skip: custom cursors, branded selection colors, magnetic button effects, designed focus states, considered loading states, crafted error pages, and correct micro-typography. These details are the difference between professional and world-class.

Why it works: Micro-interactions create a sense that every pixel was considered. When a cursor changes on hover, when text selection has a branded color, when a button has a subtle magnetic pull, and when focus states are beautiful AND accessible, users feel the care embedded in the experience. These details compound -- individually subtle, collectively transformative.

Key insights:

• Custom cursor reflects brand personality -- cursor changes on interactive elements, with optional magnetic effect on buttons
• Selection colors are branded -- custom ::selection color that works well on all backgrounds
• Every link has a considered hover state -- images have scale or overlay treatment, cards transform meaningfully
• Focus states are visible AND beautiful -- focus indicators match brand aesthetic while remaining clearly visible for keyboard navigation
• Loading and empty states are designed -- custom skeleton animations, branded progress indicators, designed 404 pages, helpful error states
• Micro-typography is correct -- smart quotes, proper apostrophes, en/em dashes where appropriate, no orphans on headlines, text-wrap: balance on key text

Product applications:

Copy patterns:

• ::selection { background: var(--color-accent); color: var(--color-light); }
• cursor: none; on body with custom cursor div following mouse position
• Magnetic effect: calculate distance between cursor and button center, apply proportional transform
• Smart quotes: use “ and ” or configure your build tool to auto-convert

Ethical boundary: Micro-interactions must enhance usability, not hinder it. Custom cursors must remain functional and visible. Focus states must meet accessibility requirements -- beauty cannot replace visibility. Designed error states must be genuinely helpful, not just clever.

See: references/case-studies.md for agency technique breakdowns on micro-interaction implementation.

Design Process

1. Concept First, Code Second

Before any code, define:

BRAND ESSENCE: What single word captures the soul?
VISUAL TENSION: What opposing forces create interest?
SIGNATURE MOMENT: What will people screenshot and share?
TECHNICAL AMBITION: What pushes the browser's limits?

2. Design the Signature Moment First

Do not start with the header. Start with the thing that defines the experience. The header can be solved later. Every 10/10 project has at least one moment that makes people stop and share: a hero animation never seen before, typography so bold it becomes the visual, an interaction that delights unexpectedly, a scroll sequence that tells a story, or a transition that feels like magic.

Questions to identify your signature:

1. What will people screenshot?
2. What will they describe to colleagues?
3. What will they try to reverse-engineer?
4. What makes this unmistakably THIS project?

3. Typography Sets Everything

Choose your display typeface first. Let it dictate the color palette mood, the animation style, the spacing rhythm, and the overall personality.

4. Motion Is Not Polish

Prototype animations early. Motion design happens alongside visual design, not after.

5. Ship With Restraint

3 things perfect beats 10 things mediocre. Cut ruthlessly.

Implementation Notes

1. Start with the signature moment -- design the thing that defines the experience first
2. Conceptualize desktop-first, build mobile-first -- dream big, implement progressively
3. Prototype animations early -- motion is not a polish step, it is core to the design
4. Test on real devices -- simulators lie about performance and feel
5. Ship with restraint -- 3 things perfect beats 10 things mediocre
6. Sweat the micro-details -- craft lives in the 1% others skip
7. Design the states -- hover, focus, loading, empty, error all matter
8. Own your constraints -- every limitation is a design opportunity
9. Use project conventions -- if Tailwind 4+ and/or shadcn/ui are available, build on top of them rather than fighting them. Extend their design tokens, customize their components, and use their patterns as a foundation for 10/10 craft

Reference Files

Consult these for detailed implementation:

• references/typography.md: Font pairing strategies, type scale systems, advanced CSS typography
• references/animation-patterns.md: Scroll animations, page transitions, micro-interactions with code
• references/layout-systems.md: Grid frameworks, breakpoints, responsive patterns
• references/technical-stack.md: Libraries, tools, performance optimization
• references/case-studies.md: Agency technique breakdowns (Locomotive, Studio Freight, AREA 17, Hello Monday, etc.)

Common Mistakes

Quick Diagnostic

Further Reading

• Designing with Type by James Craig -- the foundational text on typographic principles, hierarchy, and the architecture of type in design
• Grid Systems in Graphic Design by Josef Muller-Brockmann -- the definitive work on grid-based composition, proportional systems, and the mathematical foundations of visual layout
• The Elements of Typographic Style by Robert Bringhurst -- the typographer's bible covering rhythm, proportion, and the craft of setting type beautifully
• Interaction of Color by Josef Albers -- essential reading on color perception, contrast, and how colors behave in relation to each other
• Layout Essentials: 100 Design Principles for Using Grids by Beth Tondreau -- practical grid-based layout principles applied to real design scenarios
• Awwwards Annual: The Best 365 Websites Around the World -- yearly collection of the web's most innovative designs, serving as a benchmark for 10/10 craft

About the Author

This skill synthesizes techniques and principles from the world's most awarded digital design agencies. The primary sources are:

Locomotive (Montreal) -- pioneers of smooth scroll experiences (creators of Locomotive Scroll), known for monochromatic tension palettes, bold typography, and seamless page transitions. Their work for clients like Ubisoft and the National Film Board of Canada defines the standard for immersive web storytelling.

Studio Freight (New York) -- specialists in creative development, known for magnetic interactions, bold signature color palettes, and pushing the technical boundaries of the browser. Their open-source tools and experimental projects influence the broader creative development community.

AREA 17 (New York/Paris) -- a digital product agency known for contextual design systems that adapt to each client's identity, editorial-quality layouts, and the balance of visual ambition with functional clarity. Their work for cultural institutions and media organizations sets the bar for content-driven design.

Active Theory (Los Angeles) -- a creative studio specializing in WebGL, immersive 3D experiences, and interactive storytelling. Their work demonstrates what is possible when technical ambition meets design vision.

Hello Monday (Copenhagen/New York, now part of DEPT) -- known for playful, innovative interactions and page transitions that feel like magic. Their work for brands like Spotify, Adidas, and Google consistently wins top awards.

Additional inspiration drawn from Dogstudio (Belgium), Tonik (Poland), Instrument (Portland), Resn (New Zealand), and the broader community of Awwwards, FWA, CSS Design Awards, and Webby Award winners whose collective work establishes the evolving standard for world-class digital craft.

Overview

Create award-winning, immersive web experiences at the level of Awwwards-featured agencies.

Prerequisites

• Access to the ORM environment or API
• Required CLI tools installed and authenticated
• Familiarity with ORM concepts and terminology

Instructions

1. Assess the current state of the ORM configuration
2. Identify the specific requirements and constraints
3. Apply the recommended patterns from this skill
4. Validate the changes against expected behavior
5. Document the configuration for team reference

Output

• Configuration files or code changes applied to the project
• Validation report confirming correct implementation
• Summary of changes made and their rationale

See ORM implementation details for output format specifications.

Error Handling

Examples

Basic usage: Apply top design to a standard project setup with default configuration options.

Advanced scenario: Customize top design for production environments with multiple constraints and team-specific requirements.

Resources

• Official ORM documentation
• Community best practices and patterns
• Related skills in this plugin pack