Claude Skills by partme-ai

Set default Node versions via nvm aliases, create .nvmrc files for project-specific versions, and configure shell auto-switching per directory. Use when the user asks about nvm alias default, .nvmrc configuration, auto-switching Node versions on directory change, or pinning a Node version for a project.

Install and configure nvm in Docker containers and CI/CD pipelines, including non-interactive shell loading via BASH_ENV or ENTRYPOINT. Use when the user asks about nvm in Docker, CI/CD nvm setup, GitHub Actions node version management, or troubleshooting nvm in non-interactive shells.

Migrate npm global packages between Node versions using reinstall-packages-from, and define a default-packages file to auto-install globals on every new version. Use when the user asks about keeping global packages after switching Node versions, setting up default npm packages, or troubleshooting missing global packages after nvm install.

Install and update nvm (Node Version Manager) using curl/wget scripts, git clone, or manual methods. Covers profile selection, NVM_DIR configuration, and Alpine Linux support. Use when the user asks to install nvm, update nvm, set up nvm for the first time, or troubleshoot nvm installation scripts.

Configure custom Node.js binary mirrors and authentication headers for corporate or restricted network environments. Use when the user asks about NVM_NODEJS_ORG_MIRROR, setting a custom node download mirror, configuring auth headers for private mirrors, or installing Node behind a firewall or corporate proxy.

Provide nvm overview, output color customization, tests, and automation examples like Ansible. Use when users ask for an nvm intro, color settings, running nvm tests, or Ansible install tasks.

Provide nvm project metadata like maintainers, support policy, enterprise support, license, and copyright notice. Use when users ask about project governance or legal notices.

Configure shell initialization files so nvm loads correctly in bash, zsh, and fish. Covers NVM_DIR, nvm.sh sourcing, profile file selection, XDG_CONFIG_HOME, and bash completion. Use when the user reports nvm not found after installation, needs to configure shell profiles, or wants to set up nvm environment variables.

Configure automatic nvm version switching when changing directories, using shell hooks for bash, zsh, and fish. Covers auto-use on cd, PATH restoration, and nvm deactivate. Use when the user wants automatic Node version switching per project, nvm use to run on directory change, or needs to deactivate nvm and restore system PATH.

Diagnose and fix nvm issues on Linux and WSL, including profile not loading, PATH errors, distro-specific differences, and Alpine compatibility problems. Use when the user reports nvm not found on Linux, nvm command not working in WSL, or distro-specific nvm issues.

Diagnose and fix nvm issues on macOS, including zsh/bash profile not loading, PATH priority conflicts, permission errors, and Homebrew Node conflicts. Use when the user reports nvm not found on macOS, nvm command not working in zsh or Terminal, or PATH priority issues after macOS updates.

Remove nvm completely by deleting NVM_DIR, cleaning nvm lines from shell profiles, and restoring system Node PATH priority. Use when the user asks to uninstall nvm, remove node version manager, clean up nvm installation, or restore their system to use the system-installed Node.

Manage Node.js versions with everyday nvm commands: install specific versions, switch active versions, list installed and remote versions, and use LTS releases. Use when the user asks about nvm install, nvm use, nvm ls, listing available Node versions, or switching between Node versions.

Verify nvm installation is working correctly by checking nvm, node, and npm commands, diagnosing PATH order, and inspecting profile loading. Use when the user reports nvm command not found, wants to verify nvm is installed, or needs to diagnose why nvm is not loading in new terminal sessions.

Install, configure, and use nvm (Node Version Manager) to manage Node.js versions. Routes to focused sub-skills for installation, shell setup, version switching, .nvmrc defaults, global packages, Docker/CI, troubleshooting, and more. Use when the user needs to manage Node.js versions, install nvm, or troubleshoot nvm usage.

OCRmyPDF Python API and plugin skill — use OCRmyPDF programmatically from Python, integrate with applications, and extend with plugins (EasyOCR, PaddleOCR, AppleOCR). Use when the user needs to call OCRmyPDF from Python code, build OCR pipelines, or use alternative OCR engines.

OCRmyPDF batch processing skill — process multiple PDFs, Docker automation, shell scripting, and CI/CD integration. Use when the user needs to OCR many PDFs, set up automated OCR pipelines, or integrate OCR into workflows.

OCRmyPDF image processing skill — deskew, rotate, clean, despeckle, remove border from scanned documents. Use when the user needs to improve scanned PDF quality, fix skewed pages, remove noise, or clean up scanned documents before OCR.

OCRmyPDF optimization skill — compress PDFs, configure PDF/A output, JBIG2 encoding, and lossless optimization. Use when the user needs to reduce PDF file size, create archival PDF/A files, or optimize OCR output.

OCRmyPDF core skill — add searchable OCR text layer to scanned PDFs, convert images to searchable PDFs, support 100+ languages via Tesseract. Use when the user needs to OCR a PDF, make a scanned PDF searchable, or extract text from scanned documents.

Implement tasks from the change using `/opsx:apply`, working through the task list and checking off items. Use when the user says "implement", "apply the change", "/opsx:apply", or "start coding from tasks".

Archive a completed change with `/opsx:archive`, merging delta specs into main specs and preserving the change for history. Use when the user says "archive the change", "finish up", "/opsx:archive", or "mark this change as done".

