- Depot CiModify Base Depot CI workflows, especially PR cost controls, path filters, runner sizing, or optional integration checks.base/base910
- Update Docs IndexUpdate llms.txt and llms-full.txt, the repo's index of every Markdown doc. Use after adding, moving, deleting, or editing any .md file, or when `just check::docs-index` fails.base/base910
- Verify BaseVerifies Base local-devnet transaction inclusion using existing devnet commands and Foundry cast. Use when checking Base changes or demonstrating sequencer transaction inclusion.base/base910
- Animation VocabularyReverse-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.base/docs343
- Apple DesignApple's approach to interface design and fluid, physical motion, translated for the web. Use when building or reviewing gesture-driven UI, spring animations, drag/swipe/sheet interactions, momentum and interruptible transitions, translucent materials and depth, typography (optical sizing, tracking, leading), reduced-motion, or the design foundations (feedback, spatial consistency, restraint) behind Apple-style interfaces.base/docs343
- Emil Design EngThis skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.base/docs343
- Find Animation OpportunitiesSearch a codebase or UI for places that don't animate but should, and reject everything that shouldn't. Read-only; it proposes motion with exact values, it does not implement it. Use when the user asks "what could be animated here?" or wants to "make this feel more alive". For fixing existing animations, use improve-animations or review-animations instead.base/docs343
- Improve AnimationsSurvey a codebase's animation and motion code as a senior motion advisor, then produce a prioritized audit and self-contained implementation plans for other agents (or cheaper models) to execute. Read-only on source code — it plans improvements, it does not apply them. Use when the user asks to "improve the animations", "audit the motion", "make this app feel better", or wants a roadmap of animation fixes rather than a review of a single diff.base/docs343
- Pick Ui LibraryPick the right library for a given frontend task from a curated, opinionated list — numbers, OTP inputs, charts, command menus, virtualization, drag and drop, toasts, state, styling, and more. Only runs when explicitly invoked; it does not trigger on its own.base/docs343
- PrototypeBuild multiple genuinely different versions of a UI piece you describe, rendered behind a visual picker so you can flip through them live and promote the one that feels right. Only runs when explicitly invoked; it does not trigger on its own.base/docs343
- Review AnimationsReviews animation and motion code against a high craft bar derived from Emil Kowalski's design engineering philosophy. Default to flagging; approval is earned.base/docs343
- Create Trading AgentScaffold Base trading agents from a plain-English strategy using the `agents/trading-agent` CLI. Use when asked to create a new trading agent project, choose wallet/tool/LLM combinations for a trading scaffold, or drive trading-agent creation headlessly from another agent.base/demos92
- Changelog GrillInterview the user relentlessly about a changelog or ADR template until reaching shared understanding. Proposes point-form edits after each round.base/base-std19
- Technical DocumentConvert changelog/TEMPLATE_POINT_FORM.md from point form into a written technical specification. Use the exact template structure. Apply ASD-STE100-inspired Simplified Technical English and Google technical-writing guidance while preserving technical facts, uncertainty, and scope.base/base-std19