agentleFS
phazurlabsphazurlabs/sumi/skills/reference-intelligence/SKILL.md

reference-intelligence

Skill58 starsChanged 23 days agoApache-2.0View on GitHub

Sources REAL design references instead of recalling them — award-winning live sites from Awwwards, app screens and flows from Mobbin (MCP), motion recipes from MotionSites (MCP) — captures them, measures their design DNA (type, color, spacing, grid, radius, motion stack), and synthesizes a Reference Board in .sumi/refs/ that every MAKE and REVIEW command builds and grades against. Use when the user mentions: inspiration, inspo, references, reference sites, moodboard, Awwwards, SOTD, site of the day, Mobbin, MotionSites, 'make it look like', 'sites like', 'award-winning', 'best in class', examples of, what are the best sites for, reference board, steal like an artist, benchmark against real sites.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Every other Sumi skill encodes taste from memory.

    line 8
  2. Distinctive:

    Run it in the background for more than 3 sites.

    line 71

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Reference Intelligence — look before you design

Every other Sumi skill encodes taste from memory. This one goes and looks. A senior studio doesn't design a fintech landing page from recollection; it pulls ten current winners onto a wall, pulls them apart, agrees what to steal, builds, then pins the build next to the wall and asks whether it belongs there.

That loop has four steps and Sumi owns all of them:

StepWhat happensWhere it lives
ScoutFind 8-12 candidates from real sourcesscripts/awwwards.mjs, Mobbin MCP, MotionSites MCP
CaptureScreenshot the LIVE sites and measure their DNAscripts/capture.mjs → .sumi/refs/<slug>/
BoardSynthesize what to steal / avoid into one direction.sumi/refs/board.md + board.json
CompareGrade a build side by side with the boardcritic agent, /grade, /roast

Source routing

The ask is…Primary sourceSecondary
Marketing site, landing page, portfolio, brand, campaignAwwwardsMotionSites for motion recipes
App screen, dashboard, settings, product UIMobbinAwwwards app-style / ui-design tags
A flow (onboarding, checkout, signup, paywall, search)Mobbin (flows)—
Motion, scroll storytelling, WebGL, transitionsAwwwards (gsap, three-js, webgl, transitions, scrolling)MotionSites
"Make it look like <url>"That URL, straight into capture.mjsAwwwards category of that site

Adapters, one per source:

  • references/awwwards-adapter.md — listings, the 192 category tags, sector → tag map, etiquette
  • references/mobbin-adapter.md — MCP auth, query shapes, what may be stored
  • references/motionsites-adapter.md — prompt library, free-tier limit, upgrade message rule
  • references/dna-schema.md — what capture.mjs measures and how to read it
  • references/board-synthesis.md — combining references without cloning one; board.json schema
  • references/comparison-protocol.md — how the critic grades a build against the board

Non-negotiables

  1. Real, not recalled. A reference must be a URL that was fetched this session (or a cached fetch under .sumi/refs/), a Mobbin result from the MCP, or a MotionSites prompt. Never present a site as an Awwwards winner from memory.
  2. Capture the live site, not the thumbnail. Awwwards and Mobbin are indexes. The DNA comes from the site itself.
  3. One script call, not click-by-click browsing. Capture runs as ONE node scripts/capture.mjs invocation over all picks. Never drive puppeteer/Chrome MCP step by step to study a site.
  4. Small and on-demand. 8-12 candidates per run, 3-5 kept. No bulk crawling of Awwwards; reuse a cached listing under .sumi/refs/ if it is under 7 days old.
  5. Steal traits, never layouts. The board takes at most ONE signature trait from each reference (see board-synthesis.md). A build that is recognisably one reference is a fail.
  6. Screenshots stay local. Third-party captures are study material. Suggest adding .sumi/refs/**/*.jpg to .gitignore; never publish or deploy them.
  7. The user curates. Present the shortlist and let them keep 3-5. Art direction is a choice, not a computation.

Running the scripts

Scripts live in the plugin, not the project. Resolve the plugin root once:

SUMI="${CLAUDE_PLUGIN_ROOT:-$(dirname "$(dirname "$(find ~/.claude/plugins -path '*sumi*/scripts/capture.mjs' -print -quit)")")}"
node "$SUMI/scripts/awwwards.mjs" technology --awarded --limit 10 --out .sumi/refs/awwwards-technology.json
node "$SUMI/scripts/capture.mjs" --from .sumi/refs/awwwards-technology.json --pick slug-a,slug-b,slug-c
node "$SUMI/scripts/capture.mjs" https://linear.app https://stripe.com   # direct URLs

capture.mjs needs puppeteer-core (resolved from the project, $SUMI_PUPPETEER_DIR, or known sibling projects) and a local Chrome. It takes ~40-60s per site (desktop + phone, scroll steps). Run it in the background for more than 3 sites.

Output: .sumi/refs/

.sumi/refs/
├── awwwards-<listing>.json   # scout results (cache)
├── mobbin.json               # Mobbin picks: app, screen/flow, url, why
├── motion.json               # MotionSites prompts used
├── <slug>/dna.json           # measured DNA, desktop + phone
├── <slug>/desktop-0..3.jpg   # scroll-step captures
├── <slug>/phone-0..2.jpg
├── board.md                  # human-readable Reference Board
└── board.json                # machine-readable direction every command consumes

board.json is the contract. /style turns its direction into tokens and its references into the references array of .sumi/style.json (per design-memory, only /style writes that file). /page, /screen and /component build against it; /grade and /roast compare against it.

Related skills

  • visual-design-mastery — the 10-dimension scoring the comparison uses
  • screen-flow-patterns — the screen/flow taxonomy used to phrase Mobbin queries
  • sector-style-intelligence — sector norms; its "Inspiration Links" seed Mobbin queries
  • interaction-motion-design, animation-recipe-library — translating captured motion stacks into code

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.