Stats
Actions
Tags
From presentfast-visual-questions
Write the Visual Questions protocol marker block into the current project's CLAUDE.md. Creates the file if absent, appends if present, idempotent on re-run. Opt-in — the plugin works without ever running this.
How this skill is triggered — by the user, by Claude, or both
Slash command
/presentfast-visual-questions:visual-initThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run the init script via Bash with the current working directory:
Run the init script via Bash with the current working directory:
node "${CLAUDE_PLUGIN_ROOT}/skills/visual-init/scripts/init.mjs" "$(pwd)"
Report the script's stdout to the user verbatim. The script prints one of:
created CLAUDE.md (N lines) — file didn't exist; created with title + protocol block.appended CLAUDE.md (N lines) — file existed; protocol block appended after existing content.unchanged — Visual Questions block already present — already initialized; no-op.After running, if the file was created or appended, suggest:
git add CLAUDE.md && git commit -m "chore: add Visual Questions protocol to CLAUDE.md"
The plugin's slash commands and PostToolUse hook work entirely from the plugin
install dir (~/.claude/plugins/...). The user's CLAUDE.md is NEVER edited
automatically. Running /visual-init is purely for users who want the protocol
visible in their repo (teammate discoverability, cross-AI portability, or
post-uninstall survival).
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 khush012/presentfast-visual-questions-plugin --plugin presentfast-visual-questions