Find your landing page message
Connect a productβs value to a specific audience and write a clear first-screen message.
Create professional App Store and Google Play screenshots with automatic sizing, device frames, marketing copy, and iterative visual learning.
---
name: screenshots
slug: screenshots
version: 1.0.1
description: Create professional App Store and Google Play screenshots with automatic sizing, device frames, marketing copy, and iterative visual learning.
homepage: https://clawic.com/skills/screenshots
changelog: Preferences now persist across skill updates
metadata:
clawdbot:
emoji: π±
requires:
bins: []
os:
- linux
- darwin
- win32
displayName: Screenshots
---
## Quick Reference
| Context | File |
|---------|------|
| Store dimensions and specs | `specs.md` |
| Marketing text overlays | `text-style.md` |
| Visual templates by category | `templates.md` |
| Full creation workflow | `workflow.md` |
| Learning from feedback | `feedback.md` |
## Memory Storage
User preferences stored at `~/Clawic/data/screenshots/memory.md`. Read on activation.
**Format:**
```markdown
# 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
```
~/Clawic/data/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
1. **Intake** β Get raw screenshots + app icon + brand colors
2. **Size** β Generate all required dimensions per `specs.md`
3. **Style** β Apply backgrounds, device frames, text overlays
4. **Review** β Use vision to verify quality before sending
5. **Iterate** β Adjust based on user feedback
6. **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"
---
name: screenshots
slug: screenshots
version: 1.0.1
description: Create professional App Store and Google Play screenshots with automatic sizing, device frames, marketing copy, and iterative visual learning.
homepage: https://clawic.com/skills/screenshots
changelog: Preferences now persist across skill updates
metadata:
clawdbot:
emoji: π±
requires:
bins: []
os:
- linux
- darwin
- win32
displayName: Screenshots
---
## Quick Reference
| Context | File |
|---------|------|
| Store dimensions and specs | `specs.md` |
| Marketing text overlays | `text-style.md` |
| Visual templates by category | `templates.md` |
| Full creation workflow | `workflow.md` |
| Learning from feedback | `feedback.md` |
## Memory Storage
User preferences stored at `~/Clawic/data/screenshots/memory.md`. Read on activation.
**Format:**
```markdown
# 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
```
~/Clawic/data/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
1. **Intake** β Get raw screenshots + app icon + brand colors
2. **Size** β Generate all required dimensions per `specs.md`
3. **Style** β Apply backgrounds, device frames, text overlays
4. **Review** β Use vision to verify quality before sending
5. **Iterate** β Adjust based on user feedback
6. **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"
Imported from the listed AgentSkill.sh category. Complete supplied package files and notices are retained. Required external tools and credentials are not installed. No bundled code was executed during import. Individual agent task behavior has not been tested.