Menu
Draft an email matching the user's voice, with structured intent and CTA
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Reverse-lookup glossary that turns a vague description of a web animation or motion effect into its exact term ("the bouncy thing when a popover opens" → Pop in; "the iOS rubber-band scroll" → Rubber-banding). Use when the user asks "what's it called when…", or describes a motion effect without knowing its name and wants the right word to prompt an AI or designer with. For naming an effect, not designing or building one.
Reviews animation and motion code against a high craft bar derived from Emil Kowalski's design engineering philosophy. Default to flagging; approval is earned.
Structured approach to finding and synthesizing information from the user's knowledge base
Pull together briefing materials before a scheduled meeting
Build distinctive, production-quality UI. Use when creating or reshaping user-facing interfaces, components, pages, layouts, visual redesigns, responsive behavior, loading/error/empty states, or accessibility-sensitive frontend work.
How to scope, draft, and revise a Markdown report artifact via generate_report
| name | email-drafting |
| description | Draft an email matching the user's voice, with structured intent and CTA |
"Draft an email to ...", "reply to this thread", "write a follow-up to X". Plain "summarize the email" is not in scope — that's a comprehension task.
Search the KB for prior emails from the user to similar audiences (same recipient, same topic class). Mirror tone, opening style, sign-off, and length distribution. If there is no precedent, default to: warm, direct, no filler, short paragraphs, one clear ask.
Every draft includes, in this order:
Re: unless replying.End your message with: "Want me to make it shorter, more formal, or add a different angle?" — give the user one obvious next step.