Stats
Actions
Tags
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.
Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub tyroneross/rosslabs-ai-toolkit --plugin showcase