General developer workflow guidance for the wanderers-guide repo — how to verify changes (render the app, take screenshots, read the DOM), how to bypass authentication for testing (public character sheet, drawer-open URL), and pointers to where shared theming/styles live. Use this whenever you're working in the repo and need to verify behavior in a browser, or when picking where to put styles. Works alongside `wg-ui` (visual/Mantine patterns) and `wg-content` (data model + linking).
Use whenever writing, editing, reviewing, or programmatically reading WG game content in the wanderers-guide repo — covers the data model (Postgres + frontend cache), the content link syntax, the cache-driven `convertToHardcodedLink` helper, the operations engine, and conventions for what to link in prose. Triggers on any work touching traits/actions/feats/spells/items/ancestries/classes/conditions/damage types or the descriptions/operations attached to them.
Use whenever creating, editing, or reviewing any UI or frontend code in the wanderers-guide repo