Generate the interaction specs your developer wishes you'd included
Developers always complain about missing hover states, error states, loading states, and mobile breakpoints. This recipe analyzes your design file and generates a complete interaction specification for every interactive element — so nothing gets lost between Figma and code.
Create a skill called "Spec Sheet". When I share a Figma file URL or design screenshots, analyze every interactive element (buttons, links, form inputs, modals, dropdowns, tabs, accordions, carousels, tooltips) and generate a complete interaction specification. For each element, document these states: default, hover, focus (with visible focus ring), active/pressed, disabled, loading, error, success, and empty. Include specific CSS values (colors, transforms, opacity, box-shadow changes), transition durations and easing curves, keyboard interaction patterns (tab order, key bindings), and mobile touch behavior. Flag any interactive element that appears to be missing states in the design. Output as a structured Markdown document organized by component.
Give your Claw your Figma file URL or design screenshots, and it identifies
every interactive element (buttons, links, forms, modals, dropdowns, tabs,
accordions) and generates a specification for each state the developer needs
to implement — including the ones you probably forgot to design.
A weekly digest of what actually matters in your tech stack
JavaScript framework churn, new CSS features, breaking changes, security advisories — there's too much noise. This recipe monitors only the tools in your stack and sends you a weekly digest of what actually matters, filtered down to changes that require action.
Extract colors, fonts, and logos from an existing site when no brand guide exists
The previous designer vanished. There's no brand guide. The only logo is a 15-year-old business card. This recipe crawls the client's existing web presence and social profiles to extract every findable brand asset — colors, fonts, logos, patterns — and compiles a basic brand guide.
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.
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.