Look up how the legacy D35E Foundry system stores mechanics. Use when writing migration scripts, designing dnd35e field equivalents, checking actor data paths (abilities, HP, saves, BAB, AC, skills), item type schemas (weapon, buff, spell, class, equipment), or understanding the changes[] modification template. System ID is D35E (all caps).
Look up planning phases, track progress, and understand phase dependencies. Find which phase covers a feature or system.
Step-by-step workflows for adding new item types, mechanics, compendium entries, and features from planning to code.
Compare D35E (legacy Foundry system), dnd5e, and PF2e implementations side-by-side. Use when deciding data structure for a new item type, comparing buff/AE/RuleElement approaches, checking HP/saves/BAB/AC paths across systems, reviewing condition implementations, or understanding why dnd35e chose a particular design over the D35E approach.
Look up raw D&D 3.5e SRD rules as written. Use when asked about spells (Fireball, Cure Moderate Wounds), feats (prerequisites, Power Attack), conditions (Stunned, Prone, Grappled), combat mechanics (iterative attacks, AoO, grapple, two-weapon fighting), saving throw DCs, or any rules-as-written question. Searches local SRD journal and d20srd.org.
Analyze, improve, and maintain phase planning documentation. Use when: consolidating redundant sections, reorganizing phase structure, updating checklists, moving deferred work, adding cross-references, or improving decision frameworks.
Look up Foundry VTT API, data structures, and patterns. Find classes, methods, events, and configuration options.