smithery/0xhoneyjar

physics-reference

Design physics tables and timing rationale

Installation

$ npx skills add smithery/0xhoneyjar --skill physics-reference

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/0xhoneyjar.

npx skills add smithery/0xhoneyjar

Browse all from smithery/0xhoneyjar

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,965 B
  • docs SUMMARY.md 67 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Physics Reference

Detailed physics tables for the crafting skill. Loaded on-demand.

The Complete Physics Table

Effect Sync Timing Confirmation Easing Spring
Financial Pessimistic 800ms Required ease-out 200/30
Destructive Pessimistic 600ms Required ease-out 200/30
Soft Delete Optimistic 200ms Toast+Undo spring 500/30
Standard Optimistic 200ms None spring 500/30
Navigation Immediate 150ms None ease —
Local State Immediate 100ms None spring 700/35

Timing Rationale

800ms (Financial)

Time needed for users to:

  1. Read and verify the amount
  2. Mentally commit to the action
  3. Feel the weight of irreversibility

Faster = anxiety. Slower = sluggish. 800ms is calibrated.

600ms (Destructive)

Permanent deletion needs deliberation but less than money. Warning color + timing = sufficient gravity.

200ms (Standard)

Research shows 200ms is perceived as "instant" while allowing visual feedback.

  • <100ms: Users miss the confirmation
  • >300ms: Feels laggy

100ms (Local)

No network latency to hide. Users expect immediate response. Any delay feels broken.

Sync Strategy Details

Pessimistic

User clicks → Loading state → Server confirms → UI updates
  • Never show success before server confirms
  • Cancel button always visible during loading
  • Error state has clear recovery path

Optimistic

User clicks → UI updates immediately → Server confirms (or rollback)
  • Requires onMutate for immediate update
  • Requires onError for rollback
  • User sees instant feedback

Immediate

User clicks → UI updates → No server call
  • Pure client state (theme, toggles)
  • useState or context only
  • Zero loading states