Archive multiple completed changes at once with `/opsx:bulk-archive`, handling spec conflicts between changes. Use when the user says "archive all changes", "bulk archive", "/opsx:bulk-archive", or has multiple completed changes.

Configure OpenSpec project settings and global CLI configuration using `openspec/config.yaml` and `openspec config` commands. Use when the user says "configure OpenSpec", "project config", "add project context", or wants to set per-artifact rules.

Create the next artifact in the dependency chain with `/opsx:continue`, building up a change incrementally. Use when the user says "continue the change", "create next artifact", "/opsx:continue", or wants step-by-step artifact creation.

Think through ideas, investigate problems, and clarify requirements before committing to a change using `/opsx:explore`. Use when the user says "explore an idea", "think through this", "investigate options", or wants to brainstorm before creating a formal change.

Fast-forward through artifact creation with `/opsx:ff`, generating all planning artifacts (proposal, specs, design, tasks) at once. Use when the user says "fast forward", "create all artifacts", "/opsx:ff", or has a clear picture of what to build.

Run `openspec init` to initialize OpenSpec in a project directory, creating the openspec/ folder structure and configuring AI tool integrations. Use when the user says "initialize OpenSpec", "openspec init", or "set up OpenSpec in this project".

Install the OpenSpec CLI globally via npm, pnpm, yarn, bun, or nix. Use when the user says "install OpenSpec", "set up OpenSpec", or "openspec command not found".

Start a new OpenSpec change with `/opsx:new`, creating a change folder with metadata and scaffolding. Use when the user says "start a new change", "new feature", "/opsx:new", or "create an OpenSpec change".

Guided onboarding through the complete OpenSpec workflow using `/opsx:onboard`, walking the user through a real change in their codebase. Use when the user says "onboard me", "tutorial", "/opsx:onboard", "how does OpenSpec work", or is new to OpenSpec.

Create and manage custom workflow schemas using `openspec schema init/fork/validate/which`. Use when the user says "create a custom workflow", "custom schema", "fork a schema", or wants to define their own artifact types and dependencies.

Sync delta specs from a change into main specs using `/opsx:sync`, without archiving the change. Use when the user says "sync specs", "merge specs to main", "/opsx:sync", or needs to update main specs mid-change.

Run `openspec update` to regenerate AI tool instruction files after upgrading the OpenSpec CLI. Use when the user says "update OpenSpec", "openspec update", or "refresh OpenSpec skills/commands".

Validate that implementation matches change artifacts using `/opsx:verify`, checking completeness, correctness, and coherence. Use when the user says "verify implementation", "check my work", "/opsx:verify", or wants quality validation before archiving.

When you need to turn Stitch page HTML (or a Stitch URL) into a Pencil .pen design. Parses DOM and Tailwind, applies HTML→Pencil mapping and execution order, outputs sequential batch_design for layout and style fidelity (background, color, size, margin, padding, shadow). Supports multi-framework tokens.

Batch execute insert, update, replace, move, and delete operations on Pencil .pen design nodes via the batch_design MCP tool. Use when the user explicitly mentions Pencil and needs to draw, insert, change, remove, or move elements on the canvas.

Batch search and read node information. The Agent's 'Eyes'. Use to find specific components e.g. all nodes named 'Button' or get child structure within a container.

Smartly find empty canvas space. Use to automatically plan artboard placement to avoid overlap and keep the canvas organized.

Get current design environment context. Use when you need to understand what is currently selected, canvas position, and environment state before any task.

Get design system guidelines. Use to read and understand specifications e.g. Material Design iOS HIG or custom specs before designing.

Capture a visual screenshot of a specific node in a Pencil .pen file via the get_screenshot MCP tool. Use when the user explicitly mentions Pencil and needs to visually verify a design operation, check for alignment or spacing issues, or review a component after batch_design changes.

Explore design style tags. Use to get design inspiration, such as 'Modern', 'Dark Mode', 'SaaS' directions.

Retrieve detailed style guide metadata (color palettes, typography rules, visual specs) by tags or ID from Pencil via the get_style_guide MCP tool. Use when the user explicitly mentions Pencil and needs to apply a specific visual style, retrieve theme colors and fonts, or look up a style guide by keyword tags.

Read design token variables (colors, fonts, spacing) from a Pencil .pen file via the get_variables MCP tool. Use when the user explicitly mentions Pencil and needs to list design tokens, check the current theme, or retrieve variable IDs for use in batch_design operations.

Open or create a design document. Use when you need to initialize design tasks, create new files, or switch to specific designs.

Batch replace matching style properties (colors, fonts, sizes) across nodes in a Pencil .pen file via the replace_all_matching_properties MCP tool. Use when the user explicitly mentions Pencil and needs to globally swap colors, update font families, migrate to a new brand style, or batch-adjust spacing across frames.

Search and list all unique values for specific properties (fills, fonts, spacing) across nodes in a Pencil .pen file via the search_all_unique_properties MCP tool. Use when the user explicitly mentions Pencil and needs to audit design consistency, find all colors or font sizes used, or identify inconsistent styles.

Set or update design variables. Use to establish or maintain a Design Token system.

Capture a structural snapshot of the node tree in a Pencil .pen file via the snapshot_layout MCP tool, optionally filtering to only show layout problems. Use when the user explicitly mentions Pencil and needs to analyze page hierarchy, check for clipped or overlapping elements, or prepare for layout adjustments.