product-help

1# ChatCut Product Help
2 
3If `track_export` is not loaded yet, load it with `ToolSearch` before calling it, so you use its real parameters instead of guessing.
4 
5For a ChatCut product question, the first substantive action is to search the
6exact topic within `https://chatcut.io/docs` and open the most relevant official
7page. Do not answer from memory, a search snippet, or an unopened result. Use the
8host's native search and page-reading capabilities; this Skill defines retrieval
9and decision rules, not a second copy of product facts.
10 
11## Route the question
12 
13- For live project, asset, timeline, item, account, or job state, use the matching
14  ChatCut read tool. If the question is only about live state, no Docs lookup is
15  needed.
16- For current behavior, visible UI labels, installation, credits, pricing,
17  billing, and troubleshooting, use the owning product Docs page.
18- For availability, regressions, or version requirements, use **Current versions**
19  and the **Changelog** in addition to the owning product Docs page.
20- For a mixed question, use tools for live state and Docs for what that state means
21  or what the user should do next.
22- For where an export runs, where its progress shows, and where the file goes,
23  use the export section below. It takes the place of the Docs lookup for those
24  facts.
25 
26Treat this Skill only as stable routing guidance. Never answer a changeable
27product fact from remembered Skill content when current Docs can be checked. Do
28not use unofficial domains.
29…