Smalltalk Developer
Guides Pharo Smalltalk development using a file-based, test-driven workflow with Tonel files.
The source repository doesn't declare a license. Check its terms before reusing the code.
Key features
- Includes patterns for creating classes, adding methods, and debugging test failures.
- Enforces a file-first philosophy where Tonel files are the single source of truth.
- Provides best practices for managing absolute paths and package dependencies.
- Automates suggestions for import and test commands after code edits.
- Implements the standard "Edit → Import → Test" development cycle for Pharo.
Use cases
- Building or extending Pharo Smalltalk applications from an external editor.
- Adding new classes and methods to a Smalltalk project using the Tonel file format.
- Running SUnit tests and debugging failures within a Smalltalk package.
FAQ
How does this skill improve my workflow?
It enforces best practices like using absolute paths and managing dependencies correctly. By automating suggestions for import and test commands after code edits, it reduces manual errors and speeds up the development cycle.
What does the Smalltalk Developer skill do?
This skill guides Claude to perform Pharo Smalltalk development using a strict, file-based workflow. It automates the 'Edit → Import → Test' cycle with Tonel files as the single source of truth, ensuring consistent and testable code.
When should I use this skill?
Use this skill for any Pharo Smalltalk task, especially when creating or modifying classes and methods, running SUnit tests, and managing package dependencies. It's ideal for projects that require a disciplined, test-driven approach.
What is the 'file-first philosophy' this skill enforces?
This philosophy dictates that all code changes must be made directly in the Tonel (.st) files, not within the Pharo image. The files are the 'single source of truth,' which improves version control, collaboration, and code consistency.