see

Audits UI surfaces against homepage gold standard using ARTISAN agents and generates structured reports.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/project-purupuru/world-purupuru --skill see
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: see
Source: https://github.com/project-purupuru/world-purupuru/tree/main/.claude/skills/see
Command: npx skills add https://github.com/project-purupuru/world-purupuru --skill see

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sky-eyes taste sweep identifies deviations across UI surfaces by comparing against the homepage gold standard and taste.md, enabling teams to maintain visual and content consistency at scale.

Core Features & Use Cases

  • Spawns ARTISAN agents to audit every surface against the homepage gold standard and taste.md.
  • Generates structured reports of violations with suggested fixes for designers and engineers.
  • Supports full sweeps or targeted page audits via /see prompts, coordinating multi-agent tasks.

Quick Start

Invoke /see with no scope for a full sweep, or specify a page like collection or chat to audit a single surface.

Frequently Asked Questions about see

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit UI surfaces against the homepage gold standard?

To audit UI surfaces against the homepage gold standard, spawn ARTISAN agents via /see prompts to check targeted pages or perform full sweeps, generating structured reports with actionable fixes.

How does multi-agent frontend design auditing work?

Multi-agent frontend design auditing works by invoking /see to spawn ARTISAN agents that compare surfaces against taste.md and homepage standards, enforcing design tokens and generating violation reports.

Can I run a targeted frontend audit on a single collection page?

Yes, you can run a targeted frontend audit on a single collection page by specifying the page name when invoking the /see prompt, coordinating ARTISAN agents for that specific surface.

What's the best way to enforce design tokens across multiple UI surfaces?

The best way to enforce design tokens across multiple UI surfaces is running a full sweep via /see, utilizing ARTISAN agents to identify deviations and output structured reports with suggested fixes.

Why does my UI surface deviate from the homepage visual standard?

Your UI surface deviates from the homepage visual standard when front-end design tokens are not applied correctly, identified by ARTISAN agents checking against taste.md guidelines.