Pythonide scene

Skill Python-IDE/pythonide-skills/pythonide-scene

Official Agent Skills for building PythonIDE AppUI MiniApps, widgets, automations, and native iOS integrations with Codex, Cursor, and Claude Code.

Install

npx -y skills add Python-IDE/pythonide-skills --skill pythonide-scene

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Build or repair PythonIDE 2D scene scripts, SpriteKit-style games, touch demos, physics samples, and turtle graphics using scene.run or turtle. Use when the user wants continuous drawing, sprites, collisions, frame loops, or game-style interaction — not AppUI forms or widgets.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.4 KB, as published. Nobody here has run it

PythonIDE Scene

Execution rulebook for scene and turtle runtimes.

Read Before Coding

Do not generate AppUI or widget code for a scene/game request.

Use When

Continuous drawing, sprite movement, collisions, physics, touch loops, or shaders
Existing code imports scene and needs repair
Turtle teaching demos

Do Not Use When

The UI is a form, list, settings screen, or AppUI MiniApp
The user wants imperative UIKit controls → pythonide-automation (ui)
Static charts or business apps → pythonide-appui

Workflow

Subclass scene.Scene
Create retained nodes in setup() after self.size is valid
Per-frame logic in update(); immediate drawing only in draw()
Touch in touch_began / touch_moved / touch_ended
End with exactly one scene.run(MyScene(), ...)
Keep assets optional unless the user provides them

Correct Pattern

import scene


class Demo(scene.Scene):
    def setup(self):
        self.background_color = "#111827"
        self.ball = scene.SpriteNode(
            color="#2f80ed",
            size=(44, 44),
            position=(self.size.w / 2, self.size.h / 2),
            parent=self,
        )
        self.label = scene.LabelNode(
            "Tap to move",
            font=("Helvetica", 18),
            position=(self.size.w / 2, 80),
            parent=self,
        )

    def touch_began(self, touch):
        self.ball.run_action(
            scene.Action.move_to(touch.location.x, touch.location.y, 0.25)
        )
        self.label.text = f"{touch.location.x:.0f}, {touch.location.y:.0f}"


scene.run(Demo(), show_fps=True)

Hard Stops

No AppUI (Button, VStack, NavigationStack, etc.) inside a Scene
No blocking while True animation loops; use update() or Action
No rect, fill, text, etc. outside draw()
SpriteNode("red") treats "red" as a texture name — use SpriteNode(color="red", ...)
Do not omit scene.run(...)
image_quad / triangle_strip are not implemented

Physics And Gameplay

Use physics bodies only when collisions matter
Retain sprites, labels, and game state on self
Use node.run_action(...) for motion; calling Action.move_to(...) alone does nothing

Turtle Runtime

Use import turtle only for teaching/simple vector drawing
Do not mix turtle and scene in one deliverable unless repairing existing code

Repair Hints

Issue	Fix
Blank scene	verify `scene.run(...)` and `setup()` does not crash
Node at origin	set explicit `position` from `self.size`
No motion	`node.run_action(...)`, not bare `Action`
Dead touch	implement `touch_began(self, touch)`

Examples

examples/tap_ball/ — tap-to-move sprite demo