frontend▌

Build custom authentication flows and visually brand Clerk components with hooks and appearance styling. \n \n Provides useSignIn and useSignUp hooks for building custom sign-in/sign-up UI; API differs between Core 2 and current SDK versions \n Appearance customization via variables (colors, typography, borders), options (logo, social button layout), and pre-built themes (dark, neobrutalism, shadcn, simple) \n shadcn theme automatically matches shadcn/ui projects when components.json is present;

Build professional, standardized financial data packs for private equity, investment banking, and asset management. Transform financial data from CIMs, offering memorandums, SEC filings, web search, or MCP server access into polished Excel workbooks ready for investment committee review.

$22

Production patterns for optimizing Bazel builds in large-scale monorepos. \n \n Covers WORKSPACE configuration, .bazelrc tuning, remote caching/execution setup, and platform-specific build constraints \n Includes templates for TypeScript and Python libraries, custom Docker rules, and dependency analysis via Bazel query \n Provides performance profiling techniques, memory optimization strategies, and best practices for fine-grained targets and visibility enforcement \n Addresses monorepo patterns

Production-grade UI design system with design tokens, layout rules, motion guidelines, and accessibility validation. \n \n Provides structured design tokens for colors, typography, spacing, shadows, and breakpoints with 8px-based spacing scale \n Includes section-by-section component architecture with responsive breakpoints (mobile-first, 640/768/1024/1280px) \n Covers motion specifications with CSS variables for duration and easing, plus hover and transition patterns \n Built-in WCAG 2.1 AA acc

React and Next.js patterns for component composition, state management, performance optimization, and accessible UI. \n \n Covers component patterns including composition, compound components, and render props for flexible, reusable UI architecture \n Provides custom hooks for state management, async data fetching, debouncing, and form handling with validation \n Includes performance techniques: memoization, code splitting with lazy loading, and virtualization for large lists \n Demonstrates err

React and Next.js performance optimization guidelines across 45 rules in 8 priority categories. \n \n Covers critical waterfalls elimination, bundle size optimization, and server-side performance with specific patterns like Promise.all, dynamic imports, and React.cache() \n Includes medium-priority rules for re-render optimization, rendering performance, and JavaScript efficiency with concrete code examples \n Organized by impact level with prefixed rule names (async-, bundle-, server-, client-,

AI-powered logo design with prompting strategies, scalability rules, and iteration workflows. \n \n Covers six logo types (wordmark, lettermark, pictorial, abstract, mascot, combination) with use cases and design considerations for each \n Provides tested prompt structures and keywords that work with AI image generators, plus explicit anti-patterns to avoid (text rendering, photorealism, gradients) \n Includes scalability checklist ensuring logos work from 16px favicons to billboards, plus color

Build and export iOS/macOS apps with xcodebuild for App Store Connect upload. \n \n Handles both iOS (IPA) and macOS (PKG) builds through archive and export workflows with xcodebuild \n Requires valid signing identity, provisioning profiles, and Xcode command line tools configured \n Integrates with asc CLI for uploading builds; macOS uploads require explicit version and build number parameters \n Build numbers must be unique and higher than previous uploads; includes commands to check existing

Essential reference guide for ADK agent development, covering spec-driven workflow, code preservation rules, and operational best practices. \n \n Read DESIGN_SPEC.md first as your primary source of truth; all implementation decisions must align with it \n Follow four mandatory phases: understand spec, build and implement, evaluate (using /adk-eval-guide ), and deploy with human approval \n Preserve all unrelated code when making modifications; only alter explicitly targeted segments and never c