CI/CD

A custom skill that helps with specific tasks in my project

Comprehensive FHIR (Fast Healthcare Interoperability Resources) software development assistant. Use when working with FHIR APIs, implementations, or healthcare data exchange. Supports FHIR R4, R4B, R5, Implementation Guides (IGs), validation, terminology, and SMART on FHIR. Ideal for building FHIR servers, clients, validators, or healthcare applications that need to process FHIR resources.

Guide for creating effective skills. This skill should be used 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.

Employ a coarse-grained, service-based architecture (a lighter form of SOA) when microservices are not yet necessary but modular deployment is required.

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

Build Model Context Protocol servers for Claude Code integration

Add authentication and authorization to routes, Server Actions, and API endpoints using Supabase Auth. Use when user needs "protect [route]", "add authentication", "require login", "add RBAC", "implement login/logout", or mentions auth, permissions, OAuth, API keys. Provides patterns for protected routes, Server Action auth checks, role-based access control (5 roles), OAuth providers (Google, GitHub), email verification, password strength, account lockout, and API key authentication. Do NOT use when building new features (use worldcrafter-feature-builder which can add auth), database-only changes (use worldcrafter-database-setup for RLS policies), routes without auth (use worldcrafter-route-creator), or testing only (use worldcrafter-test-generator).

Phase 3 of disciplined development. Executes approved implementation plansstep by step. Each step includes tests, follows the design exactly, andproduces reviewable commits.

Reference the project's defined technology stack including frameworks, languages, databases, testing tools, and deployment infrastructure. Use this skill when making technology decisions or choosing libraries. When working with project configuration files like package.json, requirements.txt, or Gemfile. When setting up new features that need to align with existing technology choices. When onboarding to understand the project's technical foundation. When choosing tools for testing, linting, CI/CD, or third-party services.

Generate GitHub issues from an approved engineering specification. Use to break down a spec into implementable, atomic tasks with dependencies, sizing, and labels.

Expert knowledge of WAI-ARIA (Accessible Rich Internet Applications). Use when users ask about ARIA roles, states, properties, accessible name computation, ARIA attributes (aria-label, aria-labelledby, aria-describedby, etc.), widget roles, landmark roles, live regions, ARIA best practices, or how to implement accessible interactive components. Also use for questions about ARIA specifications, API mappings (core-aam, html-aam), digital publishing ARIA (dpub-aria), graphics ARIA, or any ARIA implementation questions.

Audit and refactor Tailwind CSS usage for consistent theming across the codebase. Detects hardcoded colors, arbitrary values, and inconsistencies, then guides file-by-file updates with user approval.

Incident response playbook templates for Kubernetes. Detection, containment, remediation, and post-incident procedures with decision trees and validation steps.

This skill should be used when the user asks about "package development workflow", "release process", "beta testing", "package versioning", "CumulusCI", "CI/CD for packages", or needs guidance on the end-to-end package development process from design through release.

Official ollama Python library for LLM inference. Provides a clean,Pythonic interface for text generation, chat completion, embeddings,model management, and streaming responses.

AI-powered recommendation engine specialist using Google AI SDK for personalized content suggestions

[Extends e2e-tester] BDD/Cucumber specialist. Use for Gherkin feature files, step definitions, Cucumber-JVM/JS, Spring/Playwright integration. Invoke alongside e2e-tester for BDD testing approach.

Implement robust error handling with user-friendly messages, fail-fast validation, specific exception types, centralized error boundaries, graceful degradation, retry strategies, and proper resource cleanup. Use this skill when writing try-catch blocks or exception handling code in any programming language (JavaScript/TypeScript, Python, Java, Go, Rust), implementing error boundaries in React (ErrorBoundary components) or similar error handling patterns in other frameworks (Vue error handlers, Angular ErrorHandler), handling API errors and HTTP error responses in fetch calls, Axios requests, or tRPC procedures, validating user input and function preconditions at the start of functions, creating custom error classes or exception types for specific failure scenarios (ValidationError, NotFoundError, UnauthorizedError, PaymentError), implementing retry logic with exponential backoff for external service calls, network requests, or database queries, ensuring proper resource cleanup in finally blocks or using langu

Create reversible, focused database migrations with proper naming, version control practices, and zero-downtime deployment considerations. Use this skill when creating or editing migration files in database/migrations/, when writing schema changes (creating/modifying tables, columns, indexes, foreign keys), when implementing migration rollback methods, when managing database version control, when adding or modifying indexes on large tables, or when separating schema changes from data migrations for safer deployments.

Use when writing pytest tests, creating fixtures, mocking dependencies, or testing async code - provides patterns that verify actual behavior with proper fixtures and parametrization; prevents testing mocks instead of code (plugin:python@dot-claude)