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)
From heimdall
List Heimdall lock blocks. Use when the user says "list locks", "show protected files", "what's protected", "what is heimdall guarding", "show heimdall config", "list protection", or asks to inspect or audit what's locked. Displays each store, its lock blocks, unlock phrases, and the resolved file/dir targets.
How this skill is triggered — by the user, by Claude, or both
Slash command
/heimdall:listThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Show every active Heimdall store and its lock blocks (unlock phrase + protected paths, with each path resolved to a file or directory against the repo root).
Show every active Heimdall store and its lock blocks (unlock phrase + protected paths, with each path resolved to a file or directory against the repo root).
node "${CLAUDE_PLUGIN_ROOT}/scripts/heimdall-list.js"
--json.If no stores exist, tell the user to run /heimdall:install.
npx claudepluginhub thomfilg/ai-plugin-work --plugin heimdallGuides 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.
Implements work from a spec or tickets using TDD at agreed seams, with regular typechecking and test runs, followed by code review.