Pythonide
Official Agent Skills for building PythonIDE AppUI MiniApps, widgets, automations, and native iOS integrations with Codex, Cursor, and Claude Code.
npx -y skills add Python-IDE/pythonide-skills --skill pythonideAssembled 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
Route PythonIDE tasks to the correct runtime and companion skill (AppUI MiniApp, widget, scene, native modules, automation). Use when the user asks to build, fix, or choose a PythonIDE app, script, widget, game, or iOS capability workflow.
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
4.0 KB, as published. Nobody here has run it
PythonIDE Router
Thin routing skill for external coding agents. Load a focused companion skill before generating code.
Read First
- AI one-page guide
- llms-full.txt for hard rules and public API surfaces
- Native capabilities schema before any
importof iOS modules - Focused module page on pythonide.xin/docs when examples or Chinese scenario text help
Do not invent APIs from SwiftUI, UIKit, React, browser, tkinter, PyQt, Flask, or Streamlit memory.
Runtime Routing
<!-- BEGIN GENERATED: runtime-routing-table -->| Runtime | Import | Skill | Doc |
|---|---|---|---|
| AppUI MiniApp | import appui | pythonide-appui | appui-module |
| Home Screen widget | import widget | pythonide-widget | widget-module |
| 2D game / scene | import scene | pythonide-scene | scene-module |
| Legacy UI script | import ui | pythonide-automation | ui-module |
| Turtle graphics | import turtle | pythonide-scene | turtle-module |
| Plain Python / shortcuts | stdlib + native modules | pythonide-automation / pythonide-native | ios-native |
Companion Skills
| Skill | Load when |
|---|---|
pythonide-appui | Forms, lists, tabs, navigation, dashboards, AppUI media controls |
pythonide-native | Permissions, sensors, photos, location, notifications, networking, keychain, device APIs |
pythonide-widget | WidgetKit home screen widgets |
pythonide-scene | Games, sprites, physics, frame loops, turtle |
pythonide-automation | Shortcuts, keyboard snippets, legacy ui, batch scripts |
Decision Rules
- Default interactive app →
pythonide-appui - Home Screen widget →
pythonide-widget(never AppUI) - Continuous animation / game loop →
pythonide-scene(never AppUI navigation) - Needs iOS capability behind UI →
pythonide-appui+pythonide-native - Only scripts / Shortcut / editor helper →
pythonide-automationorpythonide-native - Pythonista-compatible imperative UI →
pythonide-automation(uiruntime)
AppUI + Native Pairing
When a MiniApp needs camera, photos, location, files, share, notifications, storage, or device state:
- Build the shell with
pythonide-appui - Load
pythonide-nativefor module choice, permissions, and callback-side effects - Prefer AppUI bridge components (
PhotoPicker,CameraPicker,MapView,FileImporter,ShareLink,VideoPlayer) before imperative modules when the UI is inline - Never call native APIs from AppUI
body()
Schema Entry Kinds
Route from native capabilities schema:
| Kind | Meaning | Action |
|---|---|---|
module | import <name> | Read module doc + pythonide-native |
appui_bridge | appui.<Component> | Read pythonide-appui bridge table |
topic | No direct import | Follow topic doc; often AppUI-first |
reference | Docs only | Do not import |
Output Contract
- Deliver runnable Python for PythonIDE unless the user asks for explanation only
- One primary runtime per artifact
- JSON-safe data in
storage/database; secrets only inkeychain - Say when hardware, permission, or preview validation cannot be proven from editor context