3 ready prompts
Written for the moment this actually comes up.
Execute — do the immediate task
+We need site search tracking on the storefront. Capture search_term, results_count, and page path…
Execute — do the immediate task
+We need site search tracking on the storefront. Capture search_term, results_count, and page path whenever visitors use the search box on www.example.com and mobile app webviews. Send these as events named Site Search — Search with the values user-entered query and resultCount. Verify the parameter captures exact user text, including special characters, and test searches with zero results and long queries before enabling.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Improve — make it easier to accept
+Before I enable site search reporting, make the raw data useful: extract and normalise common stop…
Improve — make it easier to accept
+Before I enable site search reporting, make the raw data useful: extract and normalise common stop words, surface zero-results queries up front, and make it easy to join search events with session data and product SKU hits. Flag any terms that could be PII or brand sensitive so legal can review. Also recommend a clean event name and parameter mapping for the reports team.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Every time front-end engineers tweak the search widget, our site search telemetry breaks and the…
Become — change the pattern
+Search tracking repeatedly fails after UI changes
Every time front-end engineers tweak the search widget, our site search telemetry breaks and the merchandising team loses trust in the reports. What small habits, naming rules, and acceptance tests should I impose so search-term capture survives UI changes and the team stops reopening old tickets?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Next to this one
Other web analytics work people do in Google Analytics.
Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.
The rest of the map
Same library, five ways in.