# Awwwards Quality Sites

> Use when designing or building a distinctive, award-caliber website with strong art direction, polished interaction, and production-ready responsive behavior. Covers creative direction, visual hierarchy, motion, accessibility, performance, and quality assurance.

- Skill: `oyi77/awwwards-quality-sites` (Agent Skill)
- Install (CLI): `npx get-skill add oyi77/awwwards-quality-sites`
- Raw SKILL.md: https://api.skillmd.com/api/skills/oyi77/awwwards-quality-sites/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- License: Apache-2.0
- Author: oyi77 (https://skillmd.com/u/oyi77)
- Updated: 2026-11-18
- Page: https://skillmd.com/skills/oyi77/awwwards-quality-sites

---


# Awwwards-Quality Sites

Create memorable websites through deliberate art direction and precise execution—not decoration for its own sake. “Award-caliber” describes a quality bar, not a guarantee of awards or a license to sacrifice usability.

## When to Use

- Creating or substantially redesigning a marketing site, portfolio, campaign, editorial experience, or product landing page.
- The brief calls for a distinctive, premium, immersive, or award-caliber web experience.
- Improving a site's visual identity, interaction craft, or responsive polish.

Do not use this as a reason to add complexity to a functional interface, or to replace product-specific UX requirements with visual spectacle.

## Overview

This skill describes how to build award-caliber web experiences: deliberate art direction, a coherent visual system, purposeful interaction, accessible controls, and production-ready responsiveness. It is a craft guide for designers and builders creating marketing sites, portfolios, campaigns, editorial pages, and landing pages with high visual ambition.

## Workflow

### 1. Establish the brief

Before choosing a visual direction, identify:

- **Audience and goal:** who arrives, what they need, and the primary action.
- **Content:** required copy, assets, sections, and information priority. Preserve supplied meaning; do not invent facts, testimonials, or claims.
- **Brand constraints:** existing identity, colors, typography, tone, and prohibited treatments.
- **Context:** target devices, browser support, framework, existing design system, and delivery constraints.

If a critical input is missing, use a conservative, reversible default and state it. Ask only when the choice would materially change the result.

### 2. Set one coherent creative direction

Write a one-sentence concept that connects the site's purpose to its visual language. Choose a clear organizing idea—such as editorial, cinematic, tactile, typographic, or product-led—and make each major choice serve it.

Define a compact system before implementation:

- Type roles and scale; use the available brand fonts or a small, purposeful pairing.
- Color roles, contrast, and accent behavior.
- Spacing rhythm, grid, content width, and alignment rules.
- Image, illustration, and icon treatment.
- Motion principles: what moves, why, and when it stops.

Avoid template-like sameness, arbitrary gradients, ornamental noise, and unrelated visual effects. Do not use a trend merely because it is fashionable.

### 3. Design the page hierarchy

- Lead with a specific headline and a clear next action.
- Make the first viewport communicate identity, purpose, and hierarchy—not just fill space.
- Arrange sections to support the user's decision or task; every section must earn its place.
- Use contrast in scale, density, whitespace, and composition to create rhythm.
- Keep navigation, labels, and controls recognizable. Novel presentation must not obscure function.
- Treat real content and assets as design inputs. Use intentional placeholders only when none are supplied; never imply placeholders are genuine.

### 4. Build responsive behavior intentionally

Design for narrow and wide viewports, not only shrink-to-fit. Reflow grids, type, imagery, navigation, and interaction targets where needed. Keep reading order logical, avoid horizontal overflow, and preserve access to every action. Test representative viewport sizes and long or translated content when relevant.

### 5. Add purposeful interaction and motion

- Give interactive elements visible hover, focus, active, and disabled states as applicable.
- Use motion to explain state, guide attention, or reinforce the concept. Keep duration and distance restrained; avoid delaying essential content or controls.
- Make interactions work by keyboard and touch, with clear outcomes and no hover-only information.
- Respect `prefers-reduced-motion`; provide an equivalent reduced or static experience.
- Avoid autoplay audio, forced scroll hijacking, flashing, and motion that prevents users from completing the task.

### 6. Protect accessibility and performance

- Use semantic landmarks, a logical heading order, descriptive link text, labels, and useful image alternatives.
- Ensure keyboard access, visible focus, sufficient text and control contrast, and appropriately sized targets.
- Do not communicate meaning by color or motion alone.
- Optimize images and media for their actual display size; reserve layout space to limit shifts.
- Defer nonessential work, avoid unnecessary dependencies and scripts, and keep the experience useful when optional effects fail.
- Verify that overlays, menus, and dialogs can be operated and dismissed accessibly.

### 7. Verify and refine

Use the running site, not screenshots alone. Check:

- Primary task and links work; no dead controls or placeholder copy remain unintentionally.
- Narrow and wide layouts, overflow, image crops, and section transitions.
- Keyboard navigation, focus visibility, reduced motion, and contrast.
- Loading behavior, console errors, and obvious layout shifts.
- Visual consistency: typography, spacing, alignment, states, and motion all support the same direction.

Fix the largest user-visible problem first. Remove effects that do not improve clarity, identity, or feedback. Report unverified constraints honestly.

## Anti-rationalization table

| Temptation | Why it fails | Required response |
|---|---|---|
| “Award-winning means more animation.” | Motion can obscure content and slow tasks. | Justify each motion by purpose; remove motion without user value. |
| “The desktop hero looks good, so it is done.” | Small screens change hierarchy and interaction. | Test narrow layouts and recompose deliberately. |
| “A pretty screenshot proves quality.” | It cannot prove working controls, accessibility, or loading behavior. | Exercise the real page with keyboard and touch. |
| “We can use low-contrast text for the aesthetic.” | Users may not be able to read or operate the site. | Preserve contrast and legibility; adjust the aesthetic instead. |
| “A trendy effect will make the design distinctive.” | Unmotivated trends produce generic, incoherent work. | Tie choices to the brief and visual concept. |
| “Placeholder content is close enough.” | It can misrepresent the product and distort layout. | Use supplied content, or clearly identify temporary placeholders. |

## Verification

- [ ] Goal, audience, constraints, and content understood.
- [ ] One coherent creative direction informs the visual system.
- [ ] Hierarchy and primary action are immediately clear.
- [ ] Responsive layouts preserve content, order, and function.
- [ ] Interactions work across keyboard, pointer, and touch.
- [ ] Reduced-motion, contrast, focus, semantics, and alternatives addressed.
- [ ] Media and effects do not impose avoidable performance costs.
- [ ] Running experience checked; remaining limitations disclosed.

