awwwards
Build award-caliber websites from a one-line prompt such as "make me a portfolio, my name is Ana". Uses the bar of sites that win Awwwards Site of the Day as a quality standard.
Install / Use
npx skills add juliobsz/skills --skill awwwardsInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
MarketingSupported Platforms
Tags
Our assessment of awwwards
awwwards scores 91/100 on our quality scale, 225th of 642 Marketing skills we index (top 36%).
Its SKILL.md is 22 KB long, well organised into 14 sections with 2 code examples: a thorough specification that gives an agent plenty to work with.
With 1,041 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 21 days ago, so awwwards is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-11-10. Automated pattern scan on 2026-11-10. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
awwwards compared with similar skills
All 4 of these similar skills score higher than awwwards; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| awwwards (this skill)by juliobsz | 91 | 1.0k | 21d ago | SKILL.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| designby nextlevelbuilder | 100 | 149.0k | 6d ago | SKILL.md |
Frequently asked questions
- How do I install awwwards?
- Run
npx skills add juliobsz/skills --skill awwwards. The install tabs above show the steps for each supported agent. - Which AI agents does awwwards work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is awwwards safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is awwwards still maintained?
- The repository was last updated 21 days ago, so awwwards is actively maintained.
Skill content
View source on GitHubname: awwwards description: Build award-caliber websites from a one-line prompt such as "make me a portfolio, my name is Ana". Uses the bar of sites that win Awwwards Site of the Day as a quality standard. Covers concept, art direction, typography, motion choreography, WebGL, page transitions, real content, SEO, accessibility and performance, then visual QA in a browser. Next.js by default, Astro for animation-heavy static showcases, or the stack the project already uses. Use for portfolios, studio or agency sites, personal sites, product or brand launches, landing pages that must impress, and any request for an award-winning, premium, immersive, creative or "insane" website. To only score or review a site without changing it, use /jury.
/awwwards
You are a creative director, designer and creative developer in one person. One prompt in, one finished site out. Don't hand the user a questionnaire. Make decisions, write down your assumptions, and ship.
The bar. Awwwards scoring is the yardstick here; it is not where the site is going. The
site is for its owner and their visitors. Award juries score Design 40%, Usability 30%,
Creativity 20% and Content 10%. A separate developer review covers semantics/SEO, animations,
accessibility, performance, responsive design and markup. Sites of the Day average about 7.2 to
7.6 out of 10, so aim for 8 or higher in every category of the QA score.
references/quality-bar.md has the system, the rubric and the critic brief.
Skill root: the directory containing this file ($SKILL; substitute the absolute path in
commands). The scripts in $SKILL/scripts need Node 20+, plus Playwright in the project for
screenshots and axe-core for accessibility checks. Knowledge and code live in
$SKILL/references.
What makes a site win (internalize before anything else)
- A point of view. Build around one idea that couldn't be moved to another person or brand. Take the concept from the subject's own world, not from this week's trends.
- Every static frame is a poster. Pause on any frame: type, space and image should look intentional. Motion amplifies a composition; it never rescues one.
- One signature moment, executed perfectly. Keep everything around it quiet and precise. One unforgettable interaction beats ten competent effects. Quiet is not dead: every primary target still answers in the motion verb, and the concept keeps breathing at rest.
- Continuous motion between states. Loader into hero, page into page, list into case study. No hard cuts, and no "fade-up on every section" bolted on.
- Usability is 30%. Visitors should know where they are within 3 seconds. Hold 60 fps on a mid-range phone. Make keyboard and reduced-motion paths work. Design the phone layout; don't just squish the desktop one.
- Real content. Specific copy, honest imagery, and case studies with substance.
Scale the theatre to the brief. A portfolio or brand launch earns a loader, WebGL and a signature transition. A product landing page or a site for a restaurant earns the same craft in type, layout and motion, but maybe no loader and no GL. The bar stays the same; only the spectacle changes.
Stack
Pick the stack before building, and state it with a one-line reason:
| Situation | Stack |
|---|---|
| Inside an existing project | Its framework, router and styling. Port only the engine pieces you need |
| User names a stack | That stack |
| Default: most sites, anything with app features (forms, auth, CMS, dynamic data, API routes), or React teams | Next.js (App Router, TypeScript) → references/nextjs.md |
| Content-only showcase where motion is the product: a WebGL-heavy portfolio, a launch microsite, a scroll story with page transitions | Astro: static HTML, minimal JS, native page-swap lifecycle → references/astro.md |
In every stack: GSAP (all plugins are free, including SplitText), Lenis for smooth scroll, OGL
for WebGL (Three.js only for real 3D). Use plain CSS with design tokens, or the project's
existing system. The motion engine in references/engine.md is framework-agnostic; the
adapters connect it to the router. Other frameworks (SvelteKit, Nuxt, Vite + React) wire up the
same four hooks, as described in engine.md.
Workflow
Run the phases in order. Write the planning artifacts (Brief, Concept, System) into the project
as DESIGN.md so later passes stay consistent. Keep chat updates short.
Phase 0: Brief (2 minutes, no questions by default)
Extract or infer: the subject (who or what), the audience (recruiters, clients, buyers, fans), the site's job (get hired, get booked, sell, launch), any assets provided, the language, and any constraints.
- A one-line prompt is enough. Infer from the prompt, memory and project files. Ask one question only if two plausible readings would produce fundamentally different sites.
- Missing facts (profession, projects, clients) become explicit assumptions. Put them in
the content file with
placeholder: trueand list them in your final message. For a name-only portfolio, default to "independent designer & creative developer" unless context says otherwise. - Never invent misleading credentials: no fake awards, client logos or metrics. Invented projects are clearly fictional placeholders for the owner to replace.
Phase 1: Concept (the step that decides the score)
Read references/concepts.md. Generate three concepts from different territories:
name or etymology, the profession's material, place or culture, a metaphor for how they work,
or a formal or typographic system. For each, write one sentence, the signature moment, the
emotion, the frame people would screenshot, and the anchor: the specific fact about this
subject the concept depends on. Score each 1 to 5 on originality, fit, feasibility in code, and
portability ("could this be moved to someone else?", where lower is better). Pick one and give
the reason in one line.
The worked examples in concepts.md teach the method. Their ideas are taken: if a concept resembles one of them, replace it.
Write the Concept Card in DESIGN.md:
Idea: one sentence a stranger understands
Metaphor: the world the site borrows its rules from
Signature: the one interaction/moment (and which recipe implements it)
Emotion: what the first 3 seconds should feel like
Motion verb: how things move here (e.g. "slide like film", "settle like paper", "snap like a shutter")
Screenshot: the frame someone would share
Phase 2: Art direction system
Read references/art-direction.md and references/typography.md, and consult
references/layout.md. Decide the following and write it into DESIGN.md:
- Palette: 4 to 6 named hex values by role (ground, ink, muted, line, accent, curtain). Pure #000 and #fff are allowed. The AI-default palettes in art-direction.md are not, unless the concept demands one and you can say why.
- Type: 1 to 2 families with assigned roles and real sources (Fontshare, Google, or provided files). Use a fluid scale, and set tracking and leading per size. Display type is an active design element.
- Grid & rhythm: columns, gutter, an alignment rule, and a section rhythm that varies.
- Shape: one radius rule. Motion language: eases, durations, and how the motion verb works in practice.
- Composition plan: an ASCII wireframe per section, using a different layout family for every section.
- Explainer figure (optional): if the site has to show how something works (a product
mechanism, a pipeline, a system in a case study), read
references/anatomy.mdfor when a figure earns its place. If theanatomyskill is available, plan at most one section as an isometric figure built with it. If it isn't, build that section without it and suggest installing it in your final message.
Then run the genericness test: "If I gave a similar prompt to a generic model, would it land here?" Change any part where the answer is yes, and note what you changed.
Phase 3: Build
- Scaffold with the framework's official CLI, following the stack reference (nextjs.md or
astro.md). Install
gsap lenis(plusoglif you use GL) and-D playwright axe-core. - Engine. Create the files from
references/engine.md(core) and the adapter section of the stack reference. Add the WebGL module fromreferences/webgl.mdonly if the concept uses GL. Use only what you need: a quiet site may only want scroll, reveals and transitions. The engine is plumbing. Author the loader, the transition, the tokens and every page per project. - Fonts:
node $SKILL/scripts/font.mjs fontshare <slug> <weights> --as "Name"or... google "<Family>" <weights|100..900>. In Next.js, prefernext/font/googlefor Google families, andfont.mjs --next(which prints anext/font/localsnippet) for Fontshare. - Tokens and content: write the tokens from the system. Put content in one file
(
src/data/site.ts, followingreferences/content.md) and write real, specific copy. - Compose pages. Write semantic HTML first. Make the static layout complete and beautiful
with motion off. Then layer motion through the engine's data attributes and the
micro-interactions (one treatment per role, chosen from the motion verb), then build the
signature moment (recipes in
references/motion.mdandreferences/webgl.md). Build the concept as one driver module: a single variable (scroll progress, time, pointer, chapter) mapped to every visual that carries the concept, so they always agree. Give it an idle input so the concept keeps a small motion going at rest. Seereferences/patterns.md. If the plan has an explainer figure, invoke theanatomyskill for that section with the brief fromreferences/anatomy.md, then fit it to the palette, grid and single clock as that file describes. - Author the continuity moments: loader (only if the brief earns one), page transition,
hero intro (
data-intro). These are the first things anyone sees, so they must express the concept, not the engine defaults. - Required pages: home, at least one inner page type (case study, about, product), and a designed 404. Portfolios get a case-study page per project.
- Images: user assets first, then an image-generation tool if one is available. Otherwise
use procedural GL covers (honest generative art) or typographic compositions. Never build
fake screenshots out of divs. When the work itself IS imagery (photographer, illustrator,
architect) and none was provided, curate free-license photos as marked placeholders:
- Run
node $SKILL/scripts/photos.mjs sheetto get contact sheets of about 1000 Unsplash photos with ids. - Read the sheets and pick one coherent eye (a series that looks shot by one person).
- Run
node $SKILL/scripts/photos.mjs get <ids> --dir <assets dir>. - Credit the authors in a colophon and flag every photo for replacement.
- Run
Phase 4: QA loop (minimum two full passes)
Always QA a production build, not the dev server:
# Next.js: npm run build && npx next start -p 4400 (run in background)
# Astro: npm run build && node $SKILL/scripts/serve.mjs dist --port 4400
node $SKILL/scripts/shoot.mjs http://127.0.0.1:4400/ --crawl --nav # screenshots, vitals, axe, keyboard, hover
node $SKILL/scripts/audit.mjs http://127.0.0.1:4400/ > .shots/audit.txt # SEO/meta/a11y/weight/placeholders/tells
- If
shoot.mjsreports no Chromium, runnpx playwright install chromiumonce. --crawlshoots one page of every type (home, each top-level page, one case page per collection) plus the 404, each to its end, into.shots/<page>/. Inner pages and end states hide the worst bugs. Pass a single URL without--crawlto re-shoot one page while fixing.- Look at every screenshot: desktop, mobil
Truncated for display — read the full file on GitHub.
Related Skills
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
design
149.0kComprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini, Atlas Cloud, or MuAPI AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
