Menu
Use when releasing library changes or deploying services across the lamina workspace. Extends /deploy with lamina-specific tools.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Use when iterating on Bubble Tea TUI code. Every change gets a direct model test before committing — send messages, assert state and View().
Use before claiming any fix, release, or implementation is complete in the lamina workspace. Extends /verify with lamina-specific evidence commands.
Use when a build fails, tests break across repos, or dependencies are out of sync. Extends /debug with lamina-specific tools.
Use when grounding in the lamina workspace. Extends /ground with lamina-specific tools.
Based on SOC occupation classification
| name | deploy-lamina |
| description | Use when releasing library changes or deploying services across the lamina workspace. Extends /deploy with lamina-specific tools. |
Follow /deploy — here's how each step works in the lamina workspace.
lamina release <module> <version> # Tag and push a module
lamina release --dry-run <module> v0.2.0 # Preview first
lamina release --all # Release in dependency order
lamina release checks for dirty state, existing tags, and warns if dependencies have unpublished changes.
lamina doctor # Check workspace health before releasing
lamina test # Run full test suite across all modules
lamina repo # Verify all repos are clean
After a library release, services that depend on it need redeployment. Use /deploy-aurelia for the service deployment itself. The lamina layer handles:
lamina doctor — confirm dependencies are consistentlamina test — full suite passeslamina release — tag the library/deploy-aurelia for each affected serviceThen /verify.
$ARGUMENTS