vision

Directing UI/UX creative work — complete redesigns, new designs, and trend application. Use when design direction decisions, Design System construction, or orchestration of Muse/Palette/Flow/Forge is needed. Does not write code. Offers an interactive co-design pair mode (decide direction together, one decision at a time).

跳到安装

仓库: simota/agent-skills
最近来源活动: 2026年7月29日 02:44
检测到的 SKILL.md 语言: 英语
星标: 71
分支: 14

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

直接命令不会经过审查 Prompt；运行前请先检查来源。

npx skills add https://github.com/simota/agent-skills --skill vision

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 SkillsMP 当前能够提供的文件。

检查来源文件

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

文件资源管理器

18 个文件

SKILL.md

来源说明 · 只读预览

返回搜索返回安装

chain

Auditing skill/plugin/MCP supply chains. Treats SKILL.md, bundled scripts, MCP server defs, hooks, and `.claude/` config as third-party software. Generates sha256 manifests, scans for Unicode Tag injection, detects curl-pipe + credential-exfil patterns, enforces third-party intake checklist, and pins MCP tool descriptions against rug-pulls. Use when auditing skill/MCP supply chain. Not for app SAST (Sentinel), CI/CD (Gear/Pipe), hook design (Latch), SKILL.md format (Gauge), or runtime exploit (Probe).

2026-08-10

latch

Proposing, configuring, debugging, and maintaining Claude Code hooks (PreToolUse/PostToolUse/Stop and other lifecycle events). Use when workflow automation, quality gates, or security enforcement via hooks is needed.

2026-08-10

nexus

Orchestrating specialist AI agent teams as a meta-coordinator. Decomposes requests into minimum viable chains, spawns each as an independent session in AUTORUN modes, and drives to final output. Use when a task spans multiple specialist domains, requires parallel agent execution, or needs hub-and-spoke routing across the skill ecosystem.

2026-08-10

查看这个仓库的全部 Skills

Vision

Creative-direction agent for redesigns, new-product design systems, trend application, and design-team orchestration. Vision does not write implementation code.

Trigger Guidance

Use Vision when the primary question is design direction, not implementation.

Typical tasks: redesign an existing UI, define a new design system, audit visual/UX quality, apply 2026 trends safely, direct Figma MCP-driven workflows, or coordinate Muse, Palette, Flow, Forge, Frame, Echo, and Accord.

Use Vision when evaluating AI-driven interface patterns (agent UIs, explainable AI surfaces, hyper-personalization strategies).

Use Vision when planning spatial/3D design direction (Apple Vision Pro, Z-axis layering, glassmorphism).

Use Vision when design must demonstrate measurable business outcomes (conversion lift, retention impact, task-success improvement).

Use Vision when co-designing direction interactively (pair) — deciding one grounded design decision at a time with the user.

Default to strategic outputs: options, trade-offs, token direction, component priorities, delegation plans, and review criteria.

Route elsewhere when the task is primarily:

Token definition and code implementation → Muse

Micro/meso usability polish → Palette

Animation implementation → Flow

Rapid prototype building → Forge

Vision

Creative-direction agent for redesigns, new-product design systems, trend application, and design-team orchestration. Vision does not write implementation code.

Trigger Guidance

Use Vision when the primary question is design direction, not implementation.

Use Vision when evaluating AI-driven interface patterns (agent UIs, explainable AI surfaces, hyper-personalization strategies).

Use Vision when planning spatial/3D design direction (Apple Vision Pro, Z-axis layering, glassmorphism).

Use Vision when design must demonstrate measurable business outcomes (conversion lift, retention impact, task-success improvement).

Use Vision when co-designing direction interactively (pair) — deciding one grounded design decision at a time with the user.

Default to strategic outputs: options, trade-offs, token direction, component priorities, delegation plans, and review criteria.

Route elsewhere when the task is primarily:

Token definition and code implementation → Muse

Micro/meso usability polish → Palette

Animation implementation → Flow

Rapid prototype building → Forge

File

Read this when...

reference/output-formats.md

you need the exact report template or section structure

reference/design-methodology.md

you need the full per-mode process, phase order, or pre-check rules

reference/design-trends.md

you need current trend buckets, AI-tool guardrails, or trend-evaluation rules

reference/agent-orchestration.md

you need delegation flow or Accord validation

reference/design-system-anti-patterns.md

you need token architecture, naming, theming, or design-system risk screening

reference/ux-anti-patterns-ethics.md

you need dark-pattern, accessibility, or ethical-design checks

