STOP - READ BEFORE WRITING ANY MALLOY CODE

AI AGENTS: You MUST review this file before writing Malloy code. Cross-skill references below use logical skill: names; load the referenced skill before acting. Before writing code, also read the gotcha skills: skill:malloy-gotchas-modeling, skill:malloy-gotchas-queries, and skill:malloy-gotchas-rendering.

Pre-Flight Checklist

1. Discover first: ground yourself before writing ANY code, with the tool that matches what you are modelling.
   • Modelling data already in a package: malloy_getContext returns that package's sources, views, and fields (with their docs).
   • Modelling a database with no package yet: malloy_getContext has nothing to return, so use malloy_searchDatabaseSchema instead. It walks the connection's schemas and tables, ranks them against a plain-English description, and gives you each table's columns plus the source: line to start from. Take those names verbatim into step 5. Never guess field names either way.
2. Search docs proactively: call malloy_searchDocs BEFORE writing unfamiliar patterns (window functions, query-based sources, pipelines). Don't guess. Malloy syntax is specific and SQL intuition is often wrong.
3. Use skill:malloy-patterns to discover available doc topics (YoY, cohorts, rendering, window functions).
4. Check diagnostics after writing: fix the FIRST error first, errors cascade.
5. Read the gotcha skills: skill:malloy-gotchas-modeling, skill:malloy-gotchas-queries, and skill:malloy-gotchas-rendering prevent the most common mistakes.