architecture

Summarize Petri's architecture patterns, including MVU and Intent System.

5|Updated Jan 2, 2026
One-click install
npx skills add https://github.com/suzbot/petri --skill architecture-suzbot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/suzbot/petri/tree/main/.claude/skills/architecture
Command: npx skills add https://github.com/suzbot/petri --skill architecture-suzbot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a concise overview of the core architectural patterns used in the Petri project, helping developers quickly grasp the design principles before diving into the codebase.

Core Features & Use Cases

  • Architecture Overview: Summarizes key design patterns like MVU, Intent System, and data structures.
  • Pattern Documentation: Points to specific sections in docs/architecture.md for detailed explanations.
  • Use Case: A new developer joining the Petri project can use this Skill to get a high-level understanding of how the game logic is structured, making it easier to contribute to specific features.

Quick Start

Use the architecture skill to get a quick reference to Petri's architecture patterns.

Frequently Asked Questions about architecture

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

FAQPage Schema
What is the MVU pattern in game development architecture?

The architecture of Petri uses the Intent System to handle game logic, which is summarized as a core design pattern alongside MVU and data structures to help developers understand code structure before exploration.

How do I understand design patterns before exploring a game codebase?

Game architecture data structures for orders, actions, procurement, and item models are summarized in this reference, providing a high-level understanding of how these elements are structured within the project.

Does this architecture reference cover item models and procurement logic?

To understand project design patterns, this reference summarizes architectural patterns like MVU and the Intent System, pointing to specific sections in documentation for detailed explanations of orders, actions, and item models.

When do I need a quick reference for game architecture patterns?

Game architecture documentation details for orders, actions, and procurement are located in `docs/architecture.md`, with this reference providing a concise overview and pointing to those specific sections.