Skip to content

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

web-reference-research

Verified

Analyze selected sources: Viktor or MotionSites.

references/web-reference-research-guide.md

View on GitHub
# Web Reference Research Guide

## Purpose

Convert taste references into concrete, verifiable design decisions.

## Use When

- The user asks for research, current references, X/GitHub inspiration, or named web design influences.
- The prompt includes brands or people such as Squarespace, Raycast, Linear, Vercel, Viktor Oddy, Codrops, Awwwards, Framer-style, or luxury/cinematic sites.
- A design feels vague and needs source-backed constraints before coding.

## Do Not Use When

- The user provides a complete approved design system and asks for implementation only.
- The task is offline and browsing is not needed or allowed.
- The request is a simple local bug fix unrelated to design references.

## Discovery Questions

- Which reference is primary and which are secondary?
- Is the reference about layout, motion, typography, copy, product realism, visual assets, or polish?
- What site category are we applying the reference to?
- What would be inappropriate to borrow from the reference?

## Decision Tree

- If the reference is current/public and precision matters, browse and cite sources.
- If a source is inaccessible, say so and label any interpretation as inference.
- Extract traits into build rules: type, layout, color, media, motion, copy, conversion, QA.
- Create steal/adapt/avoid notes before implementation.
- During QA, compare the result against the extracted traits rather than the reference name.

## Implementation Rules

- Do not pretend to have verified X content if it was not accessible.
- Use reference names as shorthand only after defining the concrete traits.
- Honor the authorized source mode. Preserve supplied/exact details when requested; adapt principles and original assets for original brand work.
- Translate references by site category: a hotel should not become a devtool homepage because Vercel was mentioned.
- Keep citations in final answers when web research materially shaped the recommendation.

## Useful Patterns

- Squarespace: clear business categories, elegant templates, practical conversion paths, image-first clarity.
- Raycast: command surface, fast ergonomic interactions, product UI details, controlled playfulness.
- Linear: dense product realism, restrained glow, workflow clarity, serious speed language.
- Vercel: monochrome precision, strong type, developer trust, minimal surfaces, system clarity.
- Viktor Oddy/MotionSites: verified public sources include `motionsites.ai`, `x.com/viktoroddy`, `youtube.com/@ViktorOddy`, and `designrocket.io`. Extract cinematic hero concepts, prompt-to-build workflows, scroll/video/3D choreography, disciplined type, conversion intent, and delivery limits from the current source—not from the name alone.
- Codrops/Awwwards: sticky scenes, masks, WebGL galleries, scroll rhythm, experimental transitions.

## Anti-Patterns

- Copying the visual skin of a reference while ignoring its information structure.
- Combining too many references into an incoherent collage.
- Treating luxury, modern, or cinematic as self-explanatory.
- Using unverifiable creator details as fact.

## QA Checklist

- Check that the brief has concrete source-supported traits and relevant avoid rules, scaled to the requested scope.
- Confirm the chosen reference family matches the site category.
- Verify any current/public claims if the user asked for research.

## Acceptance Criteria

- Another builder could implement the direction without needing the original inspiration link.
- The result follows the requested fidelity mode, preserves provenance, and distinguishes observed source details from new authorship.
- The final site can be judged against named traits, not vibes.

## Scoped execution

Apply the [shared web contract](../../website-operating-rules/references/scoped-web-contract.md) once when execution crosses phases; reuse it if already read. Load only the specialist guidance relevant to the requested surface and deliverable.
add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks.Stars: 115kUpdated Claude CodeCodexVerifiedInstall