CI/CD

Store and retrieve long-term project context, architectural decisions, and learnings.

Provides expert design guidance for creating truthful, clear, beautiful data visualizations. Focuses on **DESIGN DECISIONS ONLY**—chart selection, color strategy, visual encoding, and validation. Assumes data is accurate and prepared. Auto-activates when user mentions: data viz, dashboard, chart type, visualization, infographic

RESTful API design and OpenAPI specification generation. Use when: (1) Designing new REST API endpoints, (2) Creating OpenAPI/Swagger specifications, (3) Choosing HTTP methods, status codes, or URL patterns, (4) Implementing pagination, filtering, or sorting, (5) Planning API versioning strategy, (6) Reviewing API design for best practices, (7) Generating API documentation templates.

Review weekly notes, tasks, and meetings to surface items at risk of being dropped.Use when user requests a weekly review, uses /weekly-review, or asks to review a specific week.Invocation: /weekly-review [date|week-number]Examples: /weekly-review, /weekly-review 2025-03-12, /weekly-review 2025-W12

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.

Configure FastAPI for Vercel deployment.Bundled Resources: Includes 'vercel.json', CORSMiddleware, Python logging, Pydantic models, and personalization endpoints.

Build MCP (Model Context Protocol) servers for CasareRPA integrations using Python FastMCP. Covers server structure, tool design, error handling, and RPA-specific patterns. See references/ for detailed guides. Use when: creating MCP servers, tool design, error handling, RPA-specific patterns, FastMCP, Context logging, lifespan hooks.

OPA resource governance policies enforcing CPU/memory limits, ResourceQuota compliance, LimitRange validation, and storage constraints.

Use when creating or editing skills, before deployment, to verify they work under pressure and resist rationalization - applies RED-GREEN-REFACTOR cycle to process documentation by running baseline without skill, writing to address failures, iterating to close loopholes

Bulk-complete tasks/steps in a project. Load when user says "bulk complete [project]", "mark all done", "complete phase X", or needs to finish project tasks efficiently. Works with both steps.md and tasks.md formats.

Automated release coordination and deployment with swarm orchestration for seamless version management, testing, and deployment across multiple packages. Use for release pipelines, version coordination, deployment orchestration, and release documentation.

Perform critical code review with automated fix suggestions. Use when reviewing code changes, pull requests, specific files, or branch diffs. Triggers on requests like "review this code", "critical review", "code review for PR