Skip to content
Back to search

PropMotion

Claude Code skill: make one 3D object perform in your SwiftUI app. SceneKit stages, baked choreography, hand-rolled physics, real shadows.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/dembsky--propmotion/badge.svg)](/listings/dembsky--propmotion)

HTML

<a href="/listings/dembsky--propmotion"><img src="/api/listings/dembsky--propmotion/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

The quick way, from your project directory:

npx skills add dembsky/PropMotion

Or by hand for Claude Code: copy the `scenekit-product-stages` folder into `~/.claude/skills/`, so the file lands at `~/.claude/skills/scenekit-product-stages/SKILL.md`. That folder is the skill; everything else in this repo is for you, not the agent.

Claude.ai: zip the `scenekit-product-stages` folder and upload it under Settings > Capabilities > Skills.

Then ask for something concrete. "A coin that drops onto the table, bounces twice and settles" is a better first prompt than "add 3D".

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 120 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # PropMotion
  2. A Claude Code skill for making 3D objects move well in SwiftUI apps.
  3. [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
  4. ![Claude Code](https://img.shields.io/badge/Claude%20Code-agent%20skill-d97757)
  5. ![Swift](https://img.shields.io/badge/Swift-SwiftUI%20%2B%20SceneKit-F05138?logo=swift&logoColor=white)
  6. ![Platform](https://img.shields.io/badge/platform-iOS-blue)
  7. ![Version](https://img.shields.io/badge/version-1.9.0-green)
  8. <p align="center">
  9. <img src="media/skill-demo.gif" width="360" alt="PropMotion demo reel" />
  10. </p>
  11. ## What it's for
  12. Sometimes an app needs one 3D moment. A product spinning on a pedestal. An
  13. achievement badge that rolls in and thuds. A coin that drops when the user
  14. hits a goal. Not a game, not AR. One object that moves well.
  15. SceneKit does all of this and sits in any SwiftUI layout, but the knowledge
  16. of how is scattered and half of it is undocumented. The docs tell you what
  17. an SCNNode is. They don't tell you that deferred shadows silently break
  18. under MSAA, or that the first frame of a fresh SCNView compiles shaders in
  19. the middle of your entrance animation. This skill is the missing manual,
  20. written for an agent.
  21. ## What you can make with it
  22. - an object that rolls onto the screen, settles, and casts a real shadow
  23. over your plain SwiftUI background
  24. - grab it, throw it, it bounces off the edges; every impact taps the
  25. haptic engine
  26. - weight you can see: heavy things rise slow, fall fast, land with a thud
  27. and a shiver
  28. - coins raining into a pile, marbles colliding, a wheel doing a burnout
  29. with smoke
  30. - a fruit you slice with a finger swipe: the cut face seals itself and
  31. the smaller piece tumbles to the floor
  32. - a molten-metal blob that breathes and ripples where you tap it, lit by
  33. a real HDR studio so the chrome actually reads as chrome
  34. - a stamped medallion with metal ridges and enamel cells on one mesh, or
  35. a sphere that crumbles into grit and rests on the floor
  36. - a stream of vapor out of a vent, drawn as one shader-driven sheet
  37. - several scenes cut into one continuous clip, like the one above
  38. All geometry from primitives in code, all motion baked keyframes with
  39. hand-rolled physics. No Unity, no Blender, no assets to license.
  40. ## How to work with it
  41. Two different problems, two different inputs. This is how the clip above
  42. was actually made.
  43. **Shape: show photos.** The dumbbell started as two photos of two
  44. different dumbbells, from two angles. Same for the plate and the tire.
  45. An agent reads proportions off a reference far better than off
  46. adjectives: "a rubber dumbbell with a steel grip" gets you a generic
  47. guess, a photo gets you the thing in the photo. Two shots from different
  48. angles is enough; the skill makes the agent take real-world measurements
  49. off them before modeling anything.
  50. **Motion: write the script.** The barbell scene got no pictures at all.
  51. Just a precise description of what happens and when: rolls in from the
  52. bottom, racks itself, plates slam on one by one, and at the end the whole
  53. rack tips over backward. The skill turns a description like that into a
  54. cue sheet before any code gets written, so the tighter your sequence, the
  55. closer the first take.
  56. **Iterate on what you see.** A screenshot of what's wrong beats a
  57. paragraph about what's wrong. And when motion feels off and you can't say
  58. why, ask the agent to draw the path as a red line on the floor. One look
  59. usually settles whether the problem is the trajectory or the staging.
  60. ## What's inside
  61. One SKILL.md the agent reads first, and eighteen reference files it
  62. pulls in when the task calls for them. Roughly:
  63. - how a stage is built. Transparent SCNView over your SwiftUI layout,
  64. a camera that behaves, three lights and a separate shadow rig
  65. - how motion is designed. Cue sheets before code, baked keyframes instead
  66. of timers, a tiny integrator instead of a physics engine
  67. - how it survives real fingers. Grabs, throws, trackball spins, haptics,
  68. and what happens when the user interrupts a beat halfway through
  69. - how materials get real. HDR studios for chrome, shader-deformed
  70. surfaces, relief built from heightfields, meshes cut apart at runtime
  71. - how single scenes get cut into a sequence like the clip above
  72. - the traps. Each one named, each one with the fix that actually works
  73. The writing is opinionated because the alternatives were tried and looked
  74. worse on screen.
  75. ## Install
  76. The quick way, from your project directory:
  77. ```sh
  78. npx skills add dembsky/PropMotion
  79. ```
  80. Or by hand for Claude Code: copy the `scenekit-product-stages` folder into
  81. `~/.claude/skills/`, so the file lands at
  82. `~/.claude/skills/scenekit-product-stages/SKILL.md`. That folder is the
  83. skill; everything else in this repo is for you, not the agent.
  84. Claude.ai: zip the `scenekit-product-stages` folder and upload it under
  85. Settings > Capabilities > Skills.
  86. Then ask for something concrete. "A coin that drops onto the table, bounces
  87. twice and settles" is a better first prompt than "add 3D".
  88. ## Testing
  89. `evals.md` has the scenarios I use to check the skill triggers when it
  90. should and stays quiet when it shouldn't. Run them in a fresh session.
  91. ## License
  92. MIT. Take it, ship things with it.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.