Stop receiving 50x50 logos and watermarked stock photos
Clients send tiny JPEGs of their logo cropped from Facebook, watermarked Google Images screenshots, and photos from 2009 flip phones. This recipe checks every asset the client sends, flags what's unusable, and generates a specific re-request telling them exactly what you need.
Create a skill called "Asset Inspector". When I receive client assets (images, logos, photos), inspect each file and assess: resolution (flag anything under the required dimensions for its intended use), file format (flag raster logos that should be vector, CMYK images), watermark detection, blur and compression artifact detection, and color space. Let me define per-project asset requirements (e.g., "hero image: min 1920x1080, logo: SVG or PNG at 1024x1024+"). For each issue found, generate a specific, client-friendly re-request email explaining what's needed, in what format, at what minimum resolution, and — where helpful — where the client can likely find the original file (e.g., "Ask your previous designer for the .ai or .eps source file"). Output an asset status report showing pass/fail per file.
When client assets arrive (via email, shared folder, or direct upload),
your Claw inspects each file: resolution, format, color space, whether
it has a watermark, and whether it's appropriate for its intended use
(logo for header, hero photo, product image, etc.).
Catch "one more thing" before it eats your margin
Clients always slip in extra pages, features, and revisions that weren't in the original scope. This recipe monitors your project communication and flags scope-expanding requests the moment they appear — with a draft change order ready to send.
Turn "make it pop" into actual design direction
Clients say "make it pop" and "I'll know it when I see it." This recipe takes vague client feedback and translates it into specific, actionable design tasks — with visual reference examples pulled from the web.
Generate button labels, error messages, tooltips, and empty states
Nobody budgets for UX writing but it makes or breaks usability. This recipe generates complete microcopy sets for your UI components — error messages that actually help, empty states that guide action, button labels that are clear, and tooltips that explain without patronizing.
Turn finished projects into polished portfolio pieces without the 10-hour writing slog
Your portfolio is 3 years outdated because writing case studies takes longer than the projects themselves. This recipe takes your project files, Figma history, and a few bullet points from you, and drafts a complete case study — challenge, process, solution, results.