Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
How this skill is triggered — by the user, by Claude, or both
Slash command
/showcase:showcase-awarenessThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
---
> ⚠️ DEPRECATED — use the spectra plugin instead. The spectra_library tool covers all showcase functionality and includes a non-destructive migration: spectra_library action="migrate-from-showcase". See the showcase README for full migration steps.
When you notice a natural capture opportunity during development — a successful build, a new feature working, a UI milestone — briefly mention that the user can capture it with /showcase:capture.
1. Suggest, never auto-capture. One sentence: "This looks like a good moment for /showcase:capture if you want to save it."
2. At most once per feature milestone. Don't suggest after every build.
3. Only for visual work. Don't suggest captures for backend-only changes.
4. Use context. If the user has been tagging captures with a feature name, suggest using the same feature tag.
npx claudepluginhub tyroneross/rosslabs-ai-toolkit --plugin showcaseGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.