PythonIDE Router

June 10, 2026 · View on GitHub

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 import of 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	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

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

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-automation or pythonide-native
Pythonista-compatible imperative UI → pythonide-automation (ui runtime)

When a MiniApp needs camera, photos, location, files, share, notifications, storage, or device state:

Build the shell with pythonide-appui
Load pythonide-native for 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()

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

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 in keychain
Say when hardware, permission, or preview validation cannot be proven from editor context