vscarpenter

Reference for Claude Code's own mechanics — slash commands, skills, subagents, hooks — and how they route together. Use when creating or editing a slash command, skill, subagent, or hook, or when deciding which primitive fits a task.

Verify Sentry error capture is working after a DSN change or deploy. Use when testing Sentry, confirming error reporting works, or debugging why errors aren't showing up in the Sentry dashboard.

Sanity-check the working tree before starting plan execution or new branch work. Catches inherited damage that silently breaks verification later — merge conflict markers committed to tracked files, outstanding stash entries that may bleed into your work, uncommitted changes you may not realize you have. Runs in ~1 second. Trigger BEFORE invoking superpowers:executing-plans or superpowers:subagent-driven-development, BEFORE creating a new feature branch off main, or when verification mysteriously fails on files you did not touch.

Syncs main and deletes the local feature branch after a PR is merged on GitHub. Use when the user says they merged or squash-merged a PR ("I merged PR 411 on GitHub", "merged the PR", "clean up the branch"). Codifies this repo's squash-merge default, where `git branch -d` wrongly reports "not fully merged" and a verified force-delete is required.

Apply the Inkwell design system to an existing page or component without creating a competing styling system. Use for styling retrofits, standalone HTML explainers, docs pages, or Tailwind v4 token alignment.

Authoritative agent-runtime contract for working inside an OpenKnowledge project — a markdown-CRDT knowledge base exposed over MCP. Use whenever reading, listing, searching, or editing any `.md` or `.mdx` file in the project, and before any `mcp__open-knowledge__*` tool call (`exec`, `search`, `write`, `edit`, and the rest). Installed by `ok init`, so its presence means this is an OpenKnowledge project and it governs every markdown file here. Covers the read/write tool surface, grounding and linking rules, folder/template conventions, the live browser preview, and the rule that OK's MCP tools — never native file tools — handle in-scope markdown.

Add or modify a field on the PocketBase tasks collection end-to-end — schema script, task-mapper, Zod schema, Dexie version bump, migration test. Use when the user wants to add/remove/rename a synced task field. Codifies the PocketBase v0.23+ gotchas and recurring step-order mistakes.

Convert an approved technical plan into a sequence of small, reviewable PRs with clear phase boundaries, validation gates, and PR descriptions. Use for multi-step refactors, workflow changes, security-remediation tranches, documentation-plus-code rollouts, or any change that is too risky or noisy for one PR.

Build durable backend AI agents with the Eve framework. Use when creating, editing, or debugging an Eve project — agent instructions, skills, tools, connections, channels, sandboxes, subagents, schedules, or evals.

Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.

Comprehensive code standards and agentic behavior guidelines for AI-assisted development. Use this skill for ALL coding tasks — it governs how Claude approaches implementation, testing, verification, code review, git workflow, and task management. Trigger whenever the user asks Claude to write code, fix bugs, implement features, refactor, review PRs, create specs, plan architecture, or do any software development work. Also trigger when the user mentions "coding standards", "code quality", "best practices", "Definition of Done", "code review", or asks Claude to follow team conventions. This skill should be the baseline for every coding session — if code is being written, this skill applies.

Opinionated coding standards and agentic workflow guidance for AI-assisted development. Enforces clean, maintainable, human-readable code with strong guardrails for autonomous multi-step coding sessions. Use this skill when writing, reviewing, or refactoring code in any language or framework. Triggers on: (1) Any code generation or implementation task, (2) Code review or quality checks, (3) Multi-step agentic coding sessions, (4) Requests that include "qcheck" or "qcode" shortcuts, (5) Refactoring or cleanup tasks. This skill applies to all programming languages and frameworks. It emphasizes simplicity over cleverness, incremental delivery, standard libraries over dependencies, and boring maintainability over novelty.