Use this skill when the user asks about accessibility testing, axe-core, jest-axe, "@testing-library", "@axe-core/playwright", "Playwright accessibility testing", "WAVE", "Lighthouse accessibility", "automated a11y tests", "accessibility CI/CD", "eslint-plugin-jsx-a11y", "a11y linting", "axe DevTools", setting up accessibility tests, writing accessibility tests for React components, integrating a11y checks into a test suite, or understanding what automated tools can and cannot catch. Also use when asked to add automated a11y testing to a project.

Register a project resource (MCP server, CLI tool, script, or note) into CLAUDE.md's Resources section so `/startup` surfaces it every session. Creates the Resources section if missing. Trigger when the user says "/add-resource", "add to project resources", "remember this MCP for the project", "save this tool to CLAUDE.md", "register this resource", "remember we have X available here", "add X to the resources section".

This skill should be used when working on any Astro project or when the user asks about Astro best practices, conventions, or patterns. Trigger when: working on an Astro project, creating Astro components/pages/layouts, configuring astro.config, setting up Content Collections, using Content Layer API, choosing client directives (client:load/idle/visible/media/only), using server:defer or server islands, deciding between SSR and SSG, working with Astro Actions for forms, configuring middleware, using Zod schemas for content, building with TypeScript in Astro, creating API endpoints, using @astro/autoload, working with .astro files, Astro 5 or Astro 6 development.

This skill should be used when working on Chrome extension permissions or Chrome Web Store compliance. Trigger when: declaring extension permissions, "manifest permissions", "activeTab vs tabs", "optional_permissions", "host_permissions", "Chrome Web Store rejection", "permission minimization", "over-permissioning", "CWS review", "Purple Potassium", "extension permission audit", "narrowest permission", "permission warnings", "chrome.permissions.request", "permission justification".

This skill should be used when working with data storage in Chrome extensions or when the user asks about extension storage patterns. Trigger when: "chrome.storage", "extension storage", "storage.local", "storage.sync", "storage.session", "IndexedDB in extension", "extension data persistence", "write-through cache", "storage quota", "unlimitedStorage", "chrome.storage.onChanged", "reactive storage", "WXT storage", "storage.defineItem", "storage migration", "sync vs local storage".

This skill should be used when building React UI for Chrome extensions or when the user asks about UI patterns in extensions. Trigger when: "React in extension", "extension popup React", "side panel React", "Shadow DOM React", "content script UI", "createShadowRootUi", "extension accessibility", "rem to px extension", "portal in extension", "React popup state", "extension UI patterns", "Radix in extension", "Shadcn extension", "extension keyboard navigation", "ARIA in extension", "focus management extension".

This skill should be used when provisioning databases in Coolify, configuring database backups, restoring database backups, setting up S3-compatible backup storage, managing database SSL/TLS, connecting external clients to Coolify databases, rotating database credentials, running migrations against Coolify databases, tuning database resource limits, or choosing between standalone databases and service databases. Trigger when: "Coolify database", "create database in Coolify", "Coolify PostgreSQL", "Coolify MySQL", "Coolify Redis", "database backup Coolify", "restore database Coolify", "S3 backup Coolify", "connect to Coolify database", "database migration Coolify", "Coolify MongoDB", "Coolify MariaDB", "Coolify ClickHouse", "database credentials", "database SSL Coolify".

This skill should be used when securing Coolify deployments, managing secrets and environment variables, configuring Docker Build Secrets, setting up RBAC team roles, isolating containers on the network, configuring resource limits (CPU/memory), hardening firewall rules (UFW), managing terminal access, or auditing Coolify security. Trigger when: "Coolify security", "Coolify secrets", "Coolify environment variables security", "Docker Build Secrets Coolify", "Coolify RBAC", "Coolify team roles", "Coolify network isolation", "Coolify firewall", "UFW Docker Coolify", "Coolify resource limits", "Coolify terminal access", "secure Coolify", "harden Coolify", "Coolify permissions", "Coolify audit log", "Coolify SSO", "Coolify OAuth".

This skill should be used when implementing Fastify hooks, understanding hook execution order, using onRequest/preParsing/preValidation/preHandler/preSerialization/onError/onSend/onResponse hooks, using onReady/onListen/onClose/onRoute/onRegister application hooks, debugging hook chain issues, adding authentication hooks, implementing request lifecycle interceptors, working with Fastify lifecycle events, or understanding when request.body is available.

This skill should be used when configuring Fastify logging, setting up Pino logger, using child loggers, implementing log redaction, configuring log transports, using pino-pretty for development, async logging with sonic-boom, structured JSON logging, request correlation IDs, log levels, configuring pino.final for crash handling, multi-target log transports, or Fastify observability.

This skill should be used when deploying Fastify to production, configuring Fastify security headers, setting up reverse proxy with Fastify, implementing graceful shutdown, configuring @fastify/helmet, @fastify/cors, @fastify/rate-limit, trustProxy settings, Kubernetes Fastify deployment, Fastify performance tuning, request timeouts, handler timeouts, return503OnClosing, prototype poisoning protection, production Fastify checklist, or hardening Fastify server.

This skill should be used when testing Fastify applications, using .inject() for HTTP testing, writing Fastify unit tests, testing Fastify plugins in isolation, separating app from server for testing, using light-my-request, testing route handlers, integration testing Fastify, test setup and teardown with Fastify, parallel test execution, testing Fastify hooks, or mocking in Fastify tests.

Coordinate a complete analysis across six phases over a defined audit surface (codebase + user-provided URL list), produce a unified score, and deliver a plain-English report with prioritized, actionable fixes.

This skill should be used when the user says "audit my README", "ground my README against the code", "check if my README overpromises", "review my README honestly", "rewrite my README without marketing language", "audit my marketplace listing", "check my plugin description", "ground this description against the code", "is my README honest", "does my README match the code", or wants to (a) audit an existing README/marketplace listing against actual code to find overpromise + unbacked claims, or (b) generate a README/listing from code with grounding controls so it doesn't overpromise. Two modes: `audit` (check existing) and `generate` (create new).

This skill should be used when the user says "send an email", "email someone", "compose a message", "write an email to", "send a Gmail", "draft and send", or wants to send a new outbound email through Gmail. Covers recipients, subject, body, CC/BCC, attachments, HTML content, and send-as aliases.

Manage Google Apps Script projects.

Evaluate these ideas, which idea is best, help me prioritize, compare these options, rank these, how do I choose. Structured evaluation via Impact/Effort Matrix, Assumption Mapping, Pre-Mortem, JTBD, weighted scoring.

Comprehensive reference for building Next.js applications with the App Router. Apply these standards whenever writing or reviewing Next.js code. Security-specific patterns are in the `nextjs-security` skill; testing in `nextjs-testing`; debugging in `nextjs-troubleshooting`.

This skill should be used when the user says "summarize this note", "progressive summarization", "distill this", "bold the key points", "highlight the important parts", "executive summary", "layer 2", "layer 3", "layer 4", "make this scannable", "TL;DR this article", "distill my notes", or pastes a raw note, article, transcript, or long text and wants it condensed into layered, scannable summaries. Applies Tiago Forte's Progressive Summarization technique.