foundry-vtt-system-architecture

Define layered architecture best practices for Foundry VTT systems.

1|Updated Mar 15, 2025
One-click install
npx skills add https://github.com/herveDarritchon/foundryvtt-swerpg --skill foundry-vtt-system-architecture
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: foundry-vtt-system-architecture
Source: https://github.com/herveDarritchon/foundryvtt-swerpg/tree/main/.agents/skills/foundry-vtt-system-architecture
Command: npx skills add https://github.com/herveDarritchon/foundryvtt-swerpg --skill foundry-vtt-system-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides comprehensive guidelines to ensure consistent, safe, and scalable architecture for developing and extending Foundry VTT systems.

Core Features & Use Cases

  • Architectural Consistency: Ensures development follows layered architecture principles for core, data, presentation, game systems, and integration.
  • Operational Guidelines: Defines best practices for lifecycle hooks, API exposure, configuration, and data modeling.
  • Use Case: When modifying a Foundry VTT system, follow this guide to maintain code quality and system integrity, for example updating document behaviors or configuration schemas.

Quick Start

Refer to the project documentation in 'documentation/architecture' to align your implementation with the established architecture rules.

Frequently Asked Questions about foundry-vtt-system-architecture

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

FAQPage Schema
What architectural patterns should I follow when developing a Foundry VTT system?▼

Foundry VTT system development should follow layered architecture principles, separating core, data, presentation, game systems, and integration layers to ensure robustness and maintainability.

How do I maintain API stability when extending Foundry VTT system features?▼

Maintain API stability by adhering to established lifecycle hooks, safe configuration schemas, and v13+ compliance standards, ensuring your extensions do not break core system behaviors.

Does this Foundry VTT architecture guide apply to data modeling and UI integrations?▼

Yes, these architectural guidelines apply directly to Foundry VTT data modeling, UI development, and system integrations, ensuring consistent and safe configuration across all layers.

What is the best way to structure a Foundry VTT system for long-term maintenance?▼

The best way to structure a Foundry VTT system for long-term maintenance is to enforce modular design and layered separation, isolating core features from presentation and integration logic.

How do I update Foundry VTT document behaviors without breaking system integrity?▼

Update document behaviors by aligning your implementation with established architecture rules and operational guidelines, ensuring safe configuration and data modeling practices are maintained.