frontend▌

The agent operates as a senior talent acquisition partner, applying structured hiring methodology to build high-performing teams efficiently and equitably.

Map concepts to semantically appropriate icons across Lucide, Heroicons, and Phosphor libraries. \n \n Provides a quick reference table of 20 common concepts with icon names across all three libraries, plus a decision tree for selecting icons when uncertain \n Covers sizing rules (16px inline to 64px decorative), consistency patterns (no style mixing, no emoji), and tree-shaking best practices to avoid bundling unused icons \n Includes semantic mapping, React/HTML templates, and library comparis

Vue JSX syntax patterns and key differences from React JSX conventions. \n \n Covers attribute naming differences (e.g., class vs className ) and Vue-specific JSX configuration \n Includes migration guidance for developers converting React JSX code to Vue \n Addresses common type errors and render function patterns when using JSX in Vue projects \n

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

Best practices and patterns for building SwiftUI views, navigation, and state management. \n \n Covers state ownership strategies (from @State and @Binding to @Observable on iOS 17+), async/await patterns with .task , and environment injection for shared dependencies \n Includes cross-cutting references for NavigationStack routing, sheet presentation, deep linking, and app-level wiring with concrete ownership rules \n Provides component-specific guidance via indexed references, with anti-pattern

Accessibility patterns for building inclusive React applications following WCAG standards. Contains 7 rules across 4 categories focused on semantic HTML, screen reader support, keyboard navigation, and user preferences.

Comprehensive guide for Medusa backend architecture, workflows, and critical implementation rules. \n \n Covers six rule categories (architecture, type safety, business logic placement, imports, data access, file organization) with specific anti-patterns and enforcement checks \n Enforces strict layer separation: Module → Workflow → API Route → Frontend, with workflows required for all mutations and only GET/POST/DELETE HTTP methods allowed \n Includes critical data handling rules: prices stored

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

Create consistent characters across multiple AI-generated images via inference.sh CLI.

Create social sharing images (Open Graph) via inference.sh CLI.