building▌

Frameworks for building and scaling product communities from 18 leaders at Notion, Figma, and WordPress. \n \n Identify your community type (user, agency, or partner) and find the \"atomic unit of sharing\" that members naturally want to showcase \n Start with listening to early members through 1:1 calls before imposing structure; begin with your 20 most vocal organic supporters \n Design for quality over rapid growth by implementing application processes and cohort-based onboarding to maintain

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

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

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

Build and deploy applications on the inference.sh platform. Apps can be written in Python or Node.js.

Stateful AI agents on Cloudflare Workers with WebSocket communication, persistent state, and scheduled tasks. \n \n Build agents using the Agents SDK that maintain state across client reconnections and scale via Durable Objects \n Support real-time WebSocket communication, HTTP endpoints, and automatic message history for chat-focused agents \n Schedule background tasks with delay, specific dates, or cron expressions; query state with embedded SQLite \n Extend Agent or AIChatAgent base classes,

Master Flutter's constraint system to build responsive, overflow-free layouts efficiently. \n \n Core principle: constraints flow down, sizes flow up, parents set position. Never pass unbounded constraints in flex boxes or scrollable regions. \n Use Row / Column for linear layouts, Expanded / Flexible for space distribution, Stack for overlapping elements, and SizedBox for tight constraints. \n Apply LayoutBuilder for responsive sizing or conditional rendering for adaptive layouts across mobile,

Validated Flutter forms with field-level error handling and submission workflows. \n \n Requires StatefulWidget hosting with a persistent GlobalKey<FormState> to manage form state and validation across rebuilds \n Use TextFormField widgets with validator() callbacks that return error strings on failure or null on success \n Call _formKey.currentState!.validate() on submit to trigger all validators and automatically display error messages below fields \n Includes complete code example demons

Build and deploy remote MCP servers on Cloudflare Workers with tools and OAuth authentication. \n \n Define tools using Zod-validated parameters and expose them via MCP protocol; supports text responses, external API calls, and database bindings \n Two deployment modes: public servers (no auth) and OAuth-protected servers (GitHub, Google, Auth0, and other providers) \n Test locally with MCP Inspector, deploy with Wrangler CLI, and connect clients via Claude Desktop or other MCP-compatible applic

Complete guide for building native Expo apps with routing, styling, components, and platform conventions. \n \n Covers Expo Router fundamentals, native tabs, stack navigation, modals, and form sheets with detailed route structure conventions \n Includes styling rules aligned with Apple Human Interface Guidelines: flexbox layouts, safe area handling, animations, shadows via CSS boxShadow , and responsive design patterns \n Documents library preferences (expo-image for SF Symbols, expo-audio, expo