Screenshot Analysis & Spec Generation
Analyze website screenshots and generate detailed implementation specifications. This skill guides creation of
comprehensive SPEC.md files that document design systems extracted from visual references.
When to Use
- User provides website screenshots or design mockups
- Request for implementation specifications from visual references
- Need to extract design systems (colors, typography, spacing) from images
- Creating detailed component inventories from UI screenshots
Workflow
Step 1: Validate Prerequisites
Ensure screenshots are available in the conversation. If no images are present, request them before proceeding.
Step 2: Perform Ultra-Detailed Analysis
Analyze all provided screenshots covering these aspects:
1. Layout Architecture
- Overall page structure (header, navigation, hero, main content, sidebars, footer)
- Grid system and column layouts
- Container widths and max-widths
- Section hierarchy and nesting
2. Typography System
- Font families (identify primary, secondary, monospace)
- Font sizes for each text level (h1-h6, body, small, etc.)
- Font weights used (light, regular, medium, semibold, bold)
- Line heights and letter spacing
- Text colors and contrast ratios
3. Color Palette
- Primary brand colors
- Secondary/accent colors
- Background colors (main, sections, cards)
- Text colors (headings, body, muted, links)
- Border colors
- State colors (success, error, warning, info)
- Color codes in hex/rgb (best approximation)
4. Spacing System
- Margins between major sections
- Padding within components
- Gap spacing in flex/grid layouts
- Consistent spacing scale (e.g., 4px, 8px, 16px, 24px, 32px)
- Vertical rhythm patterns
5. Component Inventory
- Buttons (styles, sizes, states)
- Input fields and forms
- Cards and containers
- Navigation elements
- Icons and their style
- Badges, tags, labels
- Modals, tooltips, dropdowns
- List items and data tables
6. Visual Design Details
- Border radius values
- Shadow styles (box-shadow parameters)
- Border styles and thicknesses
- Background patterns or gradients
- Opacity/transparency effects
7. Images and Media
- Image locations and dimensions
- Image aspect ratios
- Icon sets (SVG, font icons, or images)
- Logo placement and size
- Decorative vs content images
- Note which images need to be sourced/created
8. Interactive Elements (if discernible)
- Hover states visible
- Active/focus states
- Transition/animation hints
- Interactive feedback patterns
9. Responsive Design (if multiple viewports shown)
- Breakpoints observable
- Layout changes per breakpoint
- Component behavior changes
- Mobile-specific patterns
10. Accessibility Considerations
- Color contrast issues
- Heading hierarchy
- Interactive element sizes
- Text readability
Step 3: Generate Comprehensive SPEC.md
Write the specification to ./SPEC.md using this structure:
# Website Implementation Specification
> Generated from screenshot analysis on [DATE]
## Overview
[2-3 sentence summary of the website's purpose and design style]
## Layout Architecture
### Page Structure
### Grid System
## Typography
### Font Families
### Text Styles
## Color System
## Spacing System
## Component Inventory
[Document each component with properties]
## Images and Assets
## Responsive Behavior
## Interactive Elements and States
## Implementation Considerations
### Design Complexity Assessment
### Observable Technical Requirements
### Accessibility Observations
### Cannot Determine from Screenshots
## Open Questions / Assumptions
## Next Steps
Step 4: Present Summary
After writing SPEC.md, provide a concise summary:
## Screenshot Analysis Complete
### Overview
[1-2 sentence description]
### Key Findings
- **Layout**: [brief description]
- **Components**: [count] distinct components identified
- **Color Palette**: [count] colors in system
- **Typography**: [primary font family], [count] type levels
- **Spacing**: [spacing scale summary]
- **Assets**: [count] images/icons to source
### Output
Full specification: `SPEC.md`
### Recommendations
[1-2 key technical recommendations]
Analysis Tips
- Start with high-level layout observations
- Progressively zoom into details
- Measure or estimate dimensions
- Identify patterns and systems
- Note uncertainties or assumptions
- Cross-reference across multiple screenshots if provided
- Higher resolution screenshots provide more accurate measurements
Notes
- All measurements are approximations; verify during implementation
- Running this analysis multiple times will overwrite existing SPEC.md
- Multi-screenshot analysis is supported and recommended for comprehensive specs
- Be explicit about states and behaviors that cannot be determined from static images
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: spec-from-screenshot3description: This skill should be used when the user asks to "analyze a screenshot", "generate implementation spec", "create SPEC.md from screenshot", "extract design specs", "spec from image", or provides website screenshots and wants detailed implementation guidance. Use when this capability is needed.4---56# Screenshot Analysis & Spec Generation78Analyze website screenshots and generate detailed implementation specifications. This skill guides creation of9comprehensive `SPEC.md` files that document design systems extracted from visual references.1011## When to Use1213- User provides website screenshots or design mockups14- Request for implementation specifications from visual references15- Need to extract design systems (colors, typography, spacing) from images16- Creating detailed component inventories from UI screenshots1718## Workflow1920### Step 1: Validate Prerequisites2122Ensure screenshots are available in the conversation. If no images are present, request them before proceeding.2324### Step 2: Perform Ultra-Detailed Analysis2526Analyze all provided screenshots covering these aspects:2728**1. Layout Architecture**2930- Overall page structure (header, navigation, hero, main content, sidebars, footer)31- Grid system and column layouts32- Container widths and max-widths33- Section hierarchy and nesting3435**2. Typography System**3637- Font families (identify primary, secondary, monospace)38- Font sizes for each text level (h1-h6, body, small, etc.)39- Font weights used (light, regular, medium, semibold, bold)40- Line heights and letter spacing41- Text colors and contrast ratios4243**3. Color Palette**4445- Primary brand colors46- Secondary/accent colors47- Background colors (main, sections, cards)48- Text colors (headings, body, muted, links)49- Border colors50- State colors (success, error, warning, info)51- Color codes in hex/rgb (best approximation)5253**4. Spacing System**5455- Margins between major sections56- Padding within components57- Gap spacing in flex/grid layouts58- Consistent spacing scale (e.g., 4px, 8px, 16px, 24px, 32px)59- Vertical rhythm patterns6061**5. Component Inventory**6263- Buttons (styles, sizes, states)64- Input fields and forms65- Cards and containers66- Navigation elements67- Icons and their style68- Badges, tags, labels69- Modals, tooltips, dropdowns70- List items and data tables7172**6. Visual Design Details**7374- Border radius values75- Shadow styles (box-shadow parameters)76- Border styles and thicknesses77- Background patterns or gradients78- Opacity/transparency effects7980**7. Images and Media**8182- Image locations and dimensions83- Image aspect ratios84- Icon sets (SVG, font icons, or images)85- Logo placement and size86- Decorative vs content images87- Note which images need to be sourced/created8889**8. Interactive Elements** (if discernible)9091- Hover states visible92- Active/focus states93- Transition/animation hints94- Interactive feedback patterns9596**9. Responsive Design** (if multiple viewports shown)9798- Breakpoints observable99- Layout changes per breakpoint100- Component behavior changes101- Mobile-specific patterns102103**10. Accessibility Considerations**104105- Color contrast issues106- Heading hierarchy107- Interactive element sizes108- Text readability109110### Step 3: Generate Comprehensive SPEC.md111112Write the specification to `./SPEC.md` using this structure:113114```markdown115# Website Implementation Specification116117> Generated from screenshot analysis on [DATE]118119## Overview120[2-3 sentence summary of the website's purpose and design style]121122## Layout Architecture123### Page Structure124### Grid System125126## Typography127### Font Families128### Text Styles129130## Color System131132## Spacing System133134## Component Inventory135[Document each component with properties]136137## Images and Assets138139## Responsive Behavior140141## Interactive Elements and States142143## Implementation Considerations144### Design Complexity Assessment145### Observable Technical Requirements146### Accessibility Observations147### Cannot Determine from Screenshots148149## Open Questions / Assumptions150151## Next Steps152```153154### Step 4: Present Summary155156After writing SPEC.md, provide a concise summary:157158```159## Screenshot Analysis Complete160161### Overview162[1-2 sentence description]163164### Key Findings165- **Layout**: [brief description]166- **Components**: [count] distinct components identified167- **Color Palette**: [count] colors in system168- **Typography**: [primary font family], [count] type levels169- **Spacing**: [spacing scale summary]170- **Assets**: [count] images/icons to source171172### Output173Full specification: `SPEC.md`174175### Recommendations176[1-2 key technical recommendations]177```178179## Analysis Tips180181- Start with high-level layout observations182- Progressively zoom into details183- Measure or estimate dimensions184- Identify patterns and systems185- Note uncertainties or assumptions186- Cross-reference across multiple screenshots if provided187- Higher resolution screenshots provide more accurate measurements188189## Notes190191- All measurements are approximations; verify during implementation192- Running this analysis multiple times will overwrite existing SPEC.md193- Multi-screenshot analysis is supported and recommended for comprehensive specs194- Be explicit about states and behaviors that cannot be determined from static images195196---197> Converted and distributed by [TomeVault](https://tomevault.io/claim/sablier-labs) — claim your Tome and manage your conversions.198<!-- tomevault:4.0:skill_md:2026-04-13 -->