Jump between related spots in your code by tagging them with the same @@id.
Put @@<id> in a comment in two or more places. Ctrl/Cmd+Click any of them and you teleport to the next one with that id. Keep clicking to cycle through all of them.
How to use
Mark a spot:
// @@checkout
function processOrder() { ... }
Mark another spot with the same id, anywhere in your project:
processOrder(); // @@checkout
Ctrl+Click (Win/Linux) or Cmd+Click (Mac) on either @@checkout → jumps to the other. (F12 works too.)
That's it. Two gates = jump back and forth. Three or more = cycle through them in order.
Why it's useful
Definitions only take you one place. Gates let you connect any spots you choose, across files:
Caller ↔ function — jump from a function to where it's actually called, and back.
Route ↔ handler ↔ frontend call — link an endpoint to the code that serves it and the UI that hits it.
Work-in-progress trail — tag every file you're touching for one change (@@fix-tax) and hop between them instead of hunting through tabs.
Config ↔ usage — connect a setting to where it's read.
Pick a short, unique id per group. Want it gone? Delete the comments.
Notes
Id = @@ + letters/numbers/_/- (e.g. @@auth, @@step-2).
You can put several on one line: // @@a @@b — each clicks independently.
