Expert guidance for clue workspace coordination. Use when working in a directory with .clue/, when multiple Claude sessions need coordination, or when managing repositories in a shared workspace.
/plugin marketplace add getnexar/clue/plugin install getnexar-clue@getnexar/clueThis skill inherits all available tools. When active, it can use any tool Claude has access to.
You are working in a clue workspace - a coordinated environment for multi-agent development.
| Need | Command |
|---|---|
| See workspace state | clue status |
| Track a thought/TODO | clue note "text" |
| Set session goal | clue set-session-goal "text" |
| Manage repositories | /clue-repo skill |
| Full workspace details | clue status --full |
When working in a clue workspace:
Before modifying code:
clue status to check for other active sessions/clue-repo work <url> <branch> to get an isolated worktreeWhen repos seem stale or missing:
clue repo scan to refresh repo trackingclue repo list to see tracked reposTo coordinate with other sessions:
clue note "working on X"Always prefer worktrees for code changes to avoid conflicts with other sessions
clue status # What's happening in this workspace?
clue repo scan # Refresh repo tracking
clue repo list # What repos are tracked?
/clue-repo work ... # Get isolated worktree for changes
clue help # All available commands
This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.