Claude Skills by scannedinc

Drive a running Xojo IDE from the command line with the bundled xojoctl tool: open, analyze, build, run, and stop projects, save, close, and reload them, list build targets, and send IDE Scripts, with JSON output for automation. Use when the user asks to build, analyze, or run a Xojo project, to drive or automate the Xojo IDE, or to run Xojo IDE scripts. Also use after editing Xojo project files on disk while the IDE is open, so the IDE reloads them instead of running stale code.

Validate, lint, and conservatively format the files of a Xojo project in text format (.xojo_project, .xojo_code, .xojo_window, and the other .xojo_* extensions). Use after creating or editing any Xojo project file, when the user asks to lint, check, validate, format, or clean up a Xojo project, and when the user wants a pre-commit check for a Xojo project.

Migrate a Xojo desktop project from API 1.0 (which Xojo's own documentation calls "pre-API 2.0") to API 2.0: a rule-driven, confidence-tiered conversion of the source code, committed one category at a time, that fixes the index bases, sentinels and epoch shift a rename alone leaves wrong. Replaces deprecated APIs such as MsgBox, Dim, RecordSet, SQLSelect, Date, InStr, Mid, Len, Ubound, ListBox members, GetFolderItem and error-code checks. Covers more than a thousand deprecated and removed sym...

Look up the Xojo language and framework in a local copy of the official documentation. Use whenever writing, reviewing, explaining or debugging Xojo code, and before using any Xojo class, property, method, event or constant, to confirm it exists, get its exact signature, and check whether it is deprecated. Also use for questions about what a Xojo API does, what replaced a removed one, which controls exist for Desktop, Web, Mobile or Console, or how a Xojo feature works. This is also the skill...