gamedev

Game design documents and mechanics are managed in an Obsidian vault using wikilinks to navigate between GDD, architecture, and roadmaps. The skill automates these references, requiring standard vault paths and header links to connect design documentation.

Yes, the Obsidian skill must be loaded first to run these game development workflows. It relies on Obsidian integration to function, using standard vault paths and wikilink patterns to coordinate design references and session notes.

A playtest session is structured using dedicated workflows with notes and templates provided by the skill. It guides capture and coordination during playtests, linking observations back to mechanics and design docs within the Obsidian vault.

The best way to organize a dev session is using the Dev Session Start workflow. It centralizes navigation between roadmaps, architecture, and design docs via Obsidian wikilinks, streamlining session coordination and documentation.

Yes, you can bootstrap a new game project setup using quick-start templates and checklists. These tools help initialize project structures within the Obsidian vault, connecting early design docs and roadmaps through standard wikilink patterns.

Linking roadmaps and architecture works by using Obsidian wikilinks and header links to connect related design references. The skill automates navigation between these documents, keeping development workflows centralized and accessible.