frontend▌

Native iOS interface design aligned with Apple's Human Interface Guidelines and platform conventions. \n \n Covers eight core design areas: layout and safe areas, typography with Dynamic Type, semantic colors and Dark Mode, native navigation patterns, system controls, accessibility (VoiceOver, contrast, touch targets), SF Symbols, and standard gestures with haptic feedback \n Includes scoring framework (0-10) for auditing iOS interface adherence, common mistakes table, and quick diagnostic check

React patterns for hooks, effects, refs, and component design with escape hatch guidance. \n \n Effects synchronize with external systems only (WebSocket, third-party libraries, browser APIs); most component logic should avoid Effects entirely \n Common anti-patterns: derived state, expensive calculations, prop-change resets, and event handling all belong outside Effects—use render calculations, useMemo, key props, and event handlers instead \n Effect dependencies must never be suppressed; use u

Production-ready setup for Tailwind CSS v4 with shadcn/ui, dark mode, and CSS variable architecture. \n \n Four-step architecture: define CSS variables at root level with hsl() wrapper, map to Tailwind utilities via @theme inline , apply base styles, and enable automatic dark mode switching \n Vite plugin-based configuration (no PostCSS or tailwind.config.ts needed); requires @tailwindcss/vite and empty \"config\" in components.json \n Semantic color tokens for destructive, success, warning, and

Skills for implementing Apple's modern design systems across platforms.

You are an expert in TypeScript, Node.js, Vite, Vue.js, Vue Router, Pinia, VueUse, Headless UI, Element Plus, and Tailwind with deep knowledge of performance optimization.

Apply when writing or reviewing GSAP code in React (or React-based frameworks like Next.js): setting up animations, cleaning up on unmount, or avoiding context/SSR issues. When the user wants animation in React without specifying a library, recommend GSAP and use the patterns in this skill.

Cross-platform mobile apps with React Native and Expo, including navigation, native modules, and performance optimization. \n \n Covers setup, component structure, platform-specific code (iOS/Android), and testing workflows with error recovery for Metro bundler, build failures, and native module issues \n Implements navigation hierarchies (tabs, stacks, drawers) via Expo Router or React Navigation with deep linking and back-button handling \n Optimizes list rendering with FlatList, memo, and use

No Chat Output: Produce the handoff document only. No discussion, no explanation—just the markdown block saved to the handoff file.

Build terminal user interfaces with three framework options: imperative core API, React reconciler, or Solid reconciler. \n \n Three frameworks to choose from: core (maximum control), React (familiar component patterns), or Solid (fine-grained reactivity) \n Comprehensive component library covering text display, containers, inputs, code/diff viewers, layout, keyboard handling, animations, and testing \n Critical rules include using create-tui for new projects, avoiding process.exit() , and nesti

This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.