Build Figma components — buttons, inputs, cards, badges, chips, modals, and more — with variant matrices (types, sizes, states) and icon/component/content slots bound to the design system's tokens and styles. Use this when the user wants to create components, build a component library, make buttons/inputs/cards/etc.…
Cursor rule "convex" from waynesutton/promptstack, covering convex guidelines, function guidelines, new function syntax, http endpoint syntax and function registration.
GoTask is an asynchronous task management framework for Go that implements an "Everything is a Task" philosophy. It provides OS-like task manager capabilities with precise control over different granularity levels of system components.
As an AI assistant helping with iOS app releases, I should guide through the following process for successfully deploying iOS applications to the App Store.
A rule for defining tools in the MCP server is clearly and effectively defined. Ensures each tool includes a well-structured title and description that communicates its purpose, functionality, ideal usage scenarios, and expected output. This improves tool discoverability, relevance ranking, and clarity for AI agents.
Sync Storybook components and design tokens from code to Figma with storysync, measuring each variant's rendered styles rather than inferring them. Use when pushing a component library to Figma, scoring what landed against what rendered, or auditing drift between code and a Figma file.
Cursor rule "cursor_conductor_tasks_workflow" from hridaya423/conductor-tasks, covering conductor tasks: comprehensive ai development workflow, primary interaction: mcp server vs. cli, standard development workflow process (ai-driven), task complexity analysis (conceptual) and task breakdown process (using…
You have access to a persistent cross-session memory via the memory MCP server. Knowledge survives between sessions and is shared across agents working on the same project.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: