From floating-clock
Terminate (quench) the running FloatingClock process. Renamed from 'quit' to avoid clashing with Claude Code's built-in /quit.
How this skill is triggered — by the user, by Claude, or both
Slash command
/floating-clock:quenchThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Terminate any running FloatingClock process.
Terminate any running FloatingClock process.
Self-Evolving Skill: This skill improves through use. If the process pattern stops matching (binary path change) — fix this file immediately, don't defer. Only update for real, reproducible issues.
if pgrep -f "FloatingClock.app/Contents/MacOS/floating-clock" >/dev/null 2>&1; then
pkill -f "FloatingClock.app/Contents/MacOS/floating-clock"
echo "FloatingClock quit."
else
echo "FloatingClock is not running."
fi
After this skill completes, check before closing:
pkill actually terminate the process? — If it lingered, escalate to kill -9 and update the script.pgrep/pkill regex.Only update if the issue is real and reproducible — not speculative.
npx claudepluginhub terrylica/cc-skills --plugin floating-clockGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.