القائمة
Export package from Pharo image to Tonel files. Use when code was changed directly in Pharo (debugger, browser, or code generation) and needs to be synced back to Tonel files.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Run SUnit tests in the running Pharo image. Use when verifying changes after import, or when checking results for a specific test class or package.
Import Tonel package into running Pharo image. Use when loading edited .st files into Pharo after code changes.
Comprehensive Pharo Smalltalk development workflow guide with AI-driven Tonel editing. Provides expertise in Tonel file format syntax (class definitions with name, superclass, instVars, category, method categories, class comment placement), package structure (package.st placement, directory organization, BaselineOf dependencies), development workflow (Edit → Import → Test cycle with absolute paths, re-import timing, test execution), and Pharo best practices (CRC format documentation, method categorization conventions). Use when working with Pharo Smalltalk projects, creating or editing Tonel .st files, organizing packages and dependencies, resolving import order issues, writing class comments, implementing standard Pharo development patterns (Singleton, Settings, etc.), or troubleshooting Tonel syntax.
Systematic debugging guide for Pharo Smalltalk development. Provides expertise in error diagnosis (MessageNotUnderstood, KeyNotFound, SubscriptOutOfBounds, AssertionFailure), incremental code execution with eval tool, intermediate value inspection, error handling patterns (`on:do:` blocks), stack trace analysis, UI debugger window detection (read_screen for hung operations), Transcript logging (crShow:,
Friendly Smalltalk development assistant and skill router. Use when the user asks any Pharo/Smalltalk development question, needs help getting started, asks about the workflow, wants to implement/debug/understand code, needs project setup guidance, or is unsure where to begin.
Smalltalk code evaluator for Pharo via MCP. Use when executing Smalltalk expressions, verifying object state or intermediate values, debugging code incrementally, checking Pharo connection, or running quick experiments.
| name | st-export |
| description | Export package from Pharo image to Tonel files. Use when code was changed directly in Pharo (debugger, browser, or code generation) and needs to be synced back to Tonel files. |
| allowed-tools | mcp__smalltalk-interop__export_package |
Export a package from the running Pharo image back to Tonel files.
/st-export PackageName /absolute/path/to/src
export_package with package name and absolute path to the src/ directoryExport is the exception, not the norm. Use only when Pharo has newer code than Tonel files:
.st files in the directory/st-export MyPackage /home/user/project/src
/st-export MyPackage-Tests /home/user/project/src