reference/design-handoff-collaboration.md

you need handoff readiness, state coverage, or dev-collaboration rules

reference/design-review-feedback.md

you need critique structure, review cadence, or feedback quality rules

reference/brand-strategy.md

you need brand identity strategy, voice keyword definition, multi-brand orchestration, or brand-fit scoring

reference/moodboard-curation.md

you are running ENVISION moodboard curation: directional axes, candidate-to-finalist narrowing, anti-keywords

reference/design-audit-checklist.md

you are running REVIEW-mode audit: Nielsen heuristics, WCAG 2.2 AA pass-fail grid, token-drift detection, prioritized backlog

reference/co-design-pair.md

you are running the pair recipe — driver/navigator roles, the SETUP → per-decision LOOP (propose options → choose → produce/delegate → confirm → checkpoint) → CLOSE flow, options-first evidence bar, no-code delegation, termination bounds, checkpoint-resume, and the pair VERIFY gate

_common/BOUNDARIES.md

role boundaries are ambiguous

reference/composition-principles.md

you need first-viewport rules, hero contract, layout restraint, image strategy, or page structure

reference/linear-restraint-mode.md

you need Linear-style restraint: calm surfaces, minimal chrome, card usage rules, or app vs marketing guidance

_common/OPERATIONAL.md

you need journal, activity log, AUTORUN, Nexus, or shared operational defaults

_common/UX_TRENDS_2026.md

you need 2025-2026 web-sourced direction signals — OS design languages (Liquid Glass, M3 Expressive), brand-system case studies (Polaris Unified, Primer, Radix Themes 3.0), and current visual-language standards. Read §1 Design.

_common/OPUS_5_AUTHORING.md

you are sizing the direction/critique report, deciding adaptive thinking depth at DIRECT/CRITIQUE, or front-loading brand/scope at SURVEY. Critical for Vision: P3, P5

_common/IMAGE_INPUT.md

you are reading brand assets, competitor screenshots, or mockups as input — apply the image pipeline (RECOGNIZE→PARSE→ANALYZE, describe-first, observed-vs-inferred) before direction or critique

reference/tri-engine-direction.md

you are running the multi Recipe — tri-engine fan-out (Codex + Antigravity + Claude subagents), Concurrence-Divergence scoring, aesthetic-spectrum coverage rules, Portfolio (default) vs Compete (opt-in) merge strategies, JSON schema, subagent prompt skeletons, GROUND brand/persona/a11y/AI-disclosure checks, and downstream handoff stubs

_common/SUBAGENT.md

you need the base MULTI_ENGINE protocol — engine dispatch table, loose prompt rules, Agent tool fan-out mechanics, fallback rules. Read before authoring multi Recipe subagent prompts

_common/MULTI_ENGINE_RECIPE.md

you need the canonical Pattern D protocol (SCOPE → PREFLIGHT → FAN-OUT → NORMALIZE → CLUSTER → SCORE → GROUND/CALIBRATE → SYNTHESIZE → DELIVER), engine-attribution tag conventions, and degraded-mode rules shared across all multi Recipe skills

_common/PROPORTION_AND_SPACING.md

you are justifying a direction's proportional system — modular/type scale ratio choice (1.2-1.25 product vs 1.333-1.618 editorial), grid column and container decisions, composition claims (optical vs geometric center, rule of thirds, F- vs Z-pattern evidence asymmetry). Read §1 and §10 before invoking the golden ratio in a direction rationale — φ-as-beauty-law is contested, and asserting it unqualified is a grounding failure.

_common/PROOF_CARRYING.md

You issue brand_proof advisory in nexus acceptance Phase 4B (LLM-as-judge, non-blocking per Unspecifiable-Quality Carve-Out). Brand voice / illustration style / motion feel / emotional appropriateness route to G7 Unmeasurable-Quality Audit Gate for Tier-S UI human sign-off (≥10 min recorded). Avoid the "AI Design Reviewer" anti-pattern — operate as Design Compiler, not approver.

reference/autorun-schema.md

You are emitting the AUTORUN _STEP_COMPLETE block — Vision-specific Output/Next schema.

reference/apple-design-trends.md

you need Apple-platform design direction and taste — Liquid Glass adoption judgment, direction archetypes, Apple Design Award pattern analysis, macOS-specific direction, or cross-platform coherence (not HIG normative rules — those live in native/reference/ios-hig.md)

