Interaction Physics
CheckedSimulates realistic object interactions & movement within a scene, enhancing immersive experiences and dynamic simulations.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add sanky369/vibe-building-skills --skill interaction-physics -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
sanky369
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned sanky369/vibe-building-skills at e9714d8dec.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- e9714d8dec
- Scanned
- 2 files, 354 lines
About this skill
What it does
This skill focuses on designing and implementing effective user interface interactions, particularly microinteractions. It teaches how to systematically approach interaction design by understanding animation principles, creating intentional feedback mechanisms (like button hover states or loading indicators), and ensuring performance and accessibility. The goal is to create intuitive and engaging experiences for users through well-designed animations and responses to their actions.
When to use it
- Creating interactive UI elements like buttons, forms, and menus.
- Designing visual feedback for user actions (e.g., button clicks, form submissions).
- Developing loading indicators or progress bars that provide clear status updates.
- Implementing transitions between different states of an application or interface.
- Adding subtle animations to guide user attention and enhance the overall experience.
Key capabilities
- Microinteraction Design: Focuses on small, contained interactions for specific tasks.
- Animation Principles: Applies principles like timing and easing to create effective animations.
- Feedback Mechanisms: Provides visual and auditory feedback in response to user actions.
- State Communication: Uses animation to clearly communicate the state of an application (loading, success, error).
- Performance Considerations: Emphasizes creating interactions that are performant and accessible.
Example prompts
- "Show me how to create a button hover effect with a 200ms ease-out transition."
- "What are some best practices for designing loading indicators?"
- "How can I use animation to guide the user's attention during form submission?"
Tips & gotchas
- Timing is crucial: Pay close attention to animation duration; too fast or slow can negatively impact usability. Refer to the provided guidelines (150-250ms for UI feedback, 300-500ms for transitions).
- Consider easing functions: Different easing functions convey different meanings and feelings – choose them intentionally.
- Prioritize clarity over complexity: Delightful animations should not distract from the user's primary task.