agentsclimarketplace

Web reference research

Skill TheGoat395/Codex-Skills/skills/web-reference-research

Codex-first Agent Skills library for premium frontend, website, motion, accessibility, QA, and handoff workflows.

Install
npx -y skills add TheGoat395/Codex-Skills --skill web-reference-research

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

Research and translate website references into reusable design constraints. Use when the user mentions Viktor Oddy, Squarespace, Raycast, Linear, Vercel, Framer, Awwwards, Codrops, luxury sites, cinematic websites, product-led sites, portfolios, or any external web design reference that should influence a build.

SKILL.md

1.1 KB, 160 tokens by cl100k_base, as published. Nobody here has run it

Web Reference Research

Purpose

Convert taste references into concrete, verifiable design decisions.

Required Use

Use this skill when the trigger description applies. Keep the SKILL.md lean, then read references/web-reference-research-guide.md for concrete rules before planning or editing a meaningful website change.

Operating Contract

  1. Inspect before coding when code exists.
  2. Convert vague taste into concrete rules.
  3. Explain planned files before major changes unless the user clearly said to proceed.
  4. Build, inspect, polish, and verify.
  5. Report commands run, files changed, and anything not tested.

Detailed Guide

Read references/web-reference-research-guide.md when this skill is active for a build, redesign, review, or implementation plan.

What ships with it: 2 files

4.3 KB alongside SKILL.md

agents/

Gives 0 of the 12 instructions most design frontend skills give in 160 tokens

Counted across 1,169 of the 1,878 authors here whose files we hold, read 2026-08-07

  • Use CSS variables for color consistencyin 72 of 1169, across 23 files
  • Commit to one bold aesthetic direction before codingin 72 of 1169, across 27 files
  • Match implementation complexity to the aesthetic visionin 70 of 1169, across 20 files
  • Add atmospheric background effects and texturesin 57 of 1169, across 9 files
  • Use unexpected spatial compositions and layoutsin 56 of 1169, across 8 files
  • Implement real working codein 55 of 1169, across 7 files
  • Vary themes and aesthetics across different designsin 48 of 1169, across 7 files
  • Launch chromium in headless modein 47 of 1169, across 4 files
  • Close the browser when donein 47 of 1169, across 4 files
  • Run provided scripts with help flag firstin 47 of 1169, across 4 files
  • Wait for network idle statein 47 of 1169, across 4 files
  • Use descriptive selectors for elementsin 47 of 1169, across 4 files

Said here and by no other author read

  • convert vague taste into concrete rules
  • explain planned files before major changes
  • build the implementation
  • inspect the implementation
  • polish the implementation
  • report commands run

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 327,132. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.