Screenshots

Quick Reference

ContextFileStore dimensions and specsspecs.mdMarketing text overlaystext-style.mdVisual templates by categorytemplates.mdFull creation workflowworkflow.mdLearning from feedbackfeedback.md

Memory Storage

• User preferences stored at ~/screenshots/memory.md. Read on activation.
• Format:
• # Screenshots Memory
• ## Style Preferences
• style: dominant-color | gradient | minimal | dark | light
• fonts: preferred headline fonts
• frames: with-frame | frameless | floating
• tone: punchy | descriptive | minimal
• ## Learned Patterns
• templates that converted well
• font/size combinations that worked
• Create folder on first use: mkdir -p ~/screenshots

Workspace Structure

~/screenshots/ ├── memory.md # Style preferences (persistent) ├── {app-slug}/ │ ├── config.md # Brand: colors, fonts, style │ ├── raw/ # Raw simulator/device captures │ ├── v1/, v2/ # Version exports │ └── latest -> v2/ # Symlink to current └── templates/ # Reusable visual templates

Core Workflow

Intake — Get raw screenshots + app icon + brand colors Size — Generate all required dimensions per specs.md Style — Apply backgrounds, device frames, text overlays Review — Use vision to verify quality before sending Iterate — Adjust based on user feedback Export — Organize by store/device/language

Quality Checklist

Use vision model to verify EVERY screenshot set: Text readable at thumbnail size? No text in unsafe zones (corners, notch area)? Consistent style across all screenshots? Device frames match the target size? Colors harmonious with app branding? If ANY check fails → fix before presenting to user.

Versioning Rules

Never overwrite — each batch goes in v{n}/ Symlink latest to current approved version config.md stores brand decisions for regeneration Compare versions when user says "go back to the old style"