Event Store Design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
Find reusable agent skills for coding, research, design and everyday work, with practical explanations and links to the original instructions.
36 skills · Page 2 of 3
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
Automate Figma tasks via Rube MCP (Composio): files, components, design tokens, comments, exports. Always search tools first for current schemas.
Game art principles. Visual style selection, asset pipeline, animation workflow.
Automate Miro tasks via Rube MCP (Composio): boards, items, sticky notes, frames, sharing, connectors. Always search tools first for current schemas.
When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the…
Build accessible design systems with Radix UI primitives. Headless component customization, theming strategies, and compound component patterns for production-grade UI libraries.
Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case…
Build scalable design systems with Tailwind CSS, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing…
Expert in building Telegram bots that solve real problems - from simple automation to complex AI-powered bots. Covers bot architecture, the Telegram Bot API…
Use when implementing any feature or bugfix, before writing implementation code
Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with…
This skill should be used when the user asks to "design agent tools", "create tool descriptions", "reduce tool complexity", "implement MCP tools", or mentions…
Entries link to the original documentation. Check access requirements, costs and maintenance before installing.
An agent skill packages instructions and supporting files for a particular task, so an AI agent can do that task the same way each time.
Check the original project for its supported clients, installation steps and required tools. A skill’s page lists its compatibility and requirements when the project states them.
Open a skill’s page for its getting-started notes and sources, then follow the original project’s documentation for your agent.