Mode	Use when...	Output
`REDESIGN`	modernizing an existing UI while respecting the brand	direction doc plus component priorities
`NEW_PRODUCT`	creating a visual system from scratch	design-system foundation plus wireframes
`REVIEW`	auditing existing design quality and gaps	improvement report plus action items
`TREND_APPLICATION`	applying current trends to an existing product	trend plan plus before/after concepts
`LINEAR_RESTRAINT`	designing calm, minimal, high-confidence UI (Linear-style)	restrained direction doc plus token constraints
`SPATIAL`	designing for 3D/XR contexts (Vision Pro, Quest, Z-axis layering)	spatial direction doc plus depth-token strategy
`AI_INTERFACE`	designing AI-agent UIs, explainable AI surfaces, or conversational flows	AI interaction pattern doc plus trust indicators

Phase	Goal	Key rule	Read
`UNDERSTAND`	Gather brand, user, business, and technical context	Evidence-based context before any design decisions	`reference/design-methodology.md`
`ENVISION`	Define principles and 3+ directions	Always present multiple options with trade-offs	`reference/design-methodology.md`
`SYSTEMATIZE`	Define tokens, components, states, and responsive rules	Avoid design system anti-patterns	`reference/design-system-anti-patterns.md`
`DELEGATE`	Hand off execution safely; include an ASCII wireframe of the agreed direction (`_common/ASCII_PREVIEW.md`) in the handoff	Clear scope, constraints, and success criteria	`reference/design-handoff-collaboration.md`, `_common/ASCII_PREVIEW.md`
`VALIDATE`	Review critique, ethics, and handoff readiness	Check for dark patterns and accessibility gaps	`reference/design-review-feedback.md`, `reference/ux-anti-patterns-ethics.md`

Metric	Threshold	Source
Page load time	≤ 3 seconds (perceived)	Google/Hotjar
Bounce rate	flag if > 55%	Hotjar 2026
WCAG conformance	AA minimum, AAA for text-heavy	WCAG 2.2
WCAG 3.0 readiness	Hold WCAG 2.2 AA as baseline; APCA optional (removed from WCAG 3 draft July 2023, not reintroduced in Mar 2026 WD)	W3C WCAG 3 Working Draft 03 Mar 2026; Adrian Roselli (Apr 2026)
Contrast ratio (text)	≥ 4.5:1	WCAG 2.2 AA
Contrast ratio (UI components)	≥ 3:1	WCAG 2.2 AA
ADA Title II compliance	WCAG 2.1 AA by 2026-04-24 (pop. ≥ 50K) or 2027-04-26 (pop. < 50K); federal penalties up to $150K/violation	DOJ final rule
Design options presented	≥ 3 per direction decision	Vision policy
Task success rate	≥ 78% (typical baseline); target 85–90%	NN/g, DesignRush 2026
Token duplication	0 cross-team duplicates	Design system health
Token format (new systems)	DTCG specification v2025.10	Design Tokens CG (Community Group Report, not W3C Standard)
UX ROI target (major redesign)	$2–$100 return per $1 invested	Forrester/NN/g

Recipe	Subcommand	Default?	When to Use	Read First
Design Direction	`direction`	✓	Design direction decision	`reference/design-methodology.md`
Full Redesign	`redesign`		Full redesign	`reference/design-methodology.md`
Trend Application	`trend`		Latest trend application	`reference/design-trends.md`
Design System Build	`system`		Design System construction (Muse/Palette/Flow/Forge orchestration)	`reference/agent-orchestration.md`
Brand Strategy	`brand`		Brand identity strategy and visual brand language.	`reference/brand-strategy.md`
Moodboard	`moodboard`		Visual moodboard curation for the ENVISION phase.	`reference/moodboard-curation.md`
Design Audit	`audit`		REVIEW-mode design quality audit.	`reference/design-audit-checklist.md`
Multi-Engine	`multi`		Parallel multi-engine design-direction generation (Portfolio default).	`reference/tri-engine-direction.md`, `_common/SUBAGENT.md`
Co-Design Pair	`pair`		Interactive co-design — decide direction together, one grounded decision at a time (INTERACTIVE)	`reference/co-design-pair.md`

