fat-marker-sketch

Classifies uploaded screenshots, sketches, and mockups to extract design intent without copying annotation styling.

4|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/laicluse/agent-fieldkit --skill fat-marker-sketch-laicluse
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fat-marker-sketch
Source: https://github.com/laicluse/agent-fieldkit/tree/main/.agents/plugins/generated/eye-of-the-beholder/skills/fat-marker-sketch
Command: npx skills add https://github.com/laicluse/agent-fieldkit --skill fat-marker-sketch-laicluse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When users upload images as design feedback, agents often misread them: copying red arrows and callout bubbles into the product UI, or treating every image as a rough sketch. This Skill classifies the artifact first, then separates genuine design evidence from annotation-tool styling so only the user's actual intent reaches the implementation. ## Core Features & Use Cases - Artifact classification: Distinguishes annotated screenshots, clean screenshots, low-fidelity sketches, design references, and unknown images using accompanying words, visible layers, filename provenance, and metadata. - Signal extraction: Pulls complaint, target area, direction, content, and topology from an image while discarding annotation styling such as arrow colors, callout bubbles, and screenshot-tool chrome. - Interpretation readback: Produces a structured readback of the classification and extracted intent before the first edit, and routes stated match intent to visual-inspection or open direction to taste-test. - Use Case: A user uploads a CleanShot capture with a red arrow pointing at a cramped header. The Skill reads it as an annotated screenshot, keeps the complaint and target, ignores the arrow's color and styling, and adds spacing using the product's existing design language. ## Quick Start Upload an annotated screenshot or sketch and ask the agent to interpret it as design feedback before making any UI changes.

Frequently Asked Questions about fat-marker-sketch

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

FAQPage Schema
How do I interpret an annotated screenshot as design feedback?▼

Classify the image first, then extract the complaint, target area, direction, content, and topology from the marks. Discard the annotation tool's visual styling such as arrow colors and callout bubbles, since those pixels belong to the tool, not the product design.

What is a fat-marker sketch in product design?▼

A fat-marker sketch is a low-fidelity drawing made with a pen so thick that detail is deliberately impossible, a term from Basecamp's Shape Up. It proposes rough structure and topology, not literal pixels, so only hierarchy and intent should be preserved.

Does a CleanShot filename mean the image has annotations?▼

No. A filename containing CleanShot, Screenshot, or similar capture conventions indicates screenshot provenance only, not annotation presence. Confirm the annotation layer visually, and treat renamed or generic filenames as weak evidence in either direction.

When should screenshot pixels be matched exactly in the UI?▼

Only when the user states match intent, such as saying pixel-perfect, match this exactly, or naming a real product element or Figma frame to reproduce. Capture fidelity alone does not establish match intent; read the user's accompanying words.

Why does copying annotation styling into the UI cause problems?▼

Arrow colors, callout bubbles, highlighter strokes, and hand-drawn boxes express the annotation tool's voice, not design decisions. Copying them introduces unintended colors and containers; only the encoded meaning, such as grouped distinctions, should survive.