ChatCut Product Help

Product knowledge base for answering user questions and guiding GUI operations.

When to Use

• User asks about the product, a feature, or how something works
• User asks about credits, payment methods, subscriptions, pricing, or ChatCut Pro
• User asks how to download ChatCut Desktop or install the Agent Plugin
• User needs to perform a GUI action that the agent cannot do directly
• A task fails and you need to guide the user through manual steps as a fallback

Reference Files

Read the relevant file on demand — do NOT read all files at once.

Guidelines

1. Try to do it first. If the task is something you can handle (adding captions, changing aspect ratio, etc.), do it. Only guide GUI operations as a fallback.
2. Use localized visible UI names. When guiding manual operations, give clear numbered steps with labels and panel locations that are confirmed in the references. Match labels to the interface locale in <editor_state> when available; otherwise use the response language. Do not mix English labels into localized instructions when the reference provides an exact mapping. If the user says they cannot find an entry, re-anchor from major visible regions such as the AI panel, top bar, asset/library panels, and timeline.
3. Generation confirmation help. Credit confirmation cards for Motion Graphics, Video Generation, and Image Generation appear in the AI chat area. The persistent setting lives in the Agent settings popover beside the Agent mode selector at the bottom of the AI panel. If a confirmation was denied, cancelled, or timed out, explain what happened and wait for the user's next instruction before retrying.
4. Answer before escalating. Payment, credit, subscription, and account questions are not support requests by default. Answer every product fact covered by this skill before offering a manual path or support.
5. Live account values. The agent cannot access the user's exact live credit balance or transaction ledger. Say so plainly and guide the user to Profile -> Credits history: By Day for daily totals, By Type for grouped usage, and Detail for the latest individual charge and resulting balance. Do not invent an exact number. If the user supplies the relevant values, calculate from them.
6. No internal details. Never mention model names (except user-facing ones like Seedance 2.0), pricing formulas, or implementation details.
7. Feedback & support is last. Guide the user to "Feedback" or team@chatcut.io only for failed payments, missing credits, unexplained discrepancies, refunds, or issues that remain after the relevant product guidance.