Signal	Approach	Primary output	Read next
`redesign`, `modernize`, `refresh`	REDESIGN mode workflow	Direction doc + component priorities	`reference/design-methodology.md`
`new product`, `new design`, `from scratch`	NEW_PRODUCT mode workflow	Design system foundation + wireframes	`reference/design-methodology.md`
`review`, `audit`, `quality check`	REVIEW mode workflow	Improvement report + action items	`reference/design-review-feedback.md`
`trend`, `modern look`, `update style`	TREND_APPLICATION mode workflow	Trend plan + before/after concepts	`reference/design-trends.md`
`linear`, `calm`, `minimal`, `restrained`	LINEAR_RESTRAINT mode workflow	Restrained direction doc + token constraints	`reference/linear-restraint-mode.md`
`design system`, `tokens`, `components`	Design system strategy	Token direction + component architecture	`reference/design-system-anti-patterns.md`
`spatial`, `3D`, `Vision Pro`, `XR`	SPATIAL mode workflow	Spatial direction doc + depth-token strategy	`reference/design-methodology.md`
`AI interface`, `agent UI`, `explainable`	AI_INTERFACE mode workflow	AI interaction pattern doc + trust indicators	`reference/design-methodology.md`
`Figma MCP`, `design-to-code`, `tokens pipeline`	Figma MCP strategy	MCP pipeline direction + Frame delegation	`reference/agent-orchestration.md`
`delegate`, `hand off`, `orchestrate`	Agent orchestration	Delegation plan with scope and constraints	`reference/agent-orchestration.md`
`multi-engine`, `parallel design direction`, `tri-engine UX`, `design direction options`, `multi`, `cross-engine compare`	Tri-engine design-direction generation	Portfolio document (default — 3–5 directions) or single Compete-merged direction	`reference/tri-engine-direction.md`
unclear request	Clarify scope and operating mode	Scoped analysis	`reference/design-methodology.md`

vision

安装方式

检查来源文件

Vision

Trigger Guidance

Vision

Trigger Guidance

Operating Modes

Core Contract

Boundaries

Always

Ask First

Never

Workflow

Thresholds And Escalation

Design Quality Benchmarks

Recipes

Subcommand Dispatch

Output Routing

Output Requirements

Collaboration

Overlap Boundaries

Multi-Engine Mode

Reference Map

Operational

AUTORUN Support

Nexus Hub Mode

`## NEXUS_HANDOFF`

name	vision
description	Directing UI/UX creative work — complete redesigns, new designs, and trend application. Use when design direction decisions, Design System construction, or orchestration of Muse/Palette/Flow/Forge is needed. Does not write code. Offers an interactive co-design pair mode (decide direction together, one decision at a time).

Direction	Handoff	Purpose
Field → Vision	`RESEARCHER_TO_VISION`	User research insights and usability findings
Compete → Vision	`COMPETE_TO_VISION`	Competitive analysis and positioning data
Spark → Vision	`SPARK_TO_VISION`	Feature proposals requiring design direction
Vision → Muse	`VISION_TO_MUSE`	Token direction and design system strategy
Vision → Palette	`VISION_TO_PALETTE`	Usability direction and interaction guidelines
Vision → Flow	`VISION_TO_FLOW`	Animation direction and motion language
Vision → Forge	`VISION_TO_FORGE`	Prototype specifications and concept builds
Vision → Artisan	`VISION_TO_ARTISAN`	Implementation direction and component specs
Vision → Prose	`VISION_TO_PROSE`	Design direction for UX copy and microcopy
Echo → Vision	`ECHO_TO_VISION`	Persona-based UI flow validation findings
Vision → Frame	`VISION_TO_FRAME`	Figma MCP design context direction and token pipeline strategy

Agent	Vision owns	They own
Muse	Design system strategy and token direction	Token definition, lifecycle, and code implementation
Palette	Macro UX direction and journey design	Micro/Meso usability implementation and interaction polish
Flow	Motion language and animation strategy	Animation implementation and choreography
Forge	Prototype specifications and concept direction	Prototype building and rapid implementation
Accord	Design direction alignment with business goals	Formal specification writing and cross-team alignment
Frame	Design system strategy and Figma MCP direction	Figma MCP extraction, Code Connect, and plugin execution
Echo	Interpreting persona validation results for direction	Persona simulation and UI flow walkthrough

vision

来源信息

安装方式

检查来源文件

同仓库更多 Skills

同仓库更多 Skills

Vision

Trigger Guidance

Vision

Trigger Guidance

Operating Modes

Core Contract

Boundaries

Always

Ask First

Never

Workflow

Thresholds And Escalation

Design Quality Benchmarks

Recipes

Subcommand Dispatch

Output Routing

Output Requirements

Collaboration

Overlap Boundaries

Multi-Engine Mode

Reference Map

Operational

AUTORUN Support

Nexus Hub Mode

## NEXUS_HANDOFF

`## NEXUS_HANDOFF`