Glossary Modal Editor
Use this skill when you need to:
- •change the Glossary modal layout, focus behavior, keyboard shortcuts, or resizing logic in
src/components/Glossary/Glossary.tsxand its sub-components. - •adjust how external UI elements (GameModals, ActionPane buttons, character sheets, tooltips) trigger or navigate within the glossary.
- •add, edit, or reorganize glossary content files so the modal renders new information.
Workflow
- •Verify the data surface: Start by handling glossary JSON entries under
public/data/glossary/entries/, obeying theid,category,filePath, and markdown rules. Referencereferences/data-editing.mdfor file structure, tooltip markup, table styling, and index-generation reminders before touching the modal. - •Update the UI: Use
references/component-architecture.mdto trace howGlossarycomposesGlossaryHeader,GlossarySidebar,GlossaryEntryPanel,GlossaryFooter, andGlossaryResizeHandlesinsideWindowFrame, how it usesuseGlossaryModal,useGlossarySearch, and the surroundingGlossaryContext, and which higher-level modules (e.g.,GameModals.tsx,App.tsx, tooltips,SingleGlossaryEntryModal) rely on it. - •Validate end-to-end: Run
node scripts/generateGlossaryIndex.js, confirm no duplicate IDs or missing categories, and trigger the glossary in-app (Open the modal, use tooltips, or open a single entry modal) to ensure the new data appears and navigation callbacks still work.
References
- •
references/component-architecture.md - •
references/data-editing.md