πŸ”Œ

vision-powers

πŸ”ŒPlugin

LeeJuOh/claude-code-zero

Installation

Add marketplace in Claude Code:
$/plugin marketplace add LeeJuOh/claude-code-zero
Step 2. Install plugin:
$/plugin install vision-powers@claude-code-zero
VibeIndex|
What it does
|

Analyze Claude Code plugins and visualize development artifacts as interactive HTML or diagram-enhanced markdown reports. On a capable account, HTML reports publish as claude.ai Artifacts by default (doc-visual, diff-visual, plugin-visual, context-health-visual); add --local for a local design-system + Mermaid file. Six skills: plugin-visual (local/installed/GitHub plugin audits with security + architecture), diff-visual (git diffs, with side-by-side split-diff of the actual changed code and File Map change-flags), doc-visual (markdown docs with Mermaid diagrams), fact-check (claim verification against code + git history, republishing corrections to the same Artifact link), context-health-visual (environment health with skill-security scan and hook schema validation), report-manager (list/open/delete/search/refine, surfacing stored Artifact URLs and republishing to the same link). Every report supports --format md, --lang, and in-browser per-section feedback.

πŸͺ

Part of

leejuoh-claude-code-zero

0
-
AddedAug 9, 2026

More from this repository10

πŸͺ
leejuoh-claude-code-zeroπŸͺMarketplace

Complete Claude Code plugin marketplace β€” agents, skills, hooks, commands, rules, MCPs.

πŸ”Œ
worktree-plusπŸ”ŒPlugin

Replaces Claude Code's built-in worktree β€” aligns with native git worktree where CC diverges (HEAD base, origin/* auto-tracking) and adds layers native lacks: .worktreeinclude/.worktreelink for gitignored files with a /worktree-setup skill that scans and builds them, upstream-aware removal guard, idempotent re-entry.

πŸ”Œ
vibeproxy-kitπŸ”ŒPlugin

State-aware VibeProxy alias manager for Claude Code. Discover VibeProxy state, choose backend-specific cc-* aliases, and rewrite only managed config and shell blocks without clobbering manual edits.

πŸ”Œ
claw-moπŸ”ŒPlugin

Manage mo markdown viewer sessions: autosync new Claude-written .md via PostToolUse hook, group-based organization, restart-on-up for fsnotify-miss recovery, file deep-linking, stdin pipe support, cmux browser integration, per-project watch patterns, port isolation

πŸ”Œ
skill-creator-proπŸ”ŒPlugin

Create, test, and iteratively improve Claude Code skills with the official lean coaching loop, an eval harness for benchmarking with variance analysis, and automated description-trigger optimization

πŸ”Œ
notebooklm-connectorπŸ”ŒPlugin

A plugin to manage NotebookLM notebooks and query them using integrated features.

πŸ”Œ
claw-muxπŸ”ŒPlugin

cmux terminal integration: terminal I/O, topology control, browser automation, markdown viewer, notifications

πŸ”Œ
codex-advisorπŸ”ŒPlugin

Get Codex's second opinion β€” and actually trust it: a different model reviews your code, plans, and research, and Claude fact-checks every finding (Agreed/Disputed/Nuanced/False Positive/Uncited) before you act, catching hallucinated citations. Skills: setup, review, adversarial, rescue, verify, research, status, result, cancel, transfer. Task delegation (rescue) wraps your verbatim request in adaptive, preview-approved prompt blocks. Transfer hands the whole session off to a resumable Codex thread (v1.0.5+). Prompt-running skills accept --model/--effort via config.toml.

πŸ”Œ
e2e-test-runnerπŸ”ŒPlugin

Run E2E browser tests using natural language test definitions powered by Claude Code SDK and agent-browser with video recording

πŸ”Œ
rubber-duck-tutorπŸ”ŒPlugin

Rubber duck tutor that keeps you engaged across the whole AI-coding lifecycle β€” before you ask AI to build (/duck-prebuild), once code is written and before you ship (/duck-verify, /duck-review), and when orienting to unfamiliar code (/duck-orient), plus /duck for auto-detect. /coach is its teaching sibling, manual-invocation only: /coach <topic> explains and drills a concept, /coach <file> or a bare /coach right after generating code dissects it section by section (what/why-this-way/where-it-breaks), and /coach alone surfaces an unresolved gap from a past duck session and teaches it β€” resolved only once you pass the exercise, not by saying you understand. Ship-point hooks triage what you just pushed against six risk categories and target the riskiest change you didn't actually discuss, fall back to retrieving an unresolved gap from a past session, or demote to a non-blocking scoreboard after three ignored confrontations in a row. Confrontation telemetry (fired/answered/ignored) is queryable from /duck-orient. Doesn't overlap /code-review or /grilling β€” duck only checks whether you understand, never whether the code or plan is good, and never teaches β€” that's coach's job.