foundry-vtt

Centralize Foundry VTT development and deployment guidance for modules, systems, and Kubernetes.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/kettleofketchup/KettleOfSkills --skill foundry-vtt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: foundry-vtt
Source: https://github.com/kettleofketchup/KettleOfSkills/tree/main/plugins/foundry-vtt/skills/foundry-vtt
Command: npx skills add https://github.com/kettleofketchup/KettleOfSkills --skill foundry-vtt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Foundry VTT development and deployment is highly fragmented, with scattered documentation for module building, system extension, testing, and self-hosted infrastructure setup, forcing developers and tabletop operators to waste time searching for consistent, up-to-date guidance.

Core Features & Use Cases

  • Module & System Development: Complete guidance for building Foundry modules and game systems using ApplicationV2, TypeDataModel schemas, Handlebars/Svelte templates, and the hooks event system, plus integration with dev tools like Vite, TypeScript, and libWrapper.
  • Infrastructure Deployment: Step-by-step instructions for deploying Foundry VTT via Docker, Helm charts, or raw Kubernetes/K3s manifests, including Traefik ingress configuration for WebSocket support and persistent storage setup with Rook-Ceph.
  • Testing & CI/CD: Patterns for in-Foundry Quench testing and external Jest/Vitest unit tests, plus GitHub Actions pipeline examples for automated module building, linting, and distribution.
  • System Extension: Dedicated reference for extending the WFRP4e game system with custom species, effects triggers, and config overrides. Use Case: A TTRPG developer building a custom WFRP4e module can use this skill to access the exact API references for effect triggers, generate a valid module.json manifest, and deploy the final add-on to a K3s cluster with a single Helm command.

Quick Start

Use the foundry-vtt skill to build a custom Foundry VTT module with ApplicationV2 actor sheets and deploy it to your K3s cluster via Helm with Traefik WebSocket ingress.

Frequently Asked Questions about foundry-vtt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a Foundry VTT module using ApplicationV2 and TypeScript?

To build a Foundry VTT module, you use ApplicationV2 for sheet architecture and TypeDataModel for schema definitions, compiled via a Vite and TypeScript build setup. This approach centralizes module development guidance to eliminate context switching and streamline Handlebars or Svelte template integration.

How do I deploy Foundry VTT to a Kubernetes cluster with Helm and Traefik?

You can deploy Foundry VTT to Kubernetes or K3s by applying raw manifests or installing Helm charts, configuring Traefik ingress for WebSocket support. This deployment workflow includes setting up persistent storage with Rook-Ceph to ensure instance data remains intact across pod restarts.

What is the best way to test a Foundry VTT module with Quench?

The best way to test a Foundry VTT module is implementing in-Foundry Quench test suites alongside external Jest or Vitest unit tests. This dual testing pattern ensures both internal client-side API logic and external utility functions are validated before distribution.

Does this Foundry VTT deployment guidance support Docker and K3s?

Yes, the Foundry VTT deployment guidance explicitly supports Docker, Helm charts, and raw Kubernetes/K3s manifests. It provides step-by-step infrastructure instructions including Traefik ingress configuration for WebSocket support and persistent storage setup using Rook-Ceph.

How do I extend the WFRP4e game system with custom species and effect triggers?

You extend the WFRP4e game system by utilizing dedicated API references for effect triggers, creating custom species, and applying config overrides within your module. This allows TTRPG developers to safely inject custom rules without altering the core system files.

How do I configure a module.json manifest and CI/CD pipeline for Foundry VTT distribution?

You configure a valid module.json manifest defining your add-on metadata, then implement a GitHub Actions pipeline for automated module building, linting, and distribution. This CI/CD workflow ensures consistent Foundry add-on releases directly from your repository.