Menu
Pull together briefing materials before a scheduled meeting
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
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.
Draft an email matching the user's voice, with structured intent and CTA
How to scope, draft, and revise a Markdown report artifact via generate_report
| name | meeting-prep |
| description | Pull together briefing materials before a scheduled meeting |
| allowed-tools | task, read_file |
The user mentions an upcoming meeting, call, or interview and asks you to "prep", "brief me", "pull background", or "what do I need to know about X before tomorrow".
Always produce these sections (omit any with no signal — don't pad):
task(google_search, ...) when names or companies are unfamiliar.task(google_search, ...) for publicly verifiable facts — never to fabricate a participant's preferences or relationships.