Playbook: build a swipe file that's actually usable

Playbook: build a swipe file that's actually usable
A folder of 500 screenshots is a graveyard. Build a system you'll actually search.
— Tag every save by JOB, not brand: 'hook-question', 'proof-screenshot', 'urgency-CTA'.
— Add one note per save: WHY it works. No note, no save. The reason is the asset.
— Separate hooks, bodies, and CTAs into different boards — you'll remix across them.
— Cap it. Every new save bumps the weakest one out. A swipe file is a top-50, not an archive.
— Re-read it before every brief, not when you're 'inspired'.
⭐ Pick of the week: a 'failed angles' board. Knowing what flopped saves you the test budget twice over.
Searchable beats big.