Starlight Design Review
Purpose
Judge whether the experience communicates the right thing, in the right order, with a coherent visual system and usable states across real viewports and input modes.
When it fires
- A user-facing surface is new or materially changed.
- A visual system, motion pattern, or generated asset is introduced.
- The user asks for design, taste, accessibility, or anti-slop review.
Inputs
- Product intent, audience, and primary task.
- Existing design system or taste kernel.
- Live preview or runnable surface and supported breakpoints.
- Content, asset provenance, accessibility, and performance constraints.
Workflow
- Verify the primary task and content hierarchy before judging decoration.
- Compare the implementation to its declared design language; do not impose a generic aesthetic.
- Inspect typography, spacing, contrast, alignment, density, and sentence-case labels.
- Exercise keyboard, focus, pointer, loading, empty, error, success, and reduced-motion states.
- Review mobile, tablet, and desktop for overflow, occlusion, and reading order.
- Inspect generated media for provenance, legibility, identity drift, and appropriate placement.
- Report defects by user impact with visual evidence and a precise correction.
Output contract
Return verdict, task/hierarchy assessment, system-coherence findings, accessibility findings, responsive findings, interaction-state findings, media/provenance findings, prioritized corrections, and verification receipts.
Tools & MCP
Use the host-approved browser or design connector and an existing preview when possible. Do not start arbitrary browser binaries or publish assets without authorization.
Quality bar
- No universal font, gradient, glass, grain, or spacing prescription.
- Sentence case is preserved unless official product casing requires otherwise.
- Accessibility and reduced motion are release criteria, not polish.
- Screenshots support findings but do not replace semantic or interaction checks.
Example
Input: “Review the new marketplace on desktop and phone.”
Good output: validate the purchase journey, heading order, focus names, state truth, line length, tracking, overflow, and primary CTA at both viewports, then list only evidence-backed corrections.
Built on SIP — Starlight Intelligence Protocol
Vertical: starlight-agent-skills · portable capability layer
1---2name: starlight-design-review3description: Audit a digital experience against its own design language, information hierarchy, accessibility, responsive behavior, interaction states, content truth, and visual craft. Use for websites, applications, dashboards, generated media, or frontend changes before release.4---56# Starlight Design Review78## Purpose910Judge whether the experience communicates the right thing, in the right order, with a coherent visual system and usable states across real viewports and input modes.1112## When it fires1314- A user-facing surface is new or materially changed.15- A visual system, motion pattern, or generated asset is introduced.16- The user asks for design, taste, accessibility, or anti-slop review.1718## Inputs1920- Product intent, audience, and primary task.21- Existing design system or taste kernel.22- Live preview or runnable surface and supported breakpoints.23- Content, asset provenance, accessibility, and performance constraints.2425## Workflow26271. Verify the primary task and content hierarchy before judging decoration.282. Compare the implementation to its declared design language; do not impose a generic aesthetic.293. Inspect typography, spacing, contrast, alignment, density, and sentence-case labels.304. Exercise keyboard, focus, pointer, loading, empty, error, success, and reduced-motion states.315. Review mobile, tablet, and desktop for overflow, occlusion, and reading order.326. Inspect generated media for provenance, legibility, identity drift, and appropriate placement.337. Report defects by user impact with visual evidence and a precise correction.3435## Output contract3637Return verdict, task/hierarchy assessment, system-coherence findings, accessibility findings, responsive findings, interaction-state findings, media/provenance findings, prioritized corrections, and verification receipts.3839## Tools & MCP4041Use the host-approved browser or design connector and an existing preview when possible. Do not start arbitrary browser binaries or publish assets without authorization.4243## Quality bar4445- No universal font, gradient, glass, grain, or spacing prescription.46- Sentence case is preserved unless official product casing requires otherwise.47- Accessibility and reduced motion are release criteria, not polish.48- Screenshots support findings but do not replace semantic or interaction checks.4950## Example5152Input: “Review the new marketplace on desktop and phone.”5354Good output: validate the purchase journey, heading order, focus names, state truth, line length, tracking, overflow, and primary CTA at both viewports, then list only evidence-backed corrections.5556---5758Built on SIP — Starlight Intelligence Protocol59Vertical: starlight-agent-skills · portable capability layer
frankxai