mzvonar
- 19 skills
- 0 followers
- 5 hours ago last updated
- ▌ Codebase Map · mzvonar bundleGenerate an interactive, zoomable map of any codebase — a high-level service/module call graph that drills into each module's endpoints and code structure. Project-agnostic. Scripts do all scanning and HTML generation; the LLM only adds semantic labels (roles, edge meanings). Use when the user asks to "map", "visualize", "diagram", "explore", or "understand the architecture of" a repo or multi-repo workspace, or to "refresh" an existing map after code changes.
- ▌ Update Skill · mzvonarChange a skill that was installed from the claude-skills-public marketplace (any `/dev-tools:*`, `/workflow:*`, `/next-js:*`, `/prisma:*`, `/describe-changes:*`, `/refdiff:*`, `/svc:*` skill) the right way — upstream in a sibling checkout, validated, version-bumped, then rolled out with a plugin update. Use whenever the user asks to update, fix, improve, extend, or reword one of these skills, says a skill "is wrong" or "should also…", or you are about to edit a file under ~/.claude/plugins/cache/ or copy a plugin skill into .claude/skills/. Never edit the cached copy and never vendor it into the repo.
- ▌
- ▌ Update Guidelines · mzvonar bundleUpdates the repo's canonical guideline docs (CLAUDE.md, AGENTS.md, architecture docs) and propagates the change to every project agent and skill that generates code. Use when the user says "update the guidelines", "update CLAUDE.md / AGENTS.md", "update the architecture", "incorporate this research"; when a convention changes systematically (naming, layering, validation, dependency, test or commit rules); when a lesson promoted by /workflow:lessons needs a guideline gist plus a skill body; or when the user asks to make CLAUDE.md leaner / slimmer / shorter, do "CLAUDE.md hygiene", or trim / de-bloat it (then the hygiene runbook is the whole job). Invoke proactively on any systematic change to how code should be written. Always runs every phase (read, update docs, hygiene, analyse managed files, apply) and never stops after one doc: a stale assertion is worse than a missing one. CLAUDE.md stays an index of one-line gists under 400 lines / 40,000 chars; rule bodies live in the repo's project skills.
- ▌
- ▌
- ▌ Clear Context Handoff · mzvonarPrepare a clean-context handoff. Use when the user asks to "hand off", "prepare a clear-context handoff", "write a handoff", or otherwise wants to /clear and continue in a fresh session. Produces a committed handoff doc (what we're doing, what's done, ordered next steps, research/open questions) plus a kickoff prompt to paste into the fresh context.
- ▌ Describe Changes · mzvonar bundlePresent an implemented change to a human reviewer the way a human needs it: what was done and why, a visual map of the high-level change (who calls whom, where data flows, what moved/split/renamed), and a ranked, tiny list of the spots that genuinely need human eyes (critical / medium / low) — with renames, moves, formatting, lockfiles and import rewrites folded away. Renders in chat AND as a mobile-first interactive HTML report, then answers follow-up questions and collects feedback so the skill sharpens over time. Use proactively right after implementing a story/task/feature, before opening a PR, and whenever the user says "describe the changes", "walk me through what you changed", "what should I review", "explain this diff/PR/branch", "show me the implementation", or "/describe-changes" (installed as `/describe-changes:describe-changes`).
- ▌ Diff · mzvonar bundleShow a rich visual diff of git changes. Generates an HTML side-by-side diff (like JetBrains) served over HTTP with the LAN URL printed (plus a Tailscale URL if Tailscale is installed). Falls back to formatted markdown if diff2html-cli is unavailable. Use when the user asks to "show the diff", "visual diff", "review my changes", or wants to see a diff on another device.
- ▌ Ngrok · mzvonarExpose a local port (or a specific URL on a local server) via ngrok so the user can open it from another device or share it externally. Use whenever the user wants to share something running on localhost — phrases like "expose my dev server", "make this accessible on my phone", "share this via ngrok", "tunnel port X", "ngrok this", or after generating any local artifact (HTML report, dashboard, file viewer, diff page) that they want to view from a different machine. Also trigger if the user complains they can't reach a localhost URL from another device. The skill prints a copy-pasteable bare URL (no angle brackets), tracks the ngrok PID for clean teardown, and offers to open the URL in the default browser.
- ▌ Test Audit · mzvonarAudit a test suite for duration and quality in parallel subagent batches, bucket the findings with low-hanging fruit first, measure a machine-local baseline so deltas are attributable, then implement bucket-by-bucket via subagents — each bucket benchmarked and recorded in a markdown table. Use when asked to "audit the tests", "speed up the e2e/test suite", "find duplicate or broken tests", "why is CI slow", "run a test audit", or to continue a previous audit's next bucket. Self-configures on first run in a repo: discovers the sanctioned full-suite command, flake ledger and repo constraints, confirms them with the user, and writes .claude/claude-skills.json. Produces docs/test-audit-<date>.md plus one docs/test-benchmark-bucket<N>.md per implemented bucket.
- ▌ Backlog · mzvonar bundleKeep a checked-in markdown backlog readable as it grows, and groom it against the work being scoped. Splits a monolithic list into an index plus one detail file per item (frontmatter holds the fields that decide what to work on), reads it through one script instead of a 3000-line file, and classifies every open item into promote-now / promote-separately / keep-deferred / kill with a paste-ready report. Use when picking what to do next, when the user says "groom the backlog", "check deferred work", "what should we pull in", "any debt to fold in", "review pending items", before a new story/task/epic is scoped or finalized, when a review defers a finding, when adopting the format in a new repo, or when the list has grown past the point of being read in full. Never fires mid-implementation or for one-line fixes.
- ▌
- ▌ Clean Dev · mzvonarKill the Next.js dev server on the project's dev port and start a fresh one with `.next` (plus any configured extra caches) cleared. Detects the port (svc → `PORT` in `.env.local` / `.env` → `-p`/`--port` in the dev script → explicit argument → 3000) and the package manager, and uses the repo's own kill / clean scripts when they exist. Use whenever the user wants a clean dev-server restart — "clean dev", "restart the dev server", "kill and restart next", "blow away .next and restart", "fresh dev server", `/next-js:clean-dev [port]` — after regenerating a Prisma client, or when a newly added route hangs compiling forever.
- ▌ Showcase · mzvonar bundleRecord and view a human-paced video + captioned screenshot walkthrough of a working feature, layered on the repo's existing Playwright e2e harness (same auth, page objects and seed helpers). Produces a self-contained `docs/showcases/<feature>/index.html` with the video and a captioned screenshot grid, verified frame by frame for error overlays and silent console errors, and served on the LAN for reviewers. Use when the user says "record a showcase for <feature>", "make me a feature showcase video", "show me <feature> working end to end", "generate the showcase page", "prove the feature works", or invokes `/workflow:showcase`. Bootstraps the vendored harness into the e2e package on first use. Optional tutorial mode turns retained specs into subtitled help videos. Never a regression suite, never in CI.
- ▌ Worktree · mzvonarCreate a new git worktree on a new branch (off the repo's default branch unless another base is stated) and switch to working inside it for the rest of the session. Use this skill whenever the user asks to "create a worktree", "new worktree", "spin up a worktree", "work from a fresh worktree/branch", "branch off main/master and work from it", or otherwise wants isolated work that must not touch the root checkout. Also covers what a fresh worktree is missing before tests, dev servers, or docker-compose stacks will run from it.
- ▌ Check Acs · mzvonar bundleAudit an implementation against its acceptance criteria, one criterion at a time, to find AC-misimplementations that code review misses. Use whenever the user wants to check, verify, or audit acceptance criteria — "does this actually satisfy the ACs", "check the ACs for this story", "did we really implement AC4", "audit this story before merge", "the review passed but I want a second opinion", or when reviewing a PR/MR against a spec or ticket. Also use when a story was marked done and the user suspects something slipped, or when they want to know which criteria a change fails. Combines a repeated fresh-context judge sweep with a deterministic existence check for criteria that name concrete artifacts.
- ▌ HTML Report · mzvonar bundleGenerates a polished dark-themed HTML code review report and opens it in the browser. Use this whenever producing or presenting a code review, security review, PR review, or any structured finding report — especially after /review, /security-review, or ultrareview, or when the user asks to "show results as HTML", "generate a report", or "present me the result". The report renders collapsible finding cards grouped by severity (Critical / Important / Suggestion), numbered reference codes (C1, C2, I1…) the user can cite back in conversation, copyable full-path file locations with line numbers for IDE navigation, and before/after code diffs.
- ▌ Prisma Migrate · mzvonar bundleRun Prisma migrations and regenerate the Prisma client safely — preflight (env file, schema location, package manager), `migrate dev` / `migrate deploy` / `generate`, and the recovery procedures for the ways `migrate dev` refuses to run (drift, edited-after-apply checksum drift, shared dev DBs, raw-SQL objects Prisma cannot model, Prisma 7's agent reset guard). Use whenever the user asks to run or create a migration, apply schema changes, regenerate the Prisma client, "update the DB", "apply the schema", "run db:migrate", or when `prisma migrate dev` complains about drift, demands a reset, hangs on a prompt, or a new enum value / model is "undefined" at runtime after a migration.