frontend▌

Duit enables backend-driven UI in Flutter applications. The server controls both data and layout via JSON, allowing UI updates without app releases.

Design system toolkit for generating tokens, documenting components, and enabling design-dev handoff. \n \n Generates complete design tokens (colors, typography, spacing, shadows, animations) from a single brand color in multiple formats (JSON, CSS, SCSS) \n Includes three style presets (modern, classic, playful) and an 8pt spacing grid system with responsive breakpoints \n Covers component architecture, accessibility compliance, and developer handoff documentation for maintaining visual consist

Utility-first CSS framework for rapid UI development with responsive design and dark mode support. \n \n Provides single-purpose utility classes for layout, spacing, typography, colors, and effects without writing custom CSS \n Includes mobile-first responsive breakpoints (sm, md, lg, xl, 2xl) and built-in dark mode with class or media strategy \n Supports framework integration with React, Next.js, Vue, Svelte, and others; includes official plugins for forms, typography, and aspect ratios \n Off

Comprehensive Vue 3 component library with 60+ UI components and full customization support. \n \n Covers installation, setup, and 25+ documented components including forms, tables, dialogs, navigation, and feedback elements \n Supports both full and on-demand imports, with Composition API examples and TypeScript support \n Includes theme customization, internationalization (i18n), and global configuration options \n Organized documentation mirrors official Element Plus structure with guides, co

SDK-first frontend integration for Medusa storefronts with React Query patterns and critical API calling rules. \n \n Always use the Medusa JS SDK for all API requests—never use regular fetch(), as it lacks required headers (publishable API key for store routes, auth for admin routes) \n Pass plain JavaScript objects to SDK methods; never use JSON.stringify() on body parameters, as the SDK handles serialization automatically \n Use useQuery for GET requests and useMutation for POST/DELETE reques

Search and extract HTTP traffic, audit findings, and security data from Burp Suite project files via CLI. \n \n Queries proxy history, site map, and audit items using regex patterns on request/response headers and bodies \n Requires Burp Suite Professional and the burpsuite-project-file-parser extension; delegates parsing to Burp's Java runtime \n Enforces sub-component filters (headers, bodies) instead of full dumps to prevent gigabyte-scale data retrieval; mandatory truncation of body content

Refactor SwiftUI views toward small, explicit, stable types with MV-first defaults. \n \n Enforces view ordering (environment, state, computed vars, init, body, helpers) and strongly prefers dedicated subview types over computed some View helpers for non-trivial sections \n Defaults to Model-View architecture: local state in views, shared dependencies in environment, business logic in services/models, view models only when explicitly required or already present \n Extracts actions and side effec

Query Hyperliquid market data, order books, metadata, and execute withdrawals via Grimoire CLI. \n \n Supports six command categories: mid prices, L2 order books, open orders, perpetual metadata, spot metadata, and USDC withdrawals \n Output formats include JSON, table, and spell (for snapshot-based agent inputs); withdrawals require explicit user confirmation and keystore credentials \n Read-only commands (mids, l2-book, open-orders, meta, spot-meta) return market snapshots; stateful withdraw a

Full-stack React framework with file-system routing, Server Components, and built-in performance optimization. \n \n File-system based routing with layouts, dynamic segments, and catch-all routes; supports both static generation (SSG) and server-side rendering (SSR) \n Server Components for data fetching directly in components; Client Components with the use hook for interactive features \n Server Actions for handling data mutations and form submissions without separate API endpoints \n Built-in

Custom UI extensions for Medusa Admin dashboard using the Admin SDK and Medusa UI components. \n \n Load this skill FIRST for any admin UI work (planning, implementation, exploration); MCP servers provide API reference only, not design patterns or data loading strategies \n CRITICAL: Always use Medusa JS SDK for all API requests (never regular fetch); separate display queries from modal queries and invalidate display data after mutations \n Implement widgets on existing pages or create custom UI