pdugan20

Refreshes the Claude Code docs baseline, runs the conformance check, and recommends schema and rule updates. Use when asked to "check for upstream changes", "check schema drift", "are our schemas up to date", or "what is new in Claude Code".

I do it

Formats Claude Code files with markdownlint, prettier, and shellcheck. Use when user asks to "format my files", "fix markdown formatting", "clean up CLAUDE.md", or "check shell scripts". Auto-fixes markdown, JSON, YAML formatting and analyzes shell script quality.

Interactively helps users optimize their CLAUDE.md files. Use when user asks to "optimize my CLAUDE.md", "my CLAUDE.md is too long", "improve organization", or "split my CLAUDE.md". Runs validation, explains issues conversationally, and helps create @import files to reduce size and improve structure.

Runs comprehensive claudelint validation on all Claude Code project files. Use when user asks to "check everything", "run all validators", "full audit", "validate my entire project", or "what's wrong with my config". Validates CLAUDE.md, skills, settings, hooks, MCP servers, and plugin manifests.

Validates CLAUDE.md files for size, imports, and structure. Use when user asks to "check my CLAUDE.md", "why is my CLAUDE.md too long", "validate imports", or "fix CLAUDE.md errors". Checks file size limits (30KB warning, 50KB error), @import directives, frontmatter in .claude/rules/, and section organization.

Validates Claude Code hooks.json files for schema, events, and commands. Use when user asks to "check my hooks", "validate hooks.json", "hook errors", "why isn't my hook firing", or "hook event types". Validates hook events, types (command, prompt, agent), matcher patterns, and command script references.

Validates MCP server configuration files (.mcp.json). Use when user asks to "check my .mcp.json", "why isn't my MCP working", ".mcp.json errors", "validate MCP servers", or "MCP connection failed". Validates transport types (stdio, sse, http, websocket), server names, and environment variables.

Design or repair one Apple App Intents system integration while preserving app-owned data, concurrency, routing, privacy, and availability boundaries. Use for AppIntent and AppEntity work that exposes an action or entity through Siri and Shortcuts; Spotlight; widgets or controls; snippets; the Action button; App Schemas; onscreen context; or AppIntentsTesting. Do not use for ordinary in-app SwiftUI work or broad Apple-platform setup that does not cross an App Intents surface.

Diagnose and tune one user-visible performance problem in a Swift, SwiftUI, React Native, or Expo mobile feature by tracing the first missed deadline across motion, rendering, state publication, media, storage, network, and observability, then applying and verifying the smallest causal change. Use when an interaction, animation, scroll, keyboard transition, first paint, or loading path is jittery, stalled, late, or less seamless than expected and the bottleneck is uncertain. Do not use for broad app performance audits, motion ideation or craft review without a runtime symptom, recording-only analysis, backend-only optimization, or release hardening.

Use when creating or initializing a new software repository, or turning an empty or newly generated project directory into a maintained local and GitHub-ready repository. Applies across Swift, Expo or React Native, Python, React or TypeScript, and other stacks. Do not use for auditing or modernizing an established repository, adding one CI job, implementing product features, deploying, or publishing.

Use when a user wants to brainstorm or compare multiple runnable UI, interaction, layout, visual, or motion directions in an existing web or native app before choosing one. Do not use for exact implementation of a selected design, production delivery, audits, or requested static or generated mockups.

Take a substantial production feature from an idea or selected behavior through specification, coordinated implementation, integration, and staged user availability. Use when delivery spans meaningful product or architecture decisions, multiple repositories or subsystems, important data or security boundaries, client and backend compatibility, or controlled rollout. Do not use for UI direction exploration, bounded feature spikes, hardening-only work, deployment of an already completed build, small fixes, or ordinary isolated changes.

Build the smallest decision-producing slice that validates a feature's value or technical feasibility before production investment. Use when a user asks for a feature spike, proof of concept, capability probe, or bounded experiment to decide whether or how to proceed. Do not use for comparing multiple UI directions, delivering an already-approved production feature, general research that needs no runnable evidence, production hardening, or experiments inside an established implementation.

Review one completed UI component or bounded surface against the design system evidenced in its repository, classify accidental deviations, intentional exceptions, system gaps, and uncertainty, then apply only approved corrections. Use for post-build UI conformance or normalization. Do not use for UI ideation, repository-wide audits, exact design translation, or general production hardening.

Use when a user supplies a UI screen recording or video and asks to dissect, diagnose, reverse engineer, compare expected and observed behavior, or explain how it could map to a target repository. Do not use for static screenshots, code-only motion review, video editing, or implementation requests without video evidence.

Deprecated compatibility skill from the archived mintlify-docs repository. Direct users to install pdugan20/skills and use write-mintlify-changelog; do not run this historical copy for new work.

Deprecated compatibility skill from the archived mintlify-docs repository. Direct users to install pdugan20/skills and use generate-mintlify-reference; do not run this historical copy for new work.

Deprecated compatibility skill from the archived mintlify-docs repository. Direct users to install pdugan20/skills and use review-mintlify-docs; do not run this historical copy for new work.

Deprecated compatibility skill from the archived mintlify-docs repository. Direct users to install pdugan20/skills and use scaffold-mintlify-site there; do not run this historical copy for new work.

This skill should be used when the user asks to "add a movie", "add a vinyl", "add to my collection", "add physical media", "add a Blu-ray", "add a CD", or "bought these records". It handles both movies (via TMDb/Trakt) and music (via Discogs).

This skill should be used when the user asks to "add a changelog entry", "write changelog", "audit changelog", "review changelog", "check changelog entries", or is editing docs-mintlify/changelog.mdx. Enforces a consistent, reader-facing voice and cuts implementation trivia.

This skill should be used when the user asks to "search for a movie", "find a record on Discogs", "look up a film", "search TMDb", "search Discogs", "what's the TMDb ID for", "what's the Discogs ID for", or wants to look up media metadata before adding it to the collection.

Use when creating or initializing a new software repository, or turning an empty or newly generated project directory into a maintained local and GitHub-ready repository. Applies across Swift, Expo or React Native, Python, React or TypeScript, and other stacks. Do not use for auditing or modernizing an established repository, adding one CI job, implementing product features, deploying, or publishing.

Build the smallest decision-producing slice that validates a feature's value or technical feasibility before production investment. Use when a user asks for a feature spike, proof of concept, capability probe, or bounded experiment to decide whether or how to proceed. Do not use for comparing multiple UI directions, delivering an already-approved production feature, general research that needs no runnable evidence, production hardening, or experiments inside an established implementation.

Reviews a Mintlify documentation site's information architecture, editorial quality, source fidelity, and launch readiness in navigation order, then makes approved targeted edits. Use for Mintlify site audits, content passes, or page-level reviews; do not use for general code review, changelog entries, or generated reference pages.

Explore and compare UI, interaction, layout, visual, or motion directions as runnable code in the existing project, browser, or relevant simulator. Use for lightweight design exploration, UI variants, visual revisions, prototypes, pixel tuning, or requests to brainstorm and compare interface directions. Do not use for production feature delivery, audit-only requests, or when the user explicitly asks for generated images or static image mockups.

Implement a substantial production-ready feature with proportional planning, coordinated implementation, risk-based testing, review, and verification. Use when the user asks to build, implement, or ship a production feature that spans multiple meaningful behaviors or subsystems, changes important data or security boundaries, or requires coordinated release checks. Do not use for lightweight UI iteration, visual exploration, prototypes, copy or motion tuning, small fixes, or ordinary isolated changes.

Prepare a selected implementation for production by auditing risk, accessibility, failure handling, security, performance, observability, cleanup, and verification. Use only when explicitly invoked after exploration or implementation; do not trigger during lightweight design iteration.