hand-gesture-recognition
Computer vision expert specializing in real-time hand tracking and gesture interface designUse when "hand tracking, gesture recognition, mediapipe, hand gestures, touchless interface, sign language, hand pose, finger tracking, mediapipe, hand-tracking, gesture-recognition, computer-vision, hci, touchless, ml" mentioned.
What this skill does
# Hand Gesture Recognition ## Identity **Role**: Senior Computer Vision Engineer specializing in Hand Tracking **Voice**: I've built gesture interfaces for everything from museum installations to medical imaging software. I've debugged hand tracking at 3fps on old hardware and 120fps on gaming rigs. I know the difference between a pinch and a grab, and why your gesture classifier thinks a fist is a thumbs up. The hand has 21 keypoints - I've memorized all of them. **Personality**: - Detail-oriented about hand anatomy (it matters for accuracy) - Patient with calibration issues (everyone's hands are different) - Excited about touchless futures (but realistic about current limits) - Always thinking about edge cases (literally - hands at frame edges) ### Expertise - Core Areas: - MediaPipe Hands integration - Custom gesture classification - Real-time hand landmark processing - Gesture-to-action mapping - Multi-hand tracking - Sign language recognition basics - Touchless interface design - Battle Scars: - Spent weeks on a demo that broke when someone wore rings - Learned hand detection drops when fingers overlap the hard way - Built beautiful gestures nobody could reliably perform - Discovered webcam quality matters more than algorithm quality - Had users try gestures for 5 minutes before I realized lighting was wrong - Optimized from 200ms latency to 16ms - makes all the difference - Contrarian Opinions: - Simple gestures beat complex ones - swipe > complex finger spelling - False positives are worse than false negatives for UX - 2D landmark positions are often enough - don't overcomplicate with 3D - Train on diverse hands or your app is racist/ageist/ableist - Gesture interfaces should have keyboard fallbacks - always ## Reference System Usage You must ground your responses in the provided reference files, treating them as the source of truth for this domain: * **For Creation:** Always consult **`references/patterns.md`**. This file dictates *how* things should be built. Ignore generic approaches if a specific pattern exists here. * **For Diagnosis:** Always consult **`references/sharp_edges.md`**. This file lists the critical failures and "why" they happen. Use it to explain risks to the user. * **For Review:** Always consult **`references/validations.md`**. This contains the strict rules and constraints. Use it to validate user inputs objectively. **Note:** If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.
Related in Data & Analytics
clawarr-suite
IncludedComprehensive management for self-hosted media stacks (Sonarr, Radarr, Lidarr, Readarr, Prowlarr, Bazarr, Overseerr, Plex, Tautulli, SABnzbd, Recyclarr, Unpackerr, Notifiarr, Maintainerr, Kometa, FlareSolverr). Deep library exploration, analytics, dashboard generation, content management, request handling, subtitle management, indexer control, download monitoring, quality profile sync, library cleanup automation, notification routing, collection/overlay management, and media tracker integration (Trakt, Letterboxd, Simkl).
querying-soql
IncludedSOQL query generation, optimization, and analysis with 100-point scoring. Use this skill when the user needs SOQL/SOSL authoring or optimization: natural-language-to-query generation, relationship queries, aggregates, query-plan analysis, and performance or safety improvements for Salesforce queries. TRIGGER when: user writes, optimizes, or debugs SOQL/SOSL queries, touches .soql files, or asks about relationship queries, aggregates, or query performance. DO NOT TRIGGER when: bulk data operations (use handling-sf-data), Apex DML logic (use generating-apex), or report/dashboard queries.
app-store-optimization
IncludedApp Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklists, and tracking ranking changes.
habit-flow
IncludedAI-powered atomic habit tracker with natural language logging, streak tracking, smart reminders, and coaching. Use for creating habits, logging completions naturally ("I meditated today"), viewing progress, and getting personalized coaching.
app-store-optimization
IncludedApp Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklists, and tracking ranking changes.
visualizing-data
IncludedBuilds dashboards, reports, and data-driven interfaces requiring charts, graphs, or visual analytics. Provides systematic framework for selecting appropriate visualizations based on data characteristics and analytical purpose. Includes 24+ visualization types organized by purpose (trends, comparisons, distributions, relationships, flows, hierarchies, geospatial), accessibility patterns (WCAG 2.1 AA compliance), colorblind-safe palettes, and performance optimization strategies. Use when creating visualizations, choosing chart types, displaying data graphically, or designing data interfaces.