fvtt-sheets

Build and migrate Foundry VTT ActorSheet and ItemSheet components across V1 and V2 APIs.

1|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/ImproperSubset/hh-agentics --skill fvtt-sheets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fvtt-sheets
Source: https://github.com/ImproperSubset/hh-agentics/tree/main/fvtt-dev/skills/fvtt-sheets
Command: npx skills add https://github.com/ImproperSubset/hh-agentics --skill fvtt-sheets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps Foundry VTT developers create and extend ActorSheet and ItemSheet classes, implement getData or _prepareContext, bind events with activateListeners, and configure drag/drop, while guiding migration from ApplicationV1 to V2 for consistency and maintainability.

Core Features & Use Cases

  • Build and migrate Foundry VTT sheets for both legacy (V1) and modern (V2) patterns.
  • Provide clean extension points for ActorSheet/ItemSheet, including getData, _prepareContext, and activateListeners.
  • Establish consistent drag/drop, templating, and event handling to ensure reliable UI behavior.
  • Use in real-world projects to accelerate module or system development with predictable sheet structures.

Quick Start

Create a basic sheet by extending ActorSheetV2, override _prepareContext, and bind events in activateListeners, then hook up drag/drop for item handling.

Frequently Asked Questions about fvtt-sheets

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

FAQPage Schema
How do I migrate a Foundry VTT ActorSheet from ApplicationV1 to V2?

Migrate Foundry VTT ActorSheet components from ApplicationV1 to V2 by overriding _prepareContext instead of getData, updating event binding, and configuring drag/drop handlers to ensure interoperability and maintainability.

What is the best way to structure event binding in a Foundry VTT ItemSheet?

Structure Foundry VTT ItemSheet event binding by overriding activateListeners, ensuring consistent drag/drop configuration and reliable UI behavior across both legacy and modern APIs.

Do I need to know the Foundry VTT sheet APIs to build a custom sheet?

Yes, building custom Foundry VTT sheets requires familiarity with ActorSheet and ItemSheet APIs to properly extend classes, implement context preparation, and ensure production-ready module structures.

How does getData differ from _prepareContext in Foundry VTT sheet development?

getData prepares data for legacy ApplicationV1 sheets, while _prepareContext serves modern ApplicationV2 sheets, requiring developers to transition patterns for consistent template rendering and event handling.

Can I use drag-and-drop with both legacy and modern Foundry VTT sheet APIs?

Yes, you can configure drag-and-drop for items across both legacy and modern Foundry VTT sheet APIs by following structured extension points to establish consistent UI behavior.