amhuppert
51 verified skills52 total stars
hotkey-helper
Use when picking or vetting a keyboard shortcut on macOS. Triggers include "what hotkey should I use for X", "is `<combo>` available", "does this shortcut conflict", "recommend a keybinding for…", "check `<combo>` against my setup", "pick a hotkey for…", or any mention of choosing/binding/changing a shortcut in WezTerm, tmux, Zed, Chrome, Claude Code, or macOS. Determines whether a proposed combo collides with OS-reserved bindings, app defaults, or the user's customizations, and recommends ergonomic alternatives when needed.
tools2
cursor-rules-synchronizer
Synchronizes Cursor Rules (.mdc files in .cursor/rules/) to CLAUDE.md by generating a Rules section with context-efficient descriptions and usage instructions. Use when setting up Cursor Rules for the first time, after adding or modifying rules, or when the Rules section in CLAUDE.md is missing or outdated.
testing1
config-audit
This skill should be used when auditing or comparing Claude Code and Cursor IDE configurations to identify feature gaps, equivalencies, and migration opportunities. Useful when managing AI development tooling across both platforms or deciding how to structure AI workflows.
tools1
claude/ai-resources-plugin/skills/add-design-agent
--- name: add-design-agent description: Create a research or review agent for the /design workflow. disable-model-invocation: true argument-hint: [research|review] [agent-name] allowed-tools: Read, Write, Edit, AskUserQuestion --- Create a new project-specific design agent that integrates with the `/design` workflow. ## Arguments - `$1`: Agent type (optional) - "research" or "review" - **research**: Domain expert that gathers information during Phase 2 (before design synthesis) - **review
tools1
analyze-ralph-logs
This skill should be used when analyzing Ralph Loop workflow executions to diagnose failures, understand execution flow, or review what happened during the most recent run. Use when the user says "analyze ralph logs", "what happened with ralph", "ralph stopped", "ralph failed", "debug ralph", or wants to understand why a Ralph Loop execution ended unexpectedly.
development1
benchmark-chicken-svg
Model comparison benchmark for generating an SVG image.
data-ai1
configure-ralph
This skill should be used when the user wants to configure ralph-claude-code for a new objective. It updates .ralph/PROMPT.md and .ralph/fix_plan.md files in projects that already have Ralph enabled. Use when the user says "configure ralph", "set up ralph for", "update ralph for a new objective", or wants to start a new development objective with Ralph.
development1
create-requirements
Create a PRD / product requirements document with app summary, design principles, and detailed requirements.
testing1
init-design-config
Initialize DESIGN-AGENTS.md config for the /design workflow, populated from project context.
data-ai1
latex
Generate LaTeX documents (or convert markdown to LaTeX) with professional typography. Optionally compile to PDF.
development1
local-commit
This skill should be used when the user wants to commit changes to the local private repository using lgit. It manages versioning of private AI configuration files.
data-ai1
local-init
This skill should be used when the user wants to initialize a new local private repository in the current directory. This sets up the .local directory for versioning private AI configuration files separately from the main repository.
data-ai1
model-price-compare
Compare AI model prices across Anthropic, OpenAI, and Google. Generates pages-per-dollar / cost-per-token visualizations.
development1
nano-banana-prompt
Create a high-quality image generation prompt for Google's Nano Banana 2 (NB2) model on Gemini.
development1
reflection
Reflect on the conversation and propose improvements to CLAUDE.md configuration files.
tools1
sdd-to-ralph
This skill should be used when the user wants to convert completed CCSDD specs into Ralph execution artifacts. Use when user says "bridge spec to ralph", "convert sdd to ralph", "sdd to ralph", "generate ralph from spec", "prepare spec for ralph", or wants to take a cc-sdd feature spec and run it through Ralph for autonomous implementation.
tools1
write-tests
Write automated tests. Guides test selection, mocking strategy, and writing tests that verify behavior over implementation.
testing1
break-into-subtasks
Break frontend feature requirements into parallelizable subtasks (API, UI, integration) with dependencies and a Mermaid diagram.
development1
claude/ai-resources-plugin/skills/browser-automation
--- name: browser-automation description: Automate browser interaction with Playwright: open pages, take screenshots, verify UI, test flows, debug pages, inspect elements. allowed-tools: Bash(playwright-cli:*), Bash(npx:*), Bash(npm:*), Bash(which:*), Bash(test:*), Bash(ls:*) --- # Browser Automation with Playwright Route the request to the right tool and let the dedicated skill drive the interaction. This file does **not** teach Playwright usage — it picks the tool, ensures the right skill is
tools1
compress
Compress and optimize AI instructions to be clearer, more concise, and more efficient.
testing1
explainer-document
Write a concise explainer / learning document / beginner guide that teaches a topic to someone unfamiliar with it.
testing1
Save Current Context
Save current session context to a handoff file so a future AI agent can continue with no prior context.
data-ai1
claude/ai-resources-plugin/skills/web-debugger
--- name: web-debugger description: Debug a running web app via the web-debugger SDK: app logs, application state, runtime snapshots, React state, query cache. --- # Web App Debugger Runtime debugging for web applications via the `web-debugger-mcp` server. Provides structured logs and on-demand state snapshots from both browser and server — all saved to files for context-efficient consumption. ## Architecture ``` ┌─────────────┐ WebSocket ┌──────────────────┐ stdio ┌───────────┐ │ Web
tools1
commit
Commit staged git changes after generating and approving a message.
tools1
claude/ai-resources-plugin/skills/setup-perf-stack
--- name: setup-perf-stack description: Bootstrap web performance debugging tooling: install chrome-devtools-mcp and related MCP servers/skills. disable-model-invocation: true --- # Setup: Performance Debugging Stack Bootstrap the MCP servers and skills required for Claude Code to autonomously investigate performance issues in web applications. This skill only handles **installation**. For the actual investigation workflow (the reproduce → capture → analyze → fix → validate loop, framework-sp
tools1
assess-project-context
Assess / rate the default project context (CLAUDE.md, onboarding). Scores how well it conveys the project to AI across six dimensions, with improvement recommendations.
data-ai1
claude/ai-resources-plugin/skills/ai-validation-output
--- name: ai-validation-output description: Configure AI-optimal validation: pre-commit hooks, CommandCenter.json, and low-noise linter/test/typecheck output for AI agents. --- # AI-Optimal Validation Output Configure validation tools (linters, type checkers, test runners) to produce output optimized for AI agent consumption. AI agents read every line of tool output, and each line consumes tokens. Default output is designed for human eyes — color codes, progress bars, per-file success messages
tools1
approve
Approve and execute a previously created implementation plan with no deviation.
development1
claude/ai-resources-plugin/skills/changes-tour-guide
--- name: changes-tour-guide description: Walk through recent code changes pedagogically: a two-phase markdown guide (overview, then detailed explanations) in dependency order. allowed-tools: Read, Write, Bash(git diff:*), Bash(git log:*), Bash(git status:*), Bash(git show:*) disable-model-invocation: true --- # Code Change Review Guide Creator Create a structured markdown document that walks a reader through code changes in a clear, logical, and pedagogical manner using a two-phase approach.
tools1
changelog-review
Review the Claude Code changelog and summarize recent changes and their significance.
development1
design
Create or iterate on a software design via a multi-agent workflow with parallel research and review phases. Stores artifacts in memory-bank/planning/{name}/.
data-ai1
create-plan-anthropic
Create a decision-complete implementation plan that can be executed mechanically without further design decisions.
testing1
code-standards-review
Review a codebase for adherence to code standards. Uses specialized agents with progressive disclosure to determine which standards apply.
development1
create-reference
Create or update an AI-optimized reference document for a tool, library, framework, or API via thorough research.
tools1
cheat-sheet
Create a 1-2 page cheat sheet / quick reference for a tool, language, or framework.
tools1
fix-merge-conflicts
Resolve git merge conflicts. Use when git status shows unmerged paths or files contain conflict markers (<<<<<<< / ======= / >>>>>>>).
data-ai1
steer
Reflect on codebase navigation effectiveness at end of conversation. Surfaces dead ends, inefficiencies, missing context. Does not write files — pair with /kiro:steering-custom to persist.
development1
optimize-tsconfig
Optimize tsconfig.json for build speed, watch mode, and tsc memory. Use for slow tsc, too many file watchers, or TypeScript performance audits.
development1
claude/ai-resources-plugin/skills/understand-objective-anthropic
--- name: understand-objective-anthropic description: Thoroughly understand a software development objective before implementation: research, identify ambiguities, ask clarifying questions. --- # Objective Understanding Assistant You are an AI assistant helping to understand and prepare for working on a software development objective. Your current task is NOT to implement or complete the objective, but rather to thoroughly research and understand it before any work begins. You will be provide
tools1
worktree
Create a git worktree for parallel Claude Code sessions.
development1
transcript-path
Locate the on-disk Claude Code transcript file (.jsonl under ~/.claude/projects/) for the current or a specified conversation.
development1
claude/ai-resources-plugin/skills/jog-users-memory
--- name: jog-users-memory description: Jog the user's memory after they've been away: a brief, scannable summary of progress, next steps, and open questions. disable-model-invocation: true allowed-tools: Read, Bash(git log:*), Bash(git status:*), Bash(git diff:*) --- # Context Refresh Quick memory jog for returning to work after being away. ## Instructions ### 1. Gather Context (parallel where possible) **From git:** - Run `git log --oneline -15` to see recent commits - Run `git status --
tools1
claude/ai-resources-plugin/skills/investigate-web-perf
--- name: investigate-web-perf description: Investigate web perf issues: LCP/INP regressions, slow interactions, unnecessary React re-renders, bundle bloat, memory leaks, ForcedReflow. Uses chrome-devtools-mcp traces. Requires setup-perf-stack. --- # Investigate Web Performance Issues Disciplined, evidence-driven investigation of web app performance problems using `chrome-devtools-mcp`. This skill is the canonical loop; references are loaded on demand based on the scenario and framework. **Pr
tools1
react-scan
This skill should be used when the user asks to "set up react-scan", "install react-scan", "diagnose React re-renders", "find unnecessary renders", "find unstable props", "automate React render checks with Playwright", "react-scan + playwright", "measure component renders programmatically", "check why a React component is slow", or mentions React rendering issues, slow React interactions, render counts, or component-level perf attribution. Covers install across Next.js/Vite/Remix/script-tag/browser-extension, the lite headless API for CI, and the canonical render-attribution → fix → validate loop driven through Playwright.
tools1
claude/ai-resources-plugin/skills/init-voice-config
--- name: init-voice-config description: Initialize voice-to-text config for the project: voice.json, voice-vocabulary.md, voice-context.md. disable-model-invocation: true allowed-tools: Read, Glob, Grep, Write(voice.json), Write(voice-context.md), Write(voice-vocabulary.md), Agent --- # Initialize Voice-to-Text Project Config Create a local `voice.json` config, a `voice-vocabulary.md` vocabulary file, and a `voice-context.md` context file in the current directory. These cover the **clipboard
tools1
add-voice-context
Add terms, context, or instructions to voice-to-text files for clipboard/file mode (F9/F10) or shell-command mode (F8), at project or global level.
tools1
knowledge-base-ingest
This skill should be used when integrating source material into a knowledge base, including when the user asks to "integrate this document into the knowledge base", "add this transcript to the memory bank", "ingest this document", "update the knowledge base", "analyze a new source document", or "sync current-state docs with this source".
documentation1
configure-editor-schema
Wire an existing JSON Schema into VS Code, Cursor, and/or Zed so it provides validation and IntelliSense for matching JSON or YAML files.
development1
claude/ai-resources-plugin/skills/kb-ingest
--- name: kb-ingest description: Delegate knowledge-base ingestion to the `knowledge-base-ingester` sub-agent so the source document, primary/current trees, and ingest workflow stay out of the main conversation's context window. Run this when the user explicitly invokes `/ai-resources:kb-ingest`; do not auto-trigger from natural-language ingestion requests (those should use the `knowledge-base-ingest` skill directly). disable-agent disable-model-invocation: true --- # kb-ingest Run a knowledge
tools1
cursor-rules
This skill should be used when creating or editing Cursor rules files (.mdc format) in the .cursor/rules directory. Provides guidance on rule types, frontmatter configuration, effective rule writing patterns, and best practices for structuring AI instructions for Cursor IDE.
development1
knip
Detect and remove dead code with knip. Use when the user asks to "run knip", "find unused files", "find unused exports", "find unused dependencies", "clean up dead code", "remove dead code", "set up knip", "configure knip", "knip.json", "knip false positive", "knip CI", or mentions a `knip` config, dependency bloat, bundle bloat from unused imports, or tree-shaking unused exports. Covers the configuration-first workflow, confidence-gated deletion, framework-specific gotchas (Next.js 15+, Tailwind, Storybook, Jest, Bun's test runner and `bun build --compile`), monorepos, CI integration, and performance tuning.
development1