Individual skill

premium-visual-reference-library

Find references, Viktor Oddy and MotionSites.

skills/premium-visual-reference-library/SKILL.md

Read pinned source

Source commit 9922fa0af0aea32443cf7365ef5024dc7797382d

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
137
Repository last updated
Oct 22, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Premium Visual Reference Library

Use this skill to pick reference sources before designing a premium website.

## Workflow

1. Identify the site category: product/devtool, luxury/editorial, portfolio, hospitality, commerce, personal, agency, or content/media.
2. Read [sources.md](references/sources.md) for the relevant source clusters.
3. When the user names a creator, asks for many examples, or uses a style shorthand, also read [creator-and-pattern-index.md](references/creator-and-pattern-index.md) and [creator-methods-evidence.md](references/creator-methods-evidence.md).
4. When Viktor Oddy or MotionSites is named, read [motionsites-viktor-evidence.md](references/motionsites-viktor-evidence.md) and refresh any count or catalog claim that matters to the current project.
5. Select enough distinct references for the open decision; 3–7 is a broad direction-study option, not a quota for a supplied exact reference.
6. Extract concrete patterns: type, layout, density, media, motion, CTA, proof, navigation, section rhythm, and mobile behavior.
7. State what not to copy.
8. When implementation is in scope, add selected traits to the shared build spec; a reference-only request ends with the source-backed study.
Back to top