smalltalk-developer

Automate your Pharo Smalltalk workflow by editing Tonel files, importing packages in correct dependency order via BaselineOf, and running SUnit tests. This Skill enforces the Edit → Import → Test cycle with absolute paths and syntax validation, eliminating manual repetition and common errors like incorrect import timing.

Yes. This Skill consults your BaselineOf project to automatically resolve and suggest correct package import order, then applies changes and runs tests. It handles multi-package development and TDD sessions while validating Tonel syntax to prevent dependency conflicts.

Create classes and add methods by editing Tonel files, then let this Skill import packages with resolved dependencies and automatically run relevant SUnit tests. This streamlines feature development and catches errors immediately after each code change.

Yes. This Skill is designed for TDD sessions in Tonel-Pharo projects, automating the cycle of writing tests, editing implementation files, importing packages, and validating results—reducing friction between test definition and implementation.

You need a Pharo project structured with Tonel files, a BaselineOf class defining dependencies, and SUnit tests. This Skill requires absolute file paths and validates Tonel syntax before import, so proper project baseline configuration is essential.

Avoid this approach if your Pharo project lacks a BaselineOf definition, uses non-standard Tonel structures, or requires manual dependency resolution. This Skill enforces strict Edit → Import → Test practices; projects needing flexible or ad-hoc import sequences may require manual steps.