tauri-app-haptics

When to use this skill

• Tactile feedback on mobile devices
• Haptic patterns or device support
• Fallback on unsupported devices

• "haptics", "vibration", "feedback", "mobile"

How to use this skill

1. Identify interactions requiring haptic feedback
2. Configure haptics plugin capabilities
3. Implement feedback patterns with sensible defaults
4. Handle unsupported devices with silent fallback

Outputs

• Haptic feedback plan
• Fallback behavior checklist

Scope

• Boundary: Haptics plugin usage only
• Key points: Feedback patterns and fallback strategy

References

• https://v2.tauri.app/llms.txt
• https://v2.tauri.app/plugin/haptics/
• https://v2.tauri.app/zh-cn/plugin/haptics/

Keywords

Gotchas

1. Version Compatibility: Pay attention to compatibility between the framework version and dependent libraries; APIs may vary across different versions
2. Configuration File Format: Incorrect configuration file format is the most common issue; it is recommended to use the editor's syntax check
3. Environment Variables: Ensure all necessary environment variables are set correctly; do not hardcode sensitive information
4. Dependency Conflicts: Pay attention to dependency conflicts when multiple versions coexist; use lock files to lock versions
5. Performance Pitfalls: Pay attention to performance optimization in large data volume scenarios; avoid common issues such as N+1 queries

Usage Workflow

Step 1: Environment Preparation

Step 2: Configuration Initialization

Step 3: Core Function Usage

Step 4: Testing and Verification

Step 5: Deployment and Launch