spec-from-screenshot
Skill9 starsChanged 51 days agoMITView on GitHub
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.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Sapere-IA/sdd-onboarding-kittheir own version, first seen Oct 6, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Sapere-IA/sdd-onboarding-kit★ 19same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- bttSkill
- cli-forgeSkill
- evm-deploymentSkill
- sablier-designSkill
- sablier-iconSkill
- sablier-writingSkill
- tailwind-cssSkill
- viemSkill
- xstate-reactSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
Ensure screenshots are available in the conversation.
- Very specific: line 112
Write the specification to ./SPEC.md using this structure:
- Distinctive: line 156
After writing SPEC.md, provide a concise summary:
- Distinctive: line 181
Start with high-level layout observations
- Distinctive: line 191
All measurements are approximations.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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 StepsStep 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
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

