agentleFS
moasqmoasq/ios-dev-agent/.agents/skills/haptics/SKILL.md

haptics

Skill4 starsChanged 6 months agoMITView on GitHub

Use when adding tactile feedback. Covers UIImpactFeedbackGenerator, UINotificationFeedbackGenerator, CoreHaptics custom patterns.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this guide when adding tactile feedback to interactions.

    line 8
  2. Very specific:

    Call generator.prepare() before use for lower latency

    line 30
  3. Very specific:

    Check hardware support: CHHapticEngine.capabilitiesForHardware().supportsHaptics

    line 31
  4. Very specific:

    Use .light for subtle confirmations, .medium for standard taps, .heavy for emphasis

    line 32
  5. Very specific:

    Use .success for completed actions, .warning for caution, .error for failures

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Haptic Feedback

Use this guide when adding tactile feedback to interactions.

Quick Reference

Impact Feedback (taps, collisions)

UIImpactFeedbackGenerator(style: .medium).impactOccurred()

Styles: .light, .medium, .heavy, .soft, .rigid

Notification Feedback (outcomes)

UINotificationFeedbackGenerator().notificationOccurred(.success)

Types: .success, .warning, .error

Selection Feedback (picker changes)

UISelectionFeedbackGenerator().selectionChanged()

Best Practices

  • Call generator.prepare() before use for lower latency
  • Check hardware support: CHHapticEngine.capabilitiesForHardware().supportsHaptics
  • Use .light for subtle confirmations, .medium for standard taps, .heavy for emphasis
  • Use .success for completed actions, .warning for caution, .error for failures

CoreHaptics (Custom Patterns)

import CoreHaptics

let engine = try CHHapticEngine()
try engine.start()

let event = CHHapticEvent(
    eventType: .hapticTransient,
    parameters: [
        CHHapticEventParameter(parameterID: .hapticIntensity, value: 0.8),
        CHHapticEventParameter(parameterID: .hapticSharpness, value: 0.5)
    ],
    relativeTime: 0
)

let pattern = try CHHapticPattern(events: [event], parameters: [])
let player = try engine.makePlayer(with: pattern)
try player.start(atTime: 0)

When to Use

ActionHaptic
Button tap.light impact
Toggle switchSelection changed
Delete action.warning notification
Save success.success notification
Slider snapSelection changed
Error state.error notification

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.