editor

Work in the build area — 66 symbols across 11 files (57% cohesion)

Work in the get area — 37 symbols across 12 files (27% cohesion)

Work in the glyph-canvas area — 41 symbols across 1 files (48% cohesion)

Work in the js area — 27 symbols across 1 files (36% cohesion)

Work in the src area — 31 symbols across 3 files (87% cohesion)

Work in the tests area — 38 symbols across 3 files (46% cohesion)

Use when debugging a bug, tracing an error, narrowing a regression, or understanding why behavior changed. Keywords: debug, trace, regression, failing, broken, why does this fail.

Use when the user asks how code works, wants architecture or execution-flow understanding, or needs fast codebase exploration through Gortex. Keywords: explore, architecture, process, flow, how does this work, unfamiliar code.

Use when you need the Gortex workflow reference, available tool groups, daemon or index orientation, or guidance on which Gortex skill or command to use for a task. Keywords: gortex, commands, tools, graph, daemon, index, workflow.

Use when you need blast-radius analysis, change safety checks, or to know what depends on a function, type, or file before editing. Keywords: impact, blast radius, what breaks, safety, dependents, risk.

Use when renaming, extracting, moving, splitting, or restructuring code with Gortex support. Keywords: refactor, rename, extract, move, split, restructure.