القائمة
Design physics tables and timing rationale
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Generate or validate UI with design physics
Slot external knowledge into Rune constructs
Validate data correctness in web3 components
Capture taste preferences for design physics
Hypothesis validation and closed-loop learning
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
| name | physics-reference |
| description | Design physics tables and timing rationale |
| user-invocable | false |
Detailed physics tables for the crafting skill. Loaded on-demand.
| 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 |
Time needed for users to:
Faster = anxiety. Slower = sluggish. 800ms is calibrated.
Permanent deletion needs deliberation but less than money. Warning color + timing = sufficient gravity.
Research shows 200ms is perceived as "instant" while allowing visual feedback.
300ms: Feels laggy
No network latency to hide. Users expect immediate response. Any delay feels broken.
User clicks → Loading state → Server confirms → UI updates
User clicks → UI updates immediately → Server confirms (or rollback)
onMutate for immediate updateonError for rollbackUser clicks → UI updates → No server call