From smalltalk-dev
Initializes Pharo Smalltalk dev sessions: checks project structure, loads smalltalk-developer skill, verifies Pharo connection via eval tool, sets up Docker or local install if needed.
How this skill is triggered — by the user, by Claude, or both
Slash command
/smalltalk-dev:st-initThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Start a Pharo Smalltalk development session: verify project structure, confirm Pharo connection, and orient to the development workflow.
Start a Pharo Smalltalk development session: verify project structure, confirm Pharo connection, and orient to the development workflow.
if [ ! -f ".project" ] && [ ! -d "src" ]; then
echo "No Pharo project structure detected"
fi
.project OR src/ found → continuesmalltalk-dev:st-setup-project skillIf no project exists, offer to create one:
⚠️ No Pharo project structure detected in current directory.
Use /st-setup-project MyProjectName to set up:
• .project configuration file
• src/ directory with package structure
• BaselineOf class and Core/Tests packages
Would you like to run /st-setup-project now?
smalltalk-dev:st-setup-project skill, then continue with steps 2–4.Use the Skill tool to load smalltalk-dev:smalltalk-developer. This activates the full development workflow guidance.
Run Smalltalk version via eval:
mcp__smalltalk-interop__eval: 'Smalltalk version'
Report status to user:
✅ Pharo connected: Pharo X.Y (...)
✅ smalltalk-developer skill loaded
📋 Development workflow: Edit → Lint → Import → Test
If Pharo is not connected, check Docker availability first:
docker --version
Generate compose.yml in the project root:
services:
sis-pharo:
image: mumez/smalltalk-interop-docker
ports:
- "5900:5900"
- "6901:6901"
- "8086:8086"
environment:
PHARO_SIS_PORT: 8086
volumes:
- /tmp:/root/screenshots
- .:/root/repos
Then instruct the user:
docker compose up -d
Re-verify connection after startup.
If Docker is not available or not preferred:
1. Install Pharo:
mkdir pharo-stable
cd pharo-stable
curl https://get.pharo.org | bash
2. Load PharoSmalltalkInteropServer:
./pharo Pharo.image metacello install github://mumez/PharoSmalltalkInteropServer:main/src BaselineOfPharoSmalltalkInteropServer
3. Start Pharo (SisServer starts automatically):
./pharo-ui
Re-verify connection after Pharo is running.
If Pharo is installed but server not running, ask user to execute in Pharo:
SisServer current start
The core cycle (full details in smalltalk-dev:smalltalk-developer):
Edit .st file
↓
Lint (/st-lint)
↓
Import package (absolute path)
↓
Run tests
↓
Pass? → Done | Fail? → Debug → Fix → Repeat
| Command | Purpose |
|---|---|
/st-import PackageName /abs/path | Import Tonel package to Pharo |
/st-test TestClass | Run SUnit tests |
/st-eval code | Execute Smalltalk snippet |
/st-export PackageName | Export package from Pharo |
/st-lint src/PackageName | Validate Smalltalk best practices |
| Problem | Solution |
|---|---|
| Connection timeout | Check if Pharo image is running |
| Server not started | Run SisServer current start in Pharo |
| Port mismatch | Check PHARO_SIS_PORT env var (default: 8086) |
| MCP issues | Verify pharo-smalltalk-interop-mcp-server is installed |
| Docker path issues | Check volume mounts in compose.yml |
smalltalk-dev:st-setup-project — Create project structure if missingsmalltalk-dev:smalltalk-developer — Full development workflowsmalltalk-dev:smalltalk-debugger — Debug test failures and errorsnpx claudepluginhub mumez/smalltalk-dev-plugin --plugin smalltalk-devRoutes Pharo Smalltalk development queries to specialized skills for coding, debugging, code understanding, project setup, and workflow guidance.
Defines standardized development environments or onboards developers by generating setup scripts, container configs, CI workflows, toolchain pins, and dev-setup documents.
Provides Shipyard overview and slash commands for Claude Code projects: init, brainstorm, plan phases, build with reviews/audits, quick tasks, ship, and skill access.