Skills Registry

Analyzes Astro 5 projects (.astro, astro.config.mjs/ts) to identify performance issues, applies 47 optimization rules across 8 prioritized categories (islands architecture, build optimization, content collections, image optimization, component patterns, view transitions, environment config, advanced patterns), and refactors code following partial hydration best practices. Use when building Astro sites, configuring SSG/SSR/hybrid rendering, implementing islands with client:* directives, setting up content collections, or optimizing images and assets. Do NOT use for non-Astro frameworks like Next.js, Nuxt, or SvelteKit.

Generates Azure Bicep module files following established project conventions, with secure-by-default and cost-optimised configurations. Reads per-resource .md reference files for security baselines, cost guidelines, and code patterns. Use when creating a new Bicep module, adding a resource to an existing module, writing a role assignment module, or reviewing Bicep for convention violations. Validates parameter ordering, decorator patterns, security defaults (RBAC, soft delete, TLS 1.2, private endpoints), cost-appropriate SKU defaults, idiomatic output ordering, and code patterns (role GUIDs, conditional resources, private endpoints, parent-child relationships, null-safe access). Do NOT use for Terraform, ARM JSON, or Pulumi authoring.

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of "Word doc", "word document", ".docx", or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a "report", "memo", "letter", "template", or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.

Creates and orchestrates high-performance GSAP animation components — page loaders, scroll effects, text reveals, navigation transitions, slideshows, and micro-interactions. Generates production-ready code with state gating, defensive DOM queries, and proper cleanup. Use this skill whenever the user asks to build animations, motion design, page transitions, loading sequences, scroll-triggered effects, parallax, text splitting/revealing, animated navigation menus, slideshows, or any interactive motion component. Also trigger when users mention GSAP, GreenSock, ScrollTrigger, SplitText, Physics2D, Lenis smooth scroll, or want to add "life" or "polish" to a UI. Covers vanilla JS, React, Next.js, and Astro implementations. Do NOT use for CSS-only animations, Framer Motion, or non-animation frontend tasks like routing or state management.

Comprehensive guidance for designing and optimizing n8n 2.0+ (2026) workflows. Handles requirements analysis, node selection (Standard vs. AI Agent), and isolated Code node development. Use when the user says 'Help me create an n8n workflow', 'Build an automation for...', or 'Debug my n8n JavaScript code'. Do NOT use for general software engineering unrelated to n8n logic.

Extracts, processes, converts, and handles all PDF file operations. Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.

Generates, runs, and debugs Playwright end-to-end tests for web applications. Automates browser testing setup, creates test files with accessible locators, and validates UI behavior. Use when the user asks to add tests, write e2e tests, test the frontend, verify UI behavior, add Playwright, set up browser testing, or when Claude needs to verify that frontend changes work correctly after implementation. Also triggers for requests like "make sure this works", "test the UI", "check the page renders", or any task involving browser-based verification of a React/Vite/Next.js application. Do NOT use for unit tests, component-level testing with Jest/Vitest, or backend API testing without a browser.

Analyzes React and Vite code (.tsx, .jsx, .ts, .js) to identify performance issues, applies 40+ optimization rules across 7 prioritized categories (waterfalls, bundle size, data fetching, re-renders, rendering, JavaScript, advanced patterns), and refactors code following TanStack Query best practices. Use when optimizing React components, reducing bundle size, eliminating async waterfalls, fixing re-render issues, or implementing efficient data fetching patterns. Do NOT use for backend/server-side optimization or non-React frameworks like Vue or Angular.

Creates and validates effective agent skills. Walks users through use case definition, frontmatter generation, instruction writing, progressive disclosure design, and packaging. Use when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations. Do not use for general software engineering tasks unrelated to skill authoring.

Velais AI Solutions brand identity guidelines covering color palette, typography, logo usage, gradients, brand voice, and visual patterns. Use when creating or reviewing any Velais-branded output: websites, documents (.docx), presentations, marketing materials, social media graphics, or PDFs. Triggers on: designing Velais pages or components, choosing colors or fonts for Velais content, creating Velais-branded documents or presentations, reviewing designs or copy for brand consistency, embedding Velais logos, or any task requiring Velais visual identity decisions. Do NOT use for general design advice unrelated to Velais, or for framework-specific implementation details (Tailwind config, CSS-in-JS setup).

Formats rendered markdown and prose content with the Velais brand identity. Use when adding blog posts, documentation pages, changelogs, or any long-form markdown content to a Velais website (Astro or Vite+React). Configures the portable `prose-velais` CSS class (.css) and integrates framework-specific layouts for .astro, .tsx, and .mdx files. Do NOT use for general UI layout, component design, or color system setup — use `velais-ui-design` for those tasks.

Provides the single source of truth for building Velais-branded internal UI products. Use when starting a new Velais dashboard, tool, or client-facing app; replicating the Loader or LoginPage components (.tsx files); setting up the color system (CSS tokens, Tailwind classes), typography (Onsite Extended font, WOFF2/WOFF files), or GSAP animation conventions; or configuring shadcn/ui (New York style) for a Velais project. Covers the full tech stack (React 19 + TypeScript + Vite + Tailwind CSS 4 + TanStack React Query + GSAP + Hono). Do NOT use for general design advice unrelated to Velais, Azure DevOps API integration, or backend/auth configuration (WorkOS, Hono